This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation 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).
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:
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 updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
The intent of prometurbo is to query for custom metrics across the scope of all metrics in a single prometheus instance and we cannot try to logically merge or de-deduplicate that queries that are set on a project or namespace if the queries are pulling the same data. There are also potential performance considerations.
Eva,
I think the idea is that I would like my customers to create the PrometheusQueryMapping with their deployments since those queries are going to be custom with their application. Ideally we would like to keep all the resources they create in a namespace that they own.
For example below is just a test manifest of a deployment to a namespace turbo-horiz-metric
Well if you look at the PrometheusQueryMapping resource it has to be in turbonomic namespace and we would really like for that to be in any namespace. This way we don't have to give our users access to the turbonomic namespace. Correct me if I am wrong but the operator looking at that kind is bound to turbonomic namespace, and what we would like to see is the operator able to pick that up from any namespace.
Happy to discuss.
@Bosheng and @jason - I do not understand the ask as written. Please clarify.
What metric needs to be in the Turbo namespace?
Or is this an enhancement on the Prometurbo configuration? If yes please specify the details.