NCC Series | idf_db_to_db_sync_heartbeat_status_check

  • 28 April 2020
  • 0 replies

Userlevel 4
Badge +2

The NCC health check idf_db_to_db_sync_heartbeat_status_check verifies the consistency of data replicated from the Source Cluster to the Replica Cluster. IDF is Insights Data Fabric. A DB that contains data about all the entities in the cluster. And it has to be synced between PE and PC.

For the purposes of the check, the source cluster is where the check is run from and the replica cluster is the DB instance that is compared against.

This check returns a FAIL status when the heartbeat sync time between database on the source cluster and database on the replica cluster crosses a predefined threshold value (10 minutes, by default). 

This check is scheduled to run every 5 minutes, by default and will generate an alert after 3 consecutive failures across scheduled intervals


What is the impact?

The impact is the data replicated from the source to the replica cluster is not up to date. This could be because some services may not be working as expected.


If this check returns FAIL, verify the following:

  1. Cluster health status.

  2. Proxy setting in Prism Central and Prism Element.

  3. Connectivity between Prism Central and Prism Element.


To take a look at the commands involved, how the output looks, and what to expect, follow to KB-5582.


Getting PE-PC connectivity issues? Give a read to this post:


This topic has been closed for comments