Skip to Main Content
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.

Status Needs more information
Workspace Instana
Created by Guest
Created on Jun 17, 2025

Consistent Proxy Support Across All Instana Agent Sensors via configuration.yaml and Environment Variables

While some Instana agent sensors, such as the AWS sensor, already support proxy configuration, this functionality is not consistently available across all sensors. In particular, sensors like Prometheus do not currently support proxy settings, either through configuration.yaml or standard environment variables (http_proxy, https_proxy, no_proxy).

This inconsistency causes issues in environments where outbound traffic must go through a corporate HTTP proxy. For example, in our case, we are attempting to monitor a Prometheus endpoint exposed by Confluent Cloud (Kafka), which requires proxy access. Due to the Prometheus sensor lacking proxy support, the agent consistently fails with connection timeouts, making this integration unusable in restricted environments.

Proposal:
Introduce consistent proxy support across all agent sensors by:

Allowing proxy configuration in the configuration.yaml for each sensor.

Supporting standard environment variables (http_proxy, https_proxy, no_proxy) as a fallback.

Benefits:

Ensures a uniform experience across all sensors.

Enables monitoring of cloud services in proxy-restricted or secured enterprise environments.

Reduces implementation barriers for customers in regulated industries.

Aligns with common enterprise networking policies without needing special exceptions.

Idea priority High