---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Integrate Prometheus events

# Integrate Prometheus events {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Integrate Prometheus with Event Management by adding a standard webhook in
Prometheus's Alert Manager.

## Before you begin

* Ensure that the Event Management Connectors (sn_em_connector) plugin is installed on the ServiceNow AI Platform instance.
* Verify Configuration Items for the hosts managed by Prometheus exist in ServiceNow. These CIs can be physical or virtual, and can be either manually created or discovered using IP discovery or Cloud discovery.
* Role required: evt_mgmt_integration

## About this task

Configure the Event Management environment for the collection of events from Prometheus.  
Starting from the Xanadu release, the OOTB (Out-Of-The-Box) event rules provided with the connector, which you have not previously used (i.e., neither activated, deactivated, nor modified), will now have the Apply additional matching rules check box set to true. Previously, this check box was disabled. This change allows you to execute more event rules or automation using the same filter conditions for the events.  
Note:  
This feature applies only to active event rules.

## Procedure

1. In the Prometheus instance, add a webhook.  
   1. Navigate to Alertmanager.yml and add a webhook entry under the recievers.
   2. Enter the endpoint uRL. For example, use `https://<instance-name>/service-now.com/api/sn_em_connector/em/inbound_event?source=prometheus`.
   3. Type `basic_auth` underneath http_config.
   4. Add a username and password under basic_auth, then add the created webhook name in the receiver under route.
   {#prometheus-events-integration__ol_aw3_rjp_brb}
2. In the Prometheus instance, create an alert rule.  
   1. Create a file for the alert rule and add its' path inside prometheus.yml under rules_files.
   2. Create the alert rule as per the prometheus format using PromQL.
   3. Restart AlertManager and Prometheus to reflect the changes.
   {#prometheus-events-integration__ol_qph_2mp_brb}

## Result

Alerts start flowing from Prometheus into the Event Management plugin. The
plugin extracts information from the original Prometheus alert message to populate
the required event fields and inserts the event into the database. In your ServiceNow AI Platform instance, navigate to All Events to
see the events.

If severity isn't received in the payload, the default severity is Major, which can
be changed in the Push Connector Configuration section of Push ConnectorsPrometheus Push Connector. The valid values of severity are 1- Critical,
2- Major, 3- Minor, 4- Warning, and 5- Info.  
Note:  
To map hosts to the cmdb_ci_vm_object
record instead of cmdb_ci_hardware, enable the
Prometheus VM Binding event rule created for
Prometheus. For further information about event rules, see [Event rules](https://servicenow-prod.fluidtopics.net/NAsCQ7ocCYVbIwhpy8vV2w "Use event rules to generate alerts for tracking and remediation. Event rules are stored in the Event Rule [em_match_rule] table. Configure and customize event rules to manage events and alert generation.").

*[\>]: and then