For the complete documentation index, see llms.txt. This page is also available as Markdown.

Configuring Application Health Notifications

Harmony can send real-time notifications to Slack or Microsoft Teams whenever a monitored application's health status changes. Instead of checking the dashboard manually, your team receives alerts the moment an outage begins, worsens, recovers, or has an incident-level update. Notification rules are flexible, letting you configure two independent alert types for each rule so you only receive the signals that matter to your team.

Alert types

Each notification rule supports two independently configurable alert types:

  • Overall status change alerts - Triggered when an application transitions between health states, for example from Operational to Major Outage, or from Partial Outage back to Operational. These alerts also fire when a newly detected application is first seen in a non-operational state.

  • Incident-level update alerts - Triggered when individual incidents within a monitored application are created, updated, or resolved.

You can enable either or both alert types on a single rule, giving you fine-grained control over notification volume.

Prerequisites

Before configuring notifications, make sure you have:

  • A Slack channel with an active incoming webhook, or a Microsoft Teams channel with an incoming webhook connector configured.

  • Access to the Harmony Settings area.

Configuring a notification rule

  1. In Harmony, open Settings and navigate to the Notifications section.

  2. Click Add notification rule.

  3. Choose your notification channel type - either Slack or Microsoft Teams.

  4. Enter the Webhook URL for your chosen channel.

  5. Select the applications you want this rule to monitor. You can select one application, multiple applications, or all monitored applications.

  6. Under Alert types, enable one or both of the following:

    • Overall status change - to receive alerts when an application's top-level health state changes.

    • Incident-level updates - to receive alerts when individual incidents are created, updated, or resolved.

  7. Click Save to activate the rule.

Repeat these steps to create additional rules, for example to route critical application alerts to one Slack channel and incident-level updates to a separate Teams channel.

Editing or removing a notification rule

  1. In Settings, navigate to the Notifications section.

  2. Locate the rule you want to change and click Edit.

  3. Update any fields as needed and click Save, or click Delete to remove the rule entirely.

Deleting a rule stops all notifications associated with it immediately. Existing incident history and application health data are not affected.

Notification behavior reference

Scenario
Overall status change alert
Incident-level update alert

App moves from Operational to Partial Outage

Sent

Not sent

App moves from Partial Outage to Major Outage

Sent

Not sent

App recovers to Operational

Sent

Not sent

New app first detected in a non-operational state

Sent

Not sent

Individual incident created on an app

Not sent

Sent

Individual incident updated

Not sent

Sent

Individual incident resolved

Not sent

Sent

Tips for reducing notification noise

  • Enable only Overall status change alerts for applications where you care about the headline status but not every incremental incident update.

  • Create separate rules for different teams or escalation paths rather than adding all recipients to a single webhook.

  • Use Microsoft Teams channel threading or Slack notification preferences to control how alerts surface for individual team members.

Last updated

Was this helpful?