---
name: monitoring-troubleshoot
title: Troubleshooting for IBM Cloud Monitoring
description: Learn more about some general problems that you might encounter when you use the IBM Cloud Monitoring service. In many cases, you can recover from these problems by following a few easy steps.
last-updated: 2025-05-22
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/monitoring?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Troubleshooting for IBM Cloud Monitoring
{: #troubleshoot}

Learn more about some general problems that you might encounter when you use the IBM Cloud Monitoring service. In many cases, you can recover from these problems by following a few easy steps.
{: shortdesc}

## Are you getting an error when you create a capture?
{: #troubleshoot-entry-1}

You are failing to create a [capture file](https://cloud.ibm.com/docs/monitoring?topic=monitoring-captures&format=markdown#captures) 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.
{: tsSymptoms}

The monitoring agent that runs on the host has the feature **sysdig_capture_enabled** set to *false*.
{: tsCauses}

Enable the **sysdig_capture_enabled** feature in the monitoring agent that runs on the host.
{: tsResolve}


## Is the status of your capture file set to *requested* and does not change to status *uploaded*?
{: #troubleshoot-entry-2}

The status of a [capture file](https://cloud.ibm.com/docs/monitoring?topic=monitoring-captures&format=markdown#captures) 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*.
{: tsSymptoms}

The host has the TCP port 6443 disabled.
{: tsCauses}


Check that port 6443 is opened. For more information, see [Managing network traffic](https://cloud.ibm.com/docs/monitoring?topic=monitoring-service-connection&format=markdown)
{: tsResolve}


## Are you seeing errors when there are no problems?
{: #troubleshoot-entry-3}

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](https://docs.sysdig.com/en/sysdig-agent-release-notes.html).

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 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?
{: #troubleshoot-entry-4}

When the authorization method that is allowed in an 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](https://cloud.ibm.com/docs/monitoring?topic=monitoring-iam_instance_auth&format=markdown#iam_instance_auth_step1).

Then, review [Headers for IAM Tokens](https://cloud.ibm.com/docs/monitoring?topic=monitoring-mon-curl&format=markdown#mon-curl-headers-iam) and [Token headers](https://cloud.ibm.com/docs/monitoring?topic=monitoring-mon-curl&format=markdown#mon-curl-headers-monitoring) before you retry the request.

## Are your dashboards, alerts, and scripts no longer returning what you intended?
{: #troubleshoot-entry-5}

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 the [Metrics Store Release notes](https://docs.sysdig.com/en/release-notes/enhanced-metric-store/){: external} for details about the new metric store.

## Where is the topology map?
{: #troubleshoot-entry-6}

With the IBM Cloud Monitoring change to the metrics store, the topology map has been deprecated. See the [Metrics Store Release notes](https://docs.sysdig.com/en/release-notes/enhanced-metric-store/){: external} for details about the new metric store.