This is an IBM Automation portal for Cloud Management and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Set the `release` label for the `kube_pod_container_status_ready` metric (and any others that have it defined) to the value of the `release` label of the pod.
I'm working on some Grafana dashboards for monitoring MCM. We'd like to be able to filter based on the pod label named release. I notice in the Prometheus kube_pod_container_status_ready metric there is a release label. It looks like that may also be a label for other MCM metrics. The value of that label in the metric for all the pods I've looked at is always monitoring. I was expecting the value to be the value of the pod release label. It feels like the MCM metric code hardwired the metric label to monitoringrather than assigning the value of the pod label.
Do not place IBM confidential, company confidential, or personal information into any field.