Working with the free tier to test out the connections with various tools, and I am working on creating a custom webhook from Threatstack to xMatters. I have my webhook setup and shared that with the Threatstack integrations. I am getting a response, however I am getting this:
"A problem occurred while processing your Webhook integration from the TS communication plan.
Request ID
XXXXXXXXXXXX
Time
Nov 04, 2019 15:13:54 UTC"
Here is the log:
| 2019/11/04 10:13:56.234 |
Starting Event XXXXX, for incident INCIDENT_ID-XXXXXX, and domain applications
|
|
| 10:13:57.356 |
Notifying xMatters Support (xm-support)
|
|
| 10:13:57.394 |
xMatters Support (xm-support) has no notifiable Devices
|
|
| 10:13:57.620 |
Targeted recipient failure; none of the directly targeted recipients could be notified.
|
Not sure why it is showing no recipients, I am getting alerted on my other xMatters flows. Just not this one. Not sure what I am missing. I also don't see anything in the Activity tab for this flow, but again on the free tier, so I am not seeing the Developers tab, nor integrations...I am seeing all this through the workflow section.
Any help?
Thanks!
D
Comments
Please sign in to leave a comment.
It seems odd that you don't see anything in the Activity tab for your flow. The message you are looking at is auto-generated when there is an error, which as far as I know are always logged in the activity log. And the activity log is where the useful information about this is going to be.
Hi David,
The xm-support account is for our support team to go in there and take a look around. It's not expected to have any devices on it and should not be the target of any notifications. If you are not sending this account as a recipient and it's not configured in any forms then without seeing things it will be hard to tell why that account is being notified.
Here's a couple of starter questions:
1) Are you sending any recipients in the payload to create an xMatters event?
2) Do you have any recipients hard-coded into the form?
Is it possible to see the payload you are sending? If you want an investigation in the back-end we may need an event ID we can trace.
Thanks everyone. I was able to locate the activity tab and figure out what my issue was. I was not bringing the JSON in correctly and I was getting a 400 Bad Request error. We were then able to start alerting on the information and create a proper flow.
Great to hear!
I'd love to add Threatstack to our portfolio of integrations, if you have some time, do you think you can write up an entry for xM Labs here:
https://github.com/xmatters/xMatters-Labs
There is a template repo that walks through the format.
If you'd rather just send me the exported Workflow zip file and some screen shots and details on how to set up the Threatstack side, I can write it up and add it to the Labs. Let me know!
Happy Tuesday!