Troubleshooting for IBM Cloud Monitoring

Are you getting an error when you create a capture?

You are failing to create a capture file for a host in your infrastructure.

In the Captures section of the web UI, you get an error when you try to create a capture file for a host.

The monitoring agent that runs on the host has the feature sysdig_capture_enabled set to false.

Enable the sysdig_capture_enabled feature in the monitoring agent that runs on the host.

Is the status of your capture file set to requested and does not change to status uploaded?

The status of a capture file is set to requested and does not change to status uploaded. You are waiting for the capture file to be available for analysis.

In the Captures section of the web UI, the status of the capture file for a host does not change to uploaded.

The host has the TCP port 6443 disabled.

Check that port 6443 is opened. For more information, see Managing network traffic

Are you seeing errors when there are no problems?

Are you observing monitoring agent connection errors or receiving uptime alerts reporting an host is down when there are no problems?

IBM Cloud Monitoring has identified an issue with a subset of agent versions:

• monitoring agent 10.3.0
• monitoring agent 10.3.1
• monitoring agent 10.4.0
• monitoring agent 10.4.1

Where connectivity between your infrastructure and the IBM Cloud Monitoring hosted service may fail. For more information, see Release Notes.

If you are experiencing connectivity issues, complete the following steps:

1. Check the version of the monitoring agent.

   You can view the dashboard template monitoring agent Health & Status that is available in Host Infrastructure to check the version of your monitoring agents.

2. Upgrade your monitoring agent to version 10.5 as soon as possible to ensure a reliable flow of metrics and data into our systems.

Are you getting access denied when running API calls?

When the authorization method that is allowed in a IBM Cloud Monitoring instance is set to IAM_ONLY, you can get the following response {"errors":[{"reason":"Not enough privileges to complete the action","message":"Access is denied"}]}.

First, check the instance authorization methods that are allowed.

Then, review Headers for IAM Tokens and Token headers before you retry the request.

Are your dashboards, alerts, and scripts no longer returning what you intended?

IBM Cloud Monitoring has changed its metrics store. This change has deprecated and changed a number of metrics and labels and has changed metric behavior. See Enhanced metric store for details on the new metric store.

Where is the topology map?

With the IBM Cloud Monitoring change the metrics store, the topology map has been deprecated. See Enhanced metric store for details on the new metric store.