Resolve issues related to metric graph data, frequency of data collection, and gaps in monitoring. You’ll find detailed instructions on:

  • Fixing metric graph data not displaying on some or all resources
  • Troubleshooting gaps in metric graphs
  • Ensuring data collection is happening as per configured schedules

Metric graph data is not appearing on all resources

  1. Verify the folllowing resource attributes with Installed App Details:
  • App Name
  • App Version
  • Native Type

  1. Verify template assignments Verify that templates are assigned to the corresponding SDK app resources as specified in the SDK app documentation.

  2. Verify DMPs, Templates, and Monitors Ensure that the DMPs, Templates, and Monitors are created during the app publishing process, following the specified signature in the document.

  3. Verify DMP logs in the Cloud UI a. Go to Setup -> Resources -> Device Management Policy. b.Click on the Logs corresponding to the relevant DMP.

  4. Verify template monitor details in Gateway Database via GCLI a. Log in to the gateway. b. Open the GCLI terminal by typing gcli. c. Go to the Resource Details page for the resource with monitoring issues and copy the Resource UUID.

  5. Execute the following commands: a. To get the templateId, run: gcli> sdkgetresourceconfig <resourceuuid> b. To get the template monitor details, run: gcli> sdkgetmonitoringconfig <template id> c. To get the resource monitor details, run: gcli> sdkgetresourceconfig <Resource UUID> d. To verify the monitor schedule job details, run: gcli> sdkgetmonitorjobs <app name> <config id>

  6. Ensure the data from the above commands persists as per the template configurations and the specified schedule frequency.

  7. Verify Gateway Connectivity and Status a. Go to Setup → Resources → Management Profiles. b. Check if the status of the Management Profile is marked as Connected. This indicates whether the gateway is properly communicating with OpsRamp.

  8. Verifying Target Device Reachability and Connectivity a. Go to Setup → Resources. b. Ensure the device is listed and marked as reachable. c. Test connectivity by running the appropriate ping or network diagnostics command via the gateway or from the OpsRamp platform.

  9. Verify Monitoring API in GCLI

    a. Open the GCLI terminal. b. Execute the appropriate API command to verify monitoring, based on the specific documentation of the SDK app. c. Ensure the API response matches expected values.

Metric graph data not getting on some resources

  1. Verify the following resource attributes:
  • App Name
  • App Version
  • Native Type
  1. Ensure that templates are assigned to the SDK app resources as specified in the documentation.
  2. Verify the DMPs, Templates, and Monitors created during the app publishing process.
  3. Review the DMP logs in the cloud UI by going to Setup -> Resources -> Device Management Policy and clicking the Logs corresponding to the relevant DMP.
  4. For template monitor details in the gateway database, refer to Step 5 under Metric graph data is not getting on all resources.
  5. For gateway connectivity and status, refer to Step 1 under No single resource was discovered.
  6. For target device reachability and connectivity, refer to Step 7 under No single resource was discovered.
  7. Verify the monitoring API by following the steps in Step 8 under No single resource was discovered.

Some metric graphs are not getting on resource

  1. Verify that metrics are exist in the applied monitor of the resource & graph enabled on those metrics.

  2. Verify the metric definitions in the template configurations in gateway database by using ~gcli~ command.

                 Refer Step5 in Metric graph data is not getting on all resources

             Here, verify metric existence & 'graphPoint' attribute should true.

Step3 : Verify the target device reachability and connectivity

                Refer Step7 in No single resource was discovered

Step4 : Verify the corresponding metric monitoring api by gcli command as mentioned in the document

                Refer Step8 in No single resource was discovered

Metric graph data not appearing based on schedule frequency

  1. Verify that template monitor details are persisted in the gateway database. Refer to Step 5 under Metric graph data is not getting on all resources.
  2. Check the schedule jobs persisted in the RAM jobs scheduler using: gcli> ramjobslist

Metric graph data stopping after some time

  1. Verify the gateway connectivity and the vprobe status. Refer to Step 1 under No single resource was discovered.
  2. Verify target device reachability and connectivity as per Step 7 in No single resource was discovered.
  3. Check the monitoring API by referring to Step 8 under No single resource was discovered.

LatestMetricSnapshot data is empty

  1. Verify the gateway connectivity and vprobe status as per Step 1 under No single resource was discovered..
  2. Verify that the poll metric data is persisted in the gateway database for the relevant app by executing:
    gcli> sdkgetvaluebystorename <app-name>_metrics

Gaps in metric graphs

  1. Verify the gateway connectivity and vprobe status as per Step 1 in “No single resource was discovered”.
  2. Verify the monitoring API as per Step 8 under No single resource was discovered.
  3. If the “App Failure Notification” checkbox is enabled in the app configuration, check whether an “App Failure Notification Alert” was generated during the time interval when the gaps were observed.
  4. If the checkbox is not enabled, enable it and observe for any failure notification alerts.