Too many a2a events caused langfuse clickhouse OOM

[Colstuwjx]

** Please make sure you read the contribution guide and file the issues in the right place. **
Contribution guide.

Describe the bug
When I'm trying to put the ADK app trace data to langfuse by OpenTelemetry, I've found that Langfuse would got too many a2a events and caused the clickhouse of langfuse OOM (20 million a2a trace data got in just 7 days, as a comparison, the other agent call trace data was just < 1 million rows)

To Reproduce
Steps to reproduce the behavior:

1. Install Google ADK with an a2a agent
2. Try to send all the traces to Langfuse via OpenTelemetry integration
3. Would see many a2a events and cause the Langfuse Clickhouse issue

Expected behavior
We would expect that the A2A traces should be a set of valid trace data rather than useless events.

Screenshots

Desktop (please complete the following information):

• OS: Linux
• Python version(python -V): 3.13
• ADK version(pip show google-adk): 1.10.0

Model Information:

Additional context

[llalitkumarrr]

Hello @Colstuwjx

From your description we understand that you are using older ADK version, we recommend trying new version i.e. google-adk==1.19.0. We would highly appreciate if you could try out new version and share you observations.

[adk-bot]

This issue has been automatically marked as stale because it has not had recent activity for 7 days after a maintainer requested clarification. It will be closed if no further activity occurs within 7 days.

[kftam1994]

it still happens in latest version 1.20.0 but I am not sure if it should be raised here

[llalitkumarrr]

Hello @kftam1994 ,

Please accept my apologies for the delay. Do you think this issue might be linked to Langfuse?

[kftam1994]

It is also raised in Langfuse
I eventually handled it with this filtering method
https://github.com/orgs/langfuse/discussions/8366#discussioncomment-14949887