Skip to Main Content
Cloud 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 User Interface
Created by Guest
Created on Jul 10, 2026

Expose Event ID Directly in the Instana UI and Event APIs

Problem Statement

When investigating events in Instana, the Event ID is not readily visible within the event details displayed in the user interface. Currently, users must extract the Event ID from the URL when viewing a specific event.

This creates unnecessary friction during operational workflows, especially when:

  • Sharing event references among teams (customer recognizes there is a shared link that can be generated, but for auditing an event ID is more meaningful)
  • Troubleshooting incidents
  • Integrating with automation workflows
  • Performing API-based investigations
  • Creating support cases requiring event identification

The Event ID exists and is available within the URL, but it is not surfaced as a visible field within the event details page itself. Users who are unaware of this behavior may have difficulty locating the identifier when needed.

Proposed Enhancement

Surface the Event ID directly within the Event Details UI.

Suggested capabilities:

  • Display Event ID as a dedicated field within the event details panel
  • Provide a one-click copy-to-clipboard option
  • Ensure the Event ID remains visible regardless of navigation method
  • Maintain consistency across event types

Additionally, as a secondary enhancement, expose the Event ID through relevant APIs where applicable to simplify automation and integration use cases.

Business Value

Simplify Incident Management

- Operations teams can quickly reference and communicate individual events without requiring users to inspect URLs or manually extract identifiers. 

Improve Troubleshooting Efficiency

- Support teams, administrators, and developers can more easily correlate UI-displayed events with API queries, logs, integrations, and support cases. 

Better User Experience

-Displaying important metadata in the UI reduces reliance on browser-specific behavior and makes event identification more intuitive for both new and experienced users. 

Enable Automation

- Making Event IDs easily accessible supports scripting, API workflows, integrations, and operational tooling that depend on unique event identifiers.

Idea priority Low