Skip to Main Content
Cloud Management and AIOps

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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Is a defect
Workspace Instana
Categories Agent
Created by Guest
Created on Feb 20, 2023
Merged idea
This idea has been merged into another idea. To comment or vote on this idea, please visit INSTANA-I-1147 Instana Mode set as IQM not be defaulted back to APM on machine reboot.

IQM mode changing to APM on machine reboot Merged

We were doing our monthly patching on mongo machines where the Instana mode was showing as IQM in GUI of Instana and on the machine console as well.
[ec2-user@mng3~]$ sudo cat /opt/instana/agent/etc/instana/com.instana.agent.main.config.Agent.cfg
# Internal Instana Agent configuration.
scheduler.threads = 4
http.threads = 4
use-cloud-provider-id = true
mode = infrastructure

After our monthly patching and machine reboot the APM was changed from IQM to APM

[ec2-user@mng3~]$ sudo cat /opt/instana/agent/etc/instana/com.instana.agent.main.config.Agent.cfg
# Internal Instana Agent configuration.
scheduler.threads = 4
http.threads = 4
use-cloud-provider-id = true
[ec2-user@mng3~]$ uptime
12:26:52 up 4 min, 1 user, load average: 0.08, 0.16, 0.09

We would like to file this case as a bug and if how we can persist the mode even if machine reboot.

Idea priority Urgent