Cloud Management and AIOps


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).

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 updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

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.

Add a new idea Subscribe
Status Future consideration
Workspace Instana
Categories Kubernetes Sensor
Created by Guest
Created on Jan 26, 2024

RELATED IDEAS

Selective discovery of Prometheus sensor in Kubernetes Clusters

When deploying the Prometheus sensor to Kubernetes it tries to discover prometheus metrics endpoints from every service. This can lead to increased load and logs created by services that do not provide fitting metrics endpoints.

When deploying the Prometheus sensor outside of Kubernetes it's required to configure hostnames as targets. Similar to this it should be possible to be more selective in a Kubernetes cluster. It should be possible to select services based on label and/or namespace.


This way a team could decide if their service should be discovered by Instana.

This would also help in case different endpoints would be required for different services. This would currently double the number of discovery requests and therefore the number of logs.

Idea priority Medium
  • Guest
    Reply
    |     Aug 7, 2024

    Most of our self-developed services don't provide a metric endpoint. We wanted to use the sensor for a third party services mainly. If we were to widely use Prometheus for our services, we'd make sure the endpoints are identical.


    But yes, identifying relevant services based on a specific label should work for us.

  • Admin
    Jayanth Putta
    Reply
    |     Aug 6, 2024

    Hi @Guest!

    To dig into this further, do you have examples of how the metric endpoints look for different services? Based on the description, it seems like these are not homogenous for you.

    And do you tag services with specific labels based on the team responsible for those services?

  • Admin
    Martin Fuentes
    Reply
    |     Jul 1, 2024

    Hi Henning,

    Thanks for bringing this idea to our attention, we will come back to it in the near future.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.