You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're using the **OpenTelemetry Java Agent to automatically capture application logs (from stdout / logback) and send them directly to SigNoz via OTLP/gRPC.
Some of our logs contain lines like:[CLIFE-TRACE-LOG]|[2025-11-19 10:26:11:118]|[]|[10.244.96.85]
These are internal trace logs that we do not want to ingest — they generate high volume but no operational value.
Goal
Drop any log record whose body contains the literal string [CLIFE-TRACE-LOG]at the OpenTelemetry Collector level, before it reaches ClickHouse.
Question
Can we use the filter processor in SigNoz’s OTel Collector to exclude logs by substring match in body?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
We're using the **OpenTelemetry Java Agent to automatically capture application logs (from stdout / logback) and send them directly to SigNoz via OTLP/gRPC.
Some of our logs contain lines like:[CLIFE-TRACE-LOG]|[2025-11-19 10:26:11:118]|[]|[10.244.96.85]
These are internal trace logs that we do not want to ingest — they generate high volume but no operational value.
Goal
Drop any log record whose
bodycontains the literal string[CLIFE-TRACE-LOG]at the OpenTelemetry Collector level, before it reaches ClickHouse.Question
Can we use the
filterprocessor in SigNoz’s OTel Collector to exclude logs by substring match inbody?Beta Was this translation helpful? Give feedback.
All reactions