Site24x7 to ServiceNow CMDB integration: CI mapping reference
Site24x7 provides integration with
ServiceNow, allowing seamless population of Configuration Items (CIs) in your ServiceNow CMDB based on your monitored resources in Site24x7.
This article provides a reference for the field mappings used during the CMDB integration. The mapping is organized based on monitor categories like servers, websites, databases, containers, and more.
Mapping sheet overview
The attached
sheet contains the following columns:
Column name
| Description |
| Site24x7 monitor type (e.g., NETWORK DEVICES). |
CI Type | The corresponding ServiceNow CI table (e.g., u_cmdb_ci_wm_ec2autoscaling). |
Site24x7 field | Attribute name as sent from Site24x7 (e.g., INSTANCE_ID, URLID). |
ServiceNow field | Target field in the ServiceNow CI table (e.g., u_instance_id, u_monitor_id). |
Sample mapping
Below is a sample of field mappings for some commonly used monitor types:
Example 1: Network Device (Monitor Type: NETWORKDEVICE)
| Site24x7 field | ServiceNow field |
| u_interfaceid |
COLLECTIONTIME | u_collectiontime |
INTERFACE_IP | |
INTERFACEINDEX |
|
SYSTEM_DESC | |
URLID | |
LASTSELFTESTRESULT | |
RUNTIMEREMAINING | u_runtimeremaining |
MODEL | u_model |
| u_lastselftestdate |
BATTERYSTATUS | |
OUTPUTCURRENT | |
BATTERYHEALTH | |
LINKSTATUS | |
OUTPUTVOLTS | |
LOCATIONID | |
DEVICEPINGABLE | |
MANAGED | |
POLLINGINTERVAL | |
POLLVIA | |
DEPENDANCY | |
SYSNAME | |
VENDORNAME | |
DEVICENAME | |
COMMUNITY | u_community |
| |
DNSNAME | u_dnsname |
SYSTEMDESC | |
TRIMMEDDESC | u_trimmeddesc |
DEVICEPROTOCOL | |
MANUFACTURER | |
UPDATEDTIME | u_updatedtime |
SERIALNUMBER | |
FIRMWAREVERSION | |
| |
SWITCH_ID | u_switch_id |
SWITCH_NO | u_switch_no |
SWITCH_ROLE | u_switch_role |
SWITCH_STATE | u_switch_state |
SWITCH_MAC | u_switch_mac |
SWITCH_SWPRIORITY | u_switch_swpriority |
SWITCH_HWPRIORITY | u_switch_hwpriority |
SWITCH_MODEL | u_switch_model |
SWITCH_SERIALNO | u_switch_serialno |
STACK_REDUNDANCY | u_stack_redundancy |
NEIGHBOR1_NO | u_neighbor1_no |
NEIGHBOR1_NO | u_neighbor2_no |
NEIGHBOR1_STATUS | |
NEIGHBOR2_STATUS | u_neighbor2_status |
SWITCH_STATUS | u_switch_status |
REASON | u_reason |
How it works
During the CMDB sync process:
- Site24x7 retrieves monitor metadata and metrics.
- These fields are then mapped based on the configuration defined in this mapping sheet.
- The data is pushed into ServiceNow CI tables (custom or native) using REST API.
Related Articles
How can I choose resources in a monitor group for third-party integration
By associating the monitor group with a tag, you can select the resources in a monitor group for third-party integration. Read how to add a tag to a monitor group. Once you have added a tag to the group, choose the tag to integrate the resources ...
Preventing duplicate ticket creation in custom ticketing integrations via webhooks
Issue Alerts sent from Site24x7 to a webhook fail with a 400 error and are marked as duplicate events by the third-party system. Common cause This issue is likely caused by a possible misconfiguration in the Update URL and Close URL settings of the ...
How to integrate Site24x7 with an LLM
You can integrate LLMs with Site24x7 monitors to derive an overall summary of your monitors. The Zia Bot can answer all your queries regarding the monitors to which you have access and answer basic questions about all monitors. The Zia Bot uses the ...
APM Insight integration for Next.js in Kubernetes
To integrate the Site24x7 APM Insight Next.js agent into your Kubernetes application using initContainers with the prebuilt agent image, follow the steps below: Prerequisites A Next.js application container image The Site24x7 APM Insight license key ...
What are Incident Parameters and Custom Parameters?
Incident and Custom parameters get passed along with the body of the URL during an HTTP request invocation. Incident Parameters Incident Parameters are predefined system parameters passed in the invoked URL's body. In the HTTP response, the Incident ...