The SAP dashboards doesn't show metrics
The sap_basis probe is configured correctly (successful Test, and show green monitors), and we can see using DrNimbus that the SAP QOS Messages arrive to the primary hub.
The next query return results:
SELECT table_id, r_table, ci_metric_id, qos, target, host, robot FROM S_QOS_DATA WHERE qos like 'QOS_SAP%'
and taking the table_id and the r_table for each row results, we confirmed the data is being collected and it is recent:
SELECT * FROM <r_table value from previous query> WHERE table_id = '<table_id value from previous query>
The only thing to notice is that the ci_metric_id from first query doesn't exist in CM_CONFIGURATION_ITEM_METRIC table, i.e. next query doesn't return results
SELECT * FROM CM_CONFIGURATION_ITEM_METRIC WHERE ci_metric_id IN
(SELECT ci_metric_id FROM S_QOS_DATA WHERE qos like 'QOS_SAP%')
We tried the suggested on next technical document, but it didn't make a difference:
UMP - No metrics available displayed for many nodes
Release : 20.3
Component : UIM - SAP_BASIS
If the steps described in the above document didn't make a difference, another thing to review is that the probeDiscovery queue is created in the hub the robot report to.
Probes like sap_basis depends on probeDiscovery queue. In this case, it is necessary to ensure that there are discovery queues in place to pass the discovery messages up to your Primary hub. The parent hub of the robot needs to have an “ATTACH” queue that listens for probe_discovery messages.
The hub that retrieves data from that hub also needs a queue as stated above unless that hub is the primary hub, at which point the discovery_server creates its own listening queue.
If the hubs are not configured with the queues, then those queues need to be created along with the corresponding “GET” queues and the probe needs to be restarted.
1. Select the hub the robot with the sap_basis probe is under it
2. Double click the hub probe
3. Select the Queues tab. See if you have a queue like next. if not, create it (right click any blank space, and select New)
4. On the primary hub create a GET queue to get the probe_discovery messages from the secondary hub under it.
More details in Hub IM Configuration
After creating the queues, and confirm that messages are sent to the primary hub, the metrics should appears almost immediately
Troubleshooting Missing Data in UIM
Default hub queue configuration on secondary hub