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 (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.


Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
  • Cloud Pak for Multicloud Management

  • Cloud Pak for Network Automation - including Orchestration and Performance Management

  • Cloud Pak for Watson AIOps - including Netcool Operations Management portfolio

  • Edge Application Manager

  • IBM Observability with Instana

  • ITM-APM Products - including IBM Tivoli Monitoring v6 and Application Performance Monitoring v8

  • Workload Automation - including Workload Scheduler

  • Tivoli System Automation - including Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)

  • Tivoli Application Dependency Discovery Manager - TADDM


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 Delivered
Workspace Instana
Categories Other Tracers
Created by Guest
Created on Jul 29, 2022

Don't aggregate different SQL statements or always do it in the same way

A part of my application makes a series of SQL calls (4 inserts and 2 updates, on different tables). I want to monitor how many times the first of these calls is made (or the whole series, it's equivalent) for business and application performance purposes. However the calls are sometimes auto-aggregated (https://www.ibm.com/docs/en/instana-observability/current?topic=applications-analyzing-traces-calls#automatic-aggregation-of-short-exit-calls) and sometimes not. Therefore if I make a graph counting the SQL call I'm interested in, one call to my web service sometimes appears as one SQL call and sometimes as 6: the numbers are meaningless!

Ideally, for my purpose, the calls should not be aggregated, so I can count only the one I'm interested in.

However I see in the help that aggregation occurs based on "High frequent and repetitive access patterns of similar type". The calls made by my app are indeed always the same 6 statements on the same tables (with different data). If Instana recognizes this and groups them, it could be fine if they were always grouped. Then the count would be consistently inflated 6 times and the graph would be perfectly readable. Or if Instana recognized that the pattern was always the same if could then show it in full in the traces even with some data dropped.

Idea priority Medium
  • Admin
    Yinchi Luo
    Sep 14, 2022

    Yes, in this case it should not be a problem.

  • Guest
    Sep 14, 2022

    When you say "per trace", that means for a single call to a given endpoint?

    Currently I've seen batches of up to 6 SQL statements and traces with like a dozen mongo or sql statements. Small enough in your opinion?

  • Admin
    Yinchi Luo
    Sep 14, 2022

    A restart should be enough.

    I do not see it would greatly impact application performance. But if you have huge amount of sql statement per trace, then you might want to try it on your test environment first.

  • Guest
    Sep 14, 2022

    Thank you. With a restart we don't need to wait 10 minutes, correct?

    Is there a chance that this would impact application performance? Would you say that this warrants performance testing?

  • Admin
    Yinchi Luo
    Sep 14, 2022

    Hi, the option to disable span batching for Java is released, here is the instruction:

    Disabling batching

    Span batching can be disabled with the below configuration

    com.instana.plugin.javatrace:
    instrumentation:
    spanBatchingEnabled: false

    This configuration needs a restart of the application or a complete reset of monitored applications in Agent(Agent need to be shut down for >10 minutes)

  • Guest
    Sep 7, 2022

    Yes, our app is a Java Spring Boot app accessing a MongoDB and an Oracle SQL databases. If there is a way to disable the aggregation in our case, I'd appreciate it.

  • Admin
    Yinchi Luo
    Sep 1, 2022

    Thanks for reaching out. Could you share which environment/language you are using? We do have certain features to disable such aggregation.