I have successfully configured Crashlytics Webhook with Slack. I have also tested it with the Test Message given in Crashlytics console. Test message working fine.
But, when I have an actual crash in Crashlytics, it is not getting triggered into the Slack. I don't know where is the issue. What am I doing wrong here?
Mike from Fabric here. I responded over email, but will make the answer public as well.
For this integration, you've set the impact level to 5 which means that only issues that are the most impactful will be mentioned in Slack. If you want to be notified of every new issue, set the impact level to 1.
I configured the firebase crashlytics as it is noted using the webhooks from slack ,
Result is i have a successful testing message sent to the slack channel but not the actual errors even though i have checked all type of crashes, new and recurring, some said a thing about impact level need to be changed to 1 but i can't find how .
Related
I'm building a Telegram bot for myself that should send to me notifications when I get any. I'm trying to achieve the same behavior as GitHub's email notifications. The problem is that I'm not sure if it's even possible. I'm working with GitHub API for few days straight trying to solve this issue but I still have no idea how to do it. It's like GitHub API doesn't provide enough information about the notification.
For example, it provides field "reason", which describes why I got this notification but how to understand what this notification is about? Like, if I was assigned to the issue or pull request (right now it seems like notifications are the same whether I got assigned to the issue or got a new message in the assigned issue), or got a new message in a watching issue/pull request or anything else.
I am calling a Slack Webhook from my Azure Logic App.
All of it works but I notice that the webhook call never completes even though the message has already been received in Slack.
Any help would be great.
thanks
Russ
I threw a red herring here.
I didnt realise that there was an actual slack connector.
It now works perfectly
I am developing chatbot for Slack using Microsoft Bot Framework. The Web app is hosted on azure. We have few installations.
Everything worked fine before this morning when I saw that new bot just didn't respond (the old one is still working).
We've been experimenting on permissions and auth keys on slack, so I thought that was the reason. But I tried to reinstall the app, bot user, auth keys etc from scratch and it didn't help. My configured endpoint just don't hit.
I think the issue is in communication between Slack and Microsoft Bot Framework, 'cos when I'm testing from chatbot panel's web client everything is working fine. Also, Slack representatives confirmed that there's no problem from their side.
UPDATE: I re-checked all credentials again and seems like it's working, don't know what was the issue. But two side questions still actual:
1) Can I test this channel of communication somehow? Cos when my endpoint didn't hit I can't get any info on what is happening. I have 0 errors on Microsoft Bot Framework web console.
2) Docs on configuring slack channel have changed recently and now it suggesting to add "Subscribe to Bot Events", while everything worked w\o it. Can you elaborate on that? Also, it's not quite clear what is {YourBotHandle} docs referring to in https://slack.botframework.com/api/Events/{YourBotHandle}
Usually, the Bot Framework Portal is the place to see if any channel is reporting errors with your bot. You can also check https://github.com/Microsoft/BotBuilder/issues just in case there is a general problem with a channel.
Regarding the second question, {YourBotHandle} refers to the handle that you provided at the time of registering your bot, as explained here.
As far as why you need to subscribe to bot events, first I would recommend you to read the documentation about Events on Slack (here), but long story short, this allows the bot to subscribe to events and be notified when those happen instead of having the bot asking Slack if something happened or not.
One way to use the Events API is as an alternative to opening
websocket connections to the real time messaging API. Instead of
maintaining one or more long-lived connections for each team an
application is connected to, you simply set up one or more endpoints
on your own servers to receive events atomically in near real-time.
We have some Logic Apps setup that monitor our various sites and a Slack connection set up. If a non-200 status code is returned, it sends a message to our alerts channel in Slack. We have about 10 sites that are monitored.
The first was setup, tested the cloned for the other sites.
The issue we're having is that they all seem to work bar one.
The site in question was offline this morning (after host updated the server at 3am this morning) and I can in the Azure log the trigger was fired - but no message in Slack.
I changed the Condition to "status equals 200" (to ensure it always fires), ran it manually and still see no message.
As mentioned this logic app was cloned from one that did work so the only thing that changes from app to app is the site URL and the contents of the slack message.
Being relatively new to various Azure features this was a bit of "R&D" for Logic Apps so I'm not really sure what to check.
Any obvious gotchas we should be aware of? Any pointers you can give to help resolve this would be great.
NB: I added Slack API as a tag to this but as this part is handled by Azure and it's working for other Logic Apps feel free to remove.
I tried to execute gmail api's watch on my two gmail accounts and it works fine.
But when the other user tried to do so, it shows this error:
HTTP error 400 : "Only one user push notification client allowed per developer (call /stop then try again)">
I don't know if the problem is on the pub/sub client configuration or doing stop and watch will resolve the problem?
Can someone explain the meaning of this statement "Only one user push notification client allowed per developer"?
Try using a different project for the Cloud Pub/Sub topic that the other user wants to set up a Gmail API watch on.
You can always renew a watch by first stopping the watch and then immediately initiating a new watch right after. So, try to use users.stop once before you use users.watch.
I have encountered a similar issue. Although this might not be helpful to the OP, for me the solution was to abandon Google's Pub/Sub and use IMAP IDLE instead, which is much better suited for OP's use case of monitoring several inboxes.