---
sourceDocument: Australia Impact
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/impact

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Impact

ft:clusterId :

    - ipact

bundleId :

    - ipact


---

# Set notifications for configured key alerts

# Set notifications for configured key alerts {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Follow these steps to configure Key Alerts on an instance where critical alerts have not yet been configured.

## Before you begin

Role required: admin

## Procedure

1. Navigate to ImpactPlatform HealthMonitorGo to Instance Observer
2. Log in to Instance Observer and navigate to AlertsConfigure alerts.  
   You can view all the alert type options. These are different metrics you can use to trigger that metrics from transactional date to database response time. They are technical indicators for potential issues on performance on a given instance.

   For example, long running job alerts can indicate potential performance issues or pre-emptive alerts for upcoming performance issues. For more information and how to configure long pending jobs, see [Configure long pending jobs alert](https://servicenow-prod.fluidtopics.net/9YjZllR_OjZXHeFbihDXdg "Get notifications when jobs that are pending exceed your defined overdue thresholds by configuring the Long Pending Jobs alert. Set up conditions by job priority to take action on groups of jobs—such as all discovery jobs or system cleanup jobs—in one go, rather than managing them individually.").
3. Select Configure your alerts.  
   Alerts for metrics chosen by the system display.
4. Select up to five alerts from the Max alerts per day / per metric drop-down to receive for each metric per day.  
   The maximum number of alerts selected pertains to each of the six available system metrics. If you choose a maximum of two alerts for each metric, then you receive 12 alerts, as the maximum alert count each day, for example (2 alerts) X (6 metrics) = 12 alerts. The alert count resets daily at 00:00 UTC.
5. Select Set Notification.  
   The Alert configuration page loads and the Default notification rule is automatically selected. {#configuring-io-alerts__set-notification}
{#configuring-io-alerts__set-notification}
6. **Optional:** Select Configure Notification to create a custom rule.  
   The How to Configure Notification Rules link contains information on custom notification creation. Rule options include Rule Name, Recipients, and Notification Methods.
7. Select Review \& Create to display the summary of the alerts to be configured and the notification rule.  
8. Select Create Alert or Set Notification to return to the notifications configuration page.  
   A notification appears to confirm the alert configuration.

## Result

After the request submission, all six alerts will be enabled automatically, no manual intervention is required. If you want to see the alert threshold, navigate to Edit Alert configuration to access the IO recommended condition.  
Note:  
If one or more alerts out of the six available aren't enabled automatically, then a threshold wasn't available for that specific metric due to limited use in the instance.

After the notifications and alerts are activated you can view them on the Instance Observer home page, which is the [User configurable dashboard](https://servicenow-prod.fluidtopics.net/cPcWPLEx0Y~vVOKPP6VnFw "The All Instances Summary Dashboard is the home page that provides a snapshot of the overall health of your instances. You can create your own dashboard according to your preferences for metrics that help you to analyze the health of your system in a snapshot.") as Self-Service Alerts in the Alerts card.

## What to do next

[Manage Instance Observer alerts](https://servicenow-prod.fluidtopics.net/08PjQD6s31tk~upqdfwtnw "Act on Instance Observer (IO) threshold alerts directly from the notification.")

*[\>]: and then