Monitoring replication status in Instance Data Replication
-
- UpdatedJan 30, 2025
- 6 minutes to read
- Yokohama
- Instance Data Replication
Monitor the status of active producer and consumer replication sets, scheduled jobs, seeding requests, and license or usage details through the Instance Data Replication (IDR) Monitoring Dashboard.
Accessing the IDR Monitoring dashboard
Users with the admin or idr_admin role can access the dashboard.
- Navigate to .
- Choose either: IDR Overall Monitoring or IDR License and Usage Details dashboard.
IDR Overall Monitoring dashboard
- 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

- 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.
- 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.
- 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: Note: You can set when your IDR scheduled jobs run and configure a periodic trigger that specifies how often the job runs.
- Producer Seeding Request Within Last 7 Days
- You can monitor the status of a producer seeding request within the last seven days.
- Consumer Seeding Request Within Last 7 Days
- You can monitor the status of a consumer seeding request within the last seven days.
- IDR dashboard properties
You can access the IDR dashboard properties by navigating to .
You can change the following properties on your dashboard: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. Note: You can set the colors on the fields through the personalize list columns (v_idr_dashboard_list.do).
IDR License and Usage Details dashboard
- Subscriber Sent Messages
- Subscriber Received Messages
- IDR License Details
- IDR Messages Sent
- IDR Messages Received
- 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.
- 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
On this page
Related Content
- Manage consumer access to replication data in Instance Data Replication
Approve or deny a request to grant access to the replication data in Instance Data Replication (IDR).
- Comparing replicated data between instances in Instance Data Replication
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
Copy a replication configuration from one instance to another through an update set in Instance Data Replication (IDR).
- Cloning with Instance Data Replication
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
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.
- Preventing insert and update errors in Instance Data Replication
You can prevent insert and update failures in Instance Data Replication (IDR) by specifying a class name filter in the producer replication set.
- Resolving data replication errors in Instance Data Replication
Resolve errors and monitor the status of Instance Data Replication (IDR) replication sets.