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 Submitted
Workspace Instana
Categories Backend Enablement
Created by Guest
Created on May 6, 2024

Instana agent and ui-backend proxy settings with no proxy var or proxy config per backend

We are trying to send our instana agent to a 2nd backend on your saas for testing a feature. But our kubernetes agents are getting timeouts to your endpoint. I assume it has to do with our network setup and that our proxy has to be used to reach your saas endpoint. On our single datastore ec2 the agent is able to send to both backends without any new configuration but the ones running on kubernetes do not. On the single host there is a no proxy for our own backend but yours should run via our proxy. On kubernetes this config of the nodes does not seem to apply so i tried with applying the values via the helmchart and via the env vars in the chart. https://github.com/instana/helm-charts/tree/main/instana-agent#configuring-a-proxy-between-the-instana-agents-and-the-instana-backend


But this leads to all backends using this proxy and our own backend becomes unreachable and since it is the primary only errors are logged that it is not reachable.
The same does apply to for ui-backend to send alerts to external and internal webhooks

Idea priority Medium