Go to All Forums

Manage tags in alerts sent through third-party integrations


Dear customers,

We're happy to introduce a new feature supporting tags to help you ensure effective management of alert information shared through our third-party integration services. You now have the option to choose the tags associated with a monitor to be included as a parameter in the alerts.

Previously, when an alert was sent to a third-party service, the tags associated with the monitor would also be sent as one of the parameters with the alert. In some third-party services, like Opsgenie, the size of the alert parameters get truncated when their length exceeds a certain limit. This can cause issues when you have multiple tags for a monitor, resulting in the elimination of necessary tags and the addition of irrelevant tags.

With this enhancement, the new input field (Tags to be sent with alerts) can be used to specify the tags to be sent with the alert.

For instance, consider you have the following tags:

          Tag Name                           Tag Value
          Priority                              Low
          Priority                              Medium
          Priority                              High  
          Environment                              US-1 
          Environment                              US-2
          Functioning                              False
          DC                                1 

Consider the monitors with their tag configuration as shown below:

      Monitor Name                       Configured Tags
         Cliq                Priority:Low, Environment:US-1
         Connect               Priority:High, Environment:US-2, DC:1
         Zia               Functioning:False

 

Assume that a third-party integration supporting the new enhancement was configured for all the three monitors mentioned above, and in the Tags to be sent with alerts field, Priority and Environment are selected.

Let's take a look at what happens when these monitors are down:

  • When the Cliq monitor goes down: {Priority:Low, Environment:US-1} will be sent along with the alert.
  • When the Connect monitor goes down: {Priority: High, Environment:US-2} will be sent with the alert. (DC:1 will not be sent with the alert because you did not configure the DC tag in the input field.)
  • When the Zia monitor goes down: {Functioning:False} will be sent with the alert.(When none of the tags configured in the integration matches with the tags of a failed monitor, all the tags associated with the monitor will be sent with the alert)

But when a new integration is created without specifying any tag in the Tags to be sent with alerts field, all the tags associated with the monitor will be sent with the alert, and that might again result in the truncation of important tags.

Integrations supported in this enhancement:

  • Slack
  • Opsgenie
  • Webhooks
  • Jira
  • ServiceNow
  • PagerDuty
  • Microsoft Teams
  • ConnectWise Manage
  • Moogsoft
  • Amazon EventBridge

Learn more about third-party integrations supported in Site24x7. We'd love to hear your feedback on this enhancement in the comments section below.

Like (2) Reply
Replies (0)