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 Future consideration
Workspace Instana
Categories Sensor
Created by Guest
Created on Jan 27, 2026

Support for downstream call visibility for applications using both KafkaBatchListener (batch processing) and standard Kafka listeners (single record processing)

When com.instana.kafka.correlate.send.receive flag is set to true, downstream calls may not be captured for implementations using KafkaBatchListener.

We need simultaneous visibility into our application which uses both methods (KafkaBatchListener and standard Kafka listeners).

Using the instana.kafka.correlate.send.receive flag currently forces a trade-off where enabling one capability disables the other. Our services utilize multiple Kafka processing patterns (both batch and individual record processing), making JVM-level toggles or via ENV variable as in our case impractical.

Idea priority Medium
  • Admin
    Prashant Raj Singh
    May 26, 2026

    Hello,

    Thank you for sharing this request and the detailed context around your Kafka usage pattern.

    We understand that your application uses both KafkaBatchListener-based batch processing and standard Kafka listeners for single-record processing within the same JVM. The current Kafka send/receive correlation behavior can create a trade-off in this scenario, where enabling the correlation flag improves visibility for individual record processing but may impact downstream call visibility for batch-based processing.

    We agree that this is a valid observability gap for applications using mixed Kafka processing patterns. We are moving this request to Future Consideration while we further evaluate the best technical approach. As part of this evaluation, we will research whether span-link-style correlation or a similar model can help represent batch/asynchronous Kafka processing more accurately while preserving downstream call visibility.

    Based on the outcome of this research, we will determine the appropriate implementation direction and whether this can be prioritized in a future release.

    We truly value your feedback and appreciate you highlighting this use case. If you have additional implementation details, sample listener patterns, or trace examples, please feel free to share them, as they would help with our evaluation.

    Please note: IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion.