The built-in Dynatrace Problems trigger initiates flows when it receives a request from a webhook in Dynatrace.
- Go to the Triggers tab in the palette, expand the App Triggers section, and drag the trigger onto the canvas.
- Double-click the trigger (or click the pencil icon).
- Set the authenticating user, and then copy the URL — you'll use this to set up the webhook in Dynatrace. Alternatively, you can create an integration user to use as the authenticating user.
- Click the Flood Control tab to edit the trigger's default flood control settings. For more information about these settings, see Trigger Flood Control.
- Connect the steps you want to run when xMatters receives a request to that URL.
You're now ready to configure Dynatrace to target the trigger.
Configure Dynatrace to send requests to the trigger URL
To have Dynatrace send alerts to the flow trigger, you need to configure a webhook and set it to use the trigger URL.
- In Dynatrace, select Problems from the left-hand menu and click Set up notifications.
- On the Problem notification setup page, click Set up notifications.
- Select xMatters from the list of integrations.
- On the Set up xMattersintegration page, fill in the following fields:
- Display name: Give the integration a unique name.
- xMattersURL: Paste the trigger URL you copied from the Dynatrace trigger in Flow Designer. Add the target names of any recipients you want xMatters to notify when the alert fires.
- For example, if you want to notify Emma Pearson, Mary McBride, and the on-call members in the Monitor Team responsible for the service, you'd add ?recipients=epearson,mmcbride,monitor%20team to the URL.
- You must URL-encode any special characters or spaces in the target names.
- Leave the Custom JSON payload section unchanged.
- Select an Alerting profile from the drop-down list.
- Click Send test notification.
- When the test completes successfully, Save the integration.
You're ready to use the webhook to trigger automated flows, including steps such as sending alerts and initiating incidents, though we always recommend testing before putting things into use.
The trigger has the following outputs you can use as inputs to steps further along the flow.
|List of targeted recipients. Recipients are set by adding a recipients query parameter to the trigger URL when you configure the webhook in Dynatrace.|
|Signal Mode||Determines the path the flow will take, based on the value of State parameter.|
|Signal ID||Key or identifier used to terminate or correlate signals.|
|Impacted Entity||Entity or entities impacted by the problem.|
|PID||Unique ID of the problem in Dynatrace.|
|Problem Details JSON||All problem event details provided as a stringified JSON object.|
|Problem Details Text||All problem event details provided as text strings.|
|Problem ID||Display number of the reported problem in Dynatrace.|
Impact level of the problem that triggered the signal. Valid values are:
Severity level of the problem that triggered the signal. Valid values are:
|Problem Title||Short description of the problem in Dynatrace.|
|Problem URL||Direct link to the problem within Dynatrace.|
Current state of the problem. Valid values are:
|Tags||Comma-separated list of tags for all impacted entities.|
|Raw Request||JSON representation of the request. You can parse the raw request if you need additional details beyond the standard outputs.|