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.
See this idea on ideas.ibm.com
Dear Instana Team,
We would like to request native support for Azure App Service running PHP applications. Our current workaround involves installing the Instana agent in the startup script as a Linux agent. This approach is not convenient for our operations and significantly impacts efficiency.
The main challenges we face with the current setup include:
Agent Recycling: The agent is recycled on each Azure App Service restart or scaling in and out operations, which results in spawning a new instance with a different name. This makes it difficult to track and monitor the lifecycle of each App Service container effectively.
Agent Identification: Since the agents follow hostnames by default—over which we have no control—it becomes challenging to determine which agent corresponds to which application.
If native support cannot be provided immediately, we would appreciate:
A method to instruct the agent to reuse the same log space created by a previously destroyed agent, ensuring continuity in monitoring and tracking.
The ability to name agents explicitly, allowing for better identification and management across applications.
Your assistance in addressing these issues will greatly enhance our operational efficiency and monitoring capabilities.
Looking forward to your response.
Idea priority | Urgent |
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.