Skip to main content
Use an IBM Instana Generic webhook alert channel to send Instana issues, incidents, and changes to Flashduty On-call. Each Instana issue or incident maps to one Flashduty alert: the alert triggers when the issue opens and recovers when the issue closes.

​
In Flashduty On-call

You can get the integration push URL in either of the following ways.

​
Use a dedicated integration

  1. In the Flashduty console, select Channel and open a channel
  2. Select Configuration → Integrations → Private integration, then click Add integration
  3. Select Instana, then click Save
  4. Open the generated integration card and copy the Push URL

​
Use a shared integration

  1. In the Flashduty console, go to Integration Center → Alert Events
  2. Select Instana and enter an integration name
  3. Configure the default route and select a channel. You can add more rules under Routing after creation
  4. Click Save and copy the generated Push URL

​
Configure Instana

You need permission to configure alert channels and alerts in Instana. First create an alert channel that points to Flashduty, then select that channel in your alert configurations.
1

Create a Generic webhook alert channel in Instana

Where: Instana › Settings › Global settings › Events & alerts › Alert channels › Add alert channel (in some versions: Settings › Team settings › Alert channels)In the dialog, select Generic webhook, click Add alert channel at the bottom of the dialog, then fill in:Then click Test channel to check that Instana can reach Flashduty. Instana shows Test Successful when it can. This button only proves connectivity: the test notification does not create an alert in Flashduty. Click Create.
2

Select the channel in an Instana alert configuration

Where: Instana › Settings › Alerts › New alertYou need permission to configure alert channels and alerts in Instana.
  1. Enter an alert name
  2. In the Events drop-down, select Alert on event type(s), then turn on the event types to send: Changes and online/offline events are frequent and do not recover automatically. In most cases, turning on Incidents, Critical issues, and Warning issues is enough.
  3. Under Scope, choose the required Apply on range: an application perspective, a Dynamic Focus query (Selected entities only), or All available entities
  4. Under Alerting, click Add alert channels and select the channel you created in the previous step
  5. (Optional) Under Custom payloads, add key-value pairs. They arrive in Flashduty as labels
  6. Click Create
Smart Alerts for applications, websites, and synthetic tests select their alert channels in their own alert configuration. Select the same channel there.
3

Trigger an Instana issue and confirm

Where: Terminal on a host running the Instana agent
  1. Trigger an Instana issue and confirm that Flashduty receives an active alert. You can send a critical event with a duration through the agent’s Event SDK:
  2. Wait for the issue to close in Instana (after 5 minutes in this example) and confirm that the alert recovers
An issue raised right after you save the alert configuration may not be delivered. Wait a few minutes after saving before you trigger one.

​
Alert key

Flashduty uses the Instana issue ID (issue.id) as the Alert Key. An issue or incident carries the same issue.id when it opens and when it closes, so the close notification recovers the alert created when it opened. Changes to the issue title, severity, start time, or tags do not change the Alert Key. Requests without issue.id are rejected.

​
Status and severity

Flashduty sets the alert severity from the issue’s severity (issue.severity): issue.state sets the status: Any other state value is rejected with a parameter error.

​
Labels

Instana fills fields that do not apply with not available. Those fields do not become labels.

​
Troubleshooting

  • Test channel reports that the domain is not allowed: Instana SaaS may restrict the domains alert channels can send to. Contact IBM Instana support to allow the domain of the Flashduty push URL
  • Flashduty returns a parameter error: Make sure the URL is complete and includes integration_key
  • The alert does not recover: Make sure the alert configuration sends issues or incidents, which carry a state. Changes and online/offline events do not recover automatically
  • Real issues are not delivered: Check the event types and scope of the alert configuration, and make sure the alert is linked to the channel
For field details, see Instana Webhook alert channel.