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 Future consideration
Workspace Instana
Categories Logging
Created by Guest
Created on May 12, 2023

instana ELK plugin is not working as expected if we use someother logshipper like vector

out setup

Instana version : 241

Elastic version 8.2

Kibana : Stack Management 8.2.3

vector: 0.27.0-debian

if I click on pod or container link as it launching the correct kibana dashboard without any logs as there are some issue in filter string it generate as below

Pods ELK link (double quotes are missing and should be pod_name):


Should be


Containers ELK link (double quotes are missing and shoudl be container_id) :

current string search = fd225deacbf17c984ed4c115a1a9203747b1cb263300a2c6f301c554285920bd

should be as below


Idea priority High
  • Admin
    Martin Fuentes
    Jun 14, 2023

    Hello Sumit,

    Thanks for bringing this idea to our attention. As you described, the integration with ELK does work as expected when the ELK stack is present. Replacing one of the components means a different stack to support.

    We will come back to this idea in the near future.