--- sourceDocument: Zurich ServiceNow AI Platform Capabilities sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/servicenow-platform Release : - zurich ft:locale : - en-US ft:publication_title : - Zurich ServiceNow AI Platform Capabilities ft:clusterId : - platcap bundleId : - platcap workflow : - Platform --- # Monitoring replication status # Monitoring replication status in Instance Data Replication {#ariaid-title1} * Release version: Zurich * * Updated July 31, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 6 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Monitoring replication status in Instance Data Replication The Instance Data Replication (IDR) Monitoring Dashboard enables ServiceNow customers with admin or idradmin roles to track the health and status of data replication activities between producer and consumer instances. This monitoring is critical for ensuring data consistency, replication performance, and identifying issues promptly. Show full answer Show less You can access the dashboard by navigating to **Instance Data Replication \> Monitoring Dashboard** and selecting from three options: IDR Overall Monitoring, IDR License and Usage SMv2, or Scheduled Replication dashboard. ## Key Features * **IDR Overall Monitoring Dashboard:** Monitors active producer and consumer replication sets, data lag, network lag, replication queue lag, suite of scheduled jobs, and seeding requests within the last 7 days. * **Active Producer Replication Sets:** Displays replication set name, replication queue reading lag (time between record change and queue transfer), status, error messages, and message queue version (default Hermes V2). * **Active Consumer Replication Sets:** Shows consumer replication set name, data lag (time from producer change to consumer record), network lag (queue to consumer record), status, error messages, and message queue version. * **Suite of IDR Scheduled Jobs:** Monitors jobs responsible for polling data changes, seeding requests, and health checks on producer and consumer instances. Jobs run periodically (typically every 15 seconds) and can be configured with custom triggers. Examples include Hermes metrics collection, topic synchronization, polling consumer and producer changes, and health heartbeats. * **Producer and Consumer Seeding Requests (last 7 days):** Tracks status, start/end times, and percent completion of seeding jobs, helping identify ongoing or failed data synchronization tasks. * **IDR Dashboard Properties:** Allows customization of lag time thresholds (default 15 minutes) that highlight delays in red for Data Lag, Network Lag, and Replication Queue Reading Lag fields to quickly identify performance issues. * **IDR License and Usage SMv2 Dashboard:** Monitors message counts sent and received by subscriber instances monthly, license details including type, category, period, and license allocation and usage statistics. * **Scheduled Replication Dashboard:** Provides insights into scheduled replication sets and requests over a selected date range, including counts of completed and failed requests, overall request status visualized by a donut chart, and replication set status overview tables. ## Practical Benefits * Provides real-time visibility into replication latency and errors, enabling proactive issue resolution. * Helps ensure data integrity and synchronization between instances with detailed seeding request tracking. * Enables monitoring of scheduled replication jobs to optimize performance and reliability. * Supports license usage tracking to help manage subscription compliance and capacity planning. * Customizable dashboard properties allow tailoring alert thresholds to your organization's operational requirements. ## Next Steps ServiceNow customers should use this monitoring capability to regularly review the health of their replication environment, configure job schedules and alert thresholds as needed, and investigate any errors or lag times promptly. Additionally, consider related tasks such as managing consumer access, resolving replication errors, and comparing replicated data between instances to maintain a robust replication setup. Monitor the status of active producer and consumer replication sets, scheduled jobs, seeding requests, license usage, or scheduled replication through the Instance Data Replication (IDR) Monitoring Dashboard. ## Accessing the IDR Monitoring dashboard {#instance-data-replication-dashboard__section_lh3_vsl_4jb} Users with the admin or idr_admin role can access the dashboard. Access the IDR Monitoring dashboard in the following way: * Navigate to Instance Data ReplicationMonitoring Dashboard. * Choose one of the following: IDR Overall Monitoring, IDR License and Usage SMv2, or Scheduled Replication dashboard. {#instance-data-replication-dashboard__ul_ql1_y3v_rjb} ## IDR Overall Monitoring dashboard {#instance-data-replication-dashboard__section_tng_ptk_znb} The IDR Overall Monitoring dashboard monitors the following: * Active Producer Replication Sets * Active Consumer Replications Sets * Suite of IDR Scheduled Jobs * Producer Seeding Requests Within Last 7 Days * Consumer Seeding Requests Within Last 7 Days {#instance-data-replication-dashboard__ul_sxz_rtk_znb} Figure 1. IDR overall monitoring dashboard Active Producer Replication Sets : The Active Producer Replication Sets monitors your producer replication set status and reports the data lag time between your instance and the replication queue. {#instance-data-replication-dashboard__table_f2z_btl_4jb__entry__2} | Field | Description | |-|-| | Name | Name of the producer replication set | | Replication Queue Reading Lag | Time between a record change on the producer instance and the moment that it's sent over the outbound replication queue | | Status | Status of a replication set, either active or in error | | Status Message | Message that describes the error status | | Message Queue Version | Version of the Message Queue. Default is V2 (Hermes). | [ ] {#instance-data-replication-dashboard__table_f2z_btl_4jb} Active Consumer Replication Sets : Active Consumer Replication Sets monitors your consumer replication set status, reports the network lag time, and reports the data lag time between the producer instance and consumer instance.{#instance-data-replication-dashboard__table_iq4_ctl_4jb__entry__2} | Field | Description | |-|-| | Name | Name of the consumer replication set. | | Data Lag | Time between a record change on the producer instance and the moment that it's recorded in the consumer instance. | | Network Lag | Time between a record change log in the outbound replication queue and the moment that it's recorded in the consumer instance. | | Status | Status of a replication set, either active or in error. | | Status Message | Message that describes the error status. | | Message Queue Version | Version of the Message Queue. Default is V2 (Hermes). | [ ] {#instance-data-replication-dashboard__table_iq4_ctl_4jb} Suite of IDR Scheduled Jobs : The suite of IDR scheduled jobs poll for data changes, requests, and check the health of your producer and consumer instances. You can monitor the following jobs: {#instance-data-replication-dashboard__table_vls_jxk_znb__entry__2} | Jobs | Description | |-|-| | Hermes Metrics Collection | Collects metrics related to the Hermes Messaging Service. | | Hermes Periodic Purge | Cleans obsolete cached data in the Hermes API. | | Hermes Topics Util | Synchronizes topics across Hermes clusters. Initially, topics are created in a single Hermes cluster. This job detects new topics and creates the same topics in the remaining Hermes clusters. | | IDRConsumerJob | Polls for record changes and seeding requests on the consumer instance in 15-second intervals. | | IDRDeltaConsumerJob | Beginning in the San Diego release, when a consumer instance subscribes to a producer instance that is outside the local datacenter, the IDRDeltaConsumerJob job is created on the producer instance. The function is the same as the IDRConsumerJob. The three-letter code denotes the datacenter location. | | IDRHermesDeltaConsumer | Polls for consumer record changes from the Hermes delta topic in 15-second intervals. | | IDRHeartBeatJob | Updates information about the health of every active producer or consumer set. | | IDRMetadataConsumerJob | Polls for metadata record changes on the consumer instance in 15-second intervals. | | IDRProducerJob | Polls for new, updated, or deleted records in the data replication queue for a producer instance in 15-second intervals. | | IDRSeedingProducerJob | Checks for new seeding requests coming from consumer instances. | [ ] {#instance-data-replication-dashboard__table_vls_jxk_znb} Note: You can set when your IDR scheduled jobs run and configure a periodic trigger that specifies how often the job runs. {#instance-data-replication-dashboard__table_b4j_dtl_4jb__entry__2} | Field | Description | |-|-| | Name | Scheduled job name. | | Next Action | Date and time when the job next runs. | | Trigger type | Job that you can configure to run daily, weekly, monthly, periodically, once, on-demand, or business calendar start or end date. The trigger can repeat daily, hourly, by minute, or by second. | | Job ID | ID of the scheduled job. | | State | State of the job, for example, ready. | [Table 1. IDR Scheduled Jobs field types] {#instance-data-replication-dashboard__table_b4j_dtl_4jb} Producer Seeding Request Within Last 7 Days : You can monitor the status of a producer seeding request within the last seven days.{#instance-data-replication-dashboard__table_mvy_dtl_4jb__entry__2} | Field | Description | |-|-| | Replication Set | Producer set and the consumer set. | | Status | Status of the seeding request. The status can be completed, in progress, or failed. | | Start Time | Time that the seeding begins. | | End Time | Time that the seeding ends. | | Percent Complete | Percentage of the seeding request job that is complete. | [ ] {#instance-data-replication-dashboard__table_mvy_dtl_4jb} Consumer Seeding Request Within Last 7 Days : You can monitor the status of a consumer seeding request within the last seven days.{#instance-data-replication-dashboard__table_h44_s3d_sjb__entry__2} | Field | Description | |-|-| | Replication Set | Corresponding consumer set. | | Status | Status of the seeding request. The status can be completed, in progress, or failed. | | Start Time | Time that the seeding begins. | | End Time | Time that the seeding ends. | | Percent Complete | Percentage of the seeding request job that is complete. | [ ] {#instance-data-replication-dashboard__table_h44_s3d_sjb} IDR dashboard properties : You can access the IDR dashboard properties by navigating to Instance Data ReplicationProperties. You can change the following properties on your dashboard:{#instance-data-replication-dashboard__table_is1_rcw_rjb__entry__2} | Property field | Description | |-|-| | Minutes of lag before the Data Lag field are highlighted in red on the IDR Monitoring Dashboard | Data Lag field that is part of the Active Consumer Replication set. If the actual lag time is greater than the time threshold that you set, the system highlights the field. The default is 15 minutes. | | Minutes of lag before the Network Lag field is highlighted in red on the IDR Monitoring Dashboard | Network Lag field that is part of the Active Consumer Replication set. If the actual lag time is greater than the time threshold that you set, the system highlights the field. The default is 15 minutes. | | Minutes of lag before the system highlights the Replication Queue Reading Lag field in red on the IDR Monitoring Dashboard | Replication Queue Reading Lag field that is part of the Active Consumer Replication set. If the actual lag time is greater than the time threshold that you set, the system highlights the field. The default is 15 minutes. | [ ] {#instance-data-replication-dashboard__table_is1_rcw_rjb} Note: You can set the colors on the fields through the personalize list columns (v_idr_dashboard_list.do). ## IDR License and Usage SMv2 dashboard {#instance-data-replication-dashboard__section_jxf_yd5_znb} The IDR License and Usage SMv2 dashboard monitors the following: * Subscriber Sent Messages * Subscriber Received Messages * IDR License Details * IDR Messages Sent * IDR Messages Received {#instance-data-replication-dashboard__ul_akw_sh5_znb} Subscriber Sent Messages : The number of messages each subscriber instance sent, by month. Figure 2. Subscriber messages sent Subscriber Received Messages : The number of messages each subscriber instance received, by month. Figure 3. Subscriber messages received IDR License Details : You can monitor the status of a consumer seeding request within the last seven days.{#instance-data-replication-dashboard__table_dsw_q35_znb__entry__2} | Field | Description | |-|-| | Name | Name of the IDR license. | | Type | Type of subscription: Per-User for user subscriptions, Capacity for data driven subscriptions, or Unrestricted User for subscriptions capped by the maximum user count. | | Category | License category: ServiceNow license or Store App license. | | Start date | Start of the licensing period. | | End date | End of the licensing period. | | Display only | Does not support resource allocation or monitoring. | | Purchased | Number of purchased licenses. | | Allocated | Number of allocated licenses. | [ ] {#instance-data-replication-dashboard__table_dsw_q35_znb} IDR Messages Sent : The number of messages sent, per license, monthly. Figure 4. IDR messages sent IDR Messages Received : The number of messages received, per license, monthly. Figure 5. IDR messages received ## Scheduled Replication dashboard {#instance-data-replication-dashboard__section_yqg_5yj_1fc} Monitor the status of scheduled replication requests within a specific time period. For example, you might track the count of failures for a specific scheduled replication set, or compare the number of scheduled requests to the number of completed requests. You can view the following scheduled replication details: * Scheduled Sets * Scheduled Requests * Completed * Failed * Overall Request Status * Replication Set Status Overview {#instance-data-replication-dashboard__ul_kr2_k2k_1fc} Scheduled Sets : The total count of scheduled replication sets created in the selected date range. Scheduled Requests : The total count of scheduled request runs queued in the selected date range. Completed : The total count of scheduled request runs that completed in the selected date range. Failed : The total count of scheduled request runs that failed to complete or encountered an error in the selected date range. Overall Request Status : A donut chart showing status distribution for scheduled requests in the selected date range. Replication Set Status Overview : A table showing the count for each status in the selected date range. **Related concepts** * [Comparing replicated data between instances in Instance Data Replication](https://www.servicenow.com/docs/ZwBxZE8EjVPFz7VN4nDp_g "Find missing or mismatched records by comparing replication data between instances in Instance Data Replication (IDR).") * [Deploying a replication configuration from one instance to another in Instance Data Replication](https://www.servicenow.com/docs/OdN3eTxiDLyQ~5NoJeDW2A "Copy a replication configuration from one instance to another through an update set in Instance Data Replication (IDR).") * [Cloning options with Instance Data Replication](https://www.servicenow.com/docs/aWVqawl2PQx1R2Hy5XgOmA "Ensure that certain tables are preserved or excluded to clone your database from one instance to another successfully with Instance Data Replication (IDR).") * [Monitoring queues in Instance Data Replication](https://www.servicenow.com/docs/QATLHd6QGZANqK07upTqqA "Monitor the replication record queue, message produced queue, message consumed queue, and the messages processed for all replications sets through the Instance Data Replication (IDR) Queue Dashboard.") * [Avoiding insert and update errors in Instance Data Replication](https://www.servicenow.com/docs/9jyxlc_h6j8A0f5itHT7Dg "You can avoid insert and update failures in Instance Data Replication (IDR) by specifying a class name filter in the producer replication set.") **Related tasks** * [Manage consumer access to replication data in Instance Data Replication](https://www.servicenow.com/docs/XOfuOuuug2GyvUFGjyMMpw "Approve a consumer's request to access replication data in Instance Data Replication (IDR).") **Related reference** * [Resolving data replication errors in Instance Data Replication](https://www.servicenow.com/docs/D6N4Ub9HnNCj5jQsdrOrmw "Resolve errors and monitor the status of Instance Data Replication (IDR) replication sets.") *[\>]: and then