Frequently Asked Questions

Where can I find the list of Cloud services that generate metrics?

You can find information about the services that generate metrics in the following documentation topic: Cloud services.

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 Monitoring's hosted service may fail.

You must upgrade all monitoring agents to 10.5. Learn more.

How can I find out the metrics that are collected per agent?

In IBM Cloud Monitoring, you can monitor your monitoring agent by using the dashboard template monitoring agent Health & Status that is available in Host Infrastructure. In this dashboard, you can see the number of monitoring agents that are deployed and connected to the monitoring instance, check the version of the monitoring agents, and find out how many metrics per host the agent is collecting.

Can IBM Cloud Monitoring and IBM Cloud Security and Compliance Center Workload Protection be used together?

The IBM Cloud Monitoring and IBM Cloud Security and Compliance Center Workload Protection services can be configured so operational performance monitoring and security vulnerability monitoring data can be obtained from a single monitoring agent running in your orchestrated and non-orchestrated environment.

You need to consider the following when connecting the two services:

• You can connect only one IBM Cloud Monitoring instance to one IBM Cloud Security and Compliance Center Workload Protection instance.

• The connected IBM Cloud Monitoring and IBM Cloud Security and Compliance Center Workload Protection instances must be in the same account and region.

• Once connected, a single monitoring agent will provide data to both IBM Cloud Monitoring and IBM Cloud Security and Compliance Center Workload Protection connected instances.

• Once connected, the only way to disconnect the service instances is to delete either the IBM Cloud Monitoring or IBM Cloud Security and Compliance Center Workload Protection service instance.

To provision connected services, see Provisioning an instance.

The Graduated Tier - Sysdig Secure + Monitoring plan is deprecated. How do I keep using Workload Protection functionality?

On 18 January 2024 the IBM Cloud Monitoring Graduated Tier - Sysdig Secure + Monitoring service plan is deprecated. If you have IBM Cloud Monitoring instances currently using the Graduated Tier - Sysdig Secure + Monitoring plan, you can continue creating instances using the Graduated Tier - Sysdig Secure + Monitoring plan until 18 August 2024. New IBM Cloud Monitoring users will be unable to create instances using the Graduated Tier - Sysdig Secure + Monitoring plan after 18 February 2024.

Existing users of the Graduated Tier - Sysdig Secure + Monitoring plan will need to migrate to an independent instance of IBM Cloud Security and Compliance Center Workload Protection by 18 August 2024. On 18 August 2024, any remaining IBM Cloud Monitoring instances will be downgraded to the Graduated Tier plan. Users can continue to connect these instances to new IBM Cloud Security and Compliance Center Workload Protection instances until the end-of-service of the Graduated Tier – Sysdig Secure + Monitoring plan on 18 January 2025.

New users can provision connected instances of IBM Cloud Monitoring and IBM Cloud Security and Compliance Center Workload Protection so operational performance monitoring and security vulnerability monitoring data can be obtained from a single monitoring agent running in your orchestrated and non-orchestrated environment.