topic Muting or Excluing endpoints for Services based on Trace Ingest (OTel API) in Dynatrace Classic in Open Q&A

Muting or Excluing endpoints for Services based on Trace Ingest (OTel API) in Dynatrace Classic

Fernando_Moreir — Fri, 29 May 2026 10:09:15 GMT

Hello everyone,

I am working with a service that is being monitored via Pure OpenTelemetry (Trace Ingest API). We are receiving traces correctly, but we need to exclude/mute specific health check endpoints (example: /api/health) to optimize license consumption and clean up the service view.

In services monitored by OneAgent, we usually have the Muting or Span capturing options under Service Settings, but these options menus seem to be missing for services based purely on Trace Ingest in the Classic interface.

Questions:

Is it currently possible to perform endpoint exclusion/muting for OTel-Ingested services directly within the Dynatrace Classic UI?
If not, is this a limitation by design for Trace Ingest, where filtering MUST be done at the source (example, OTel Collector using Filter Processor)?

Thanks in advance for your help!

Re: Muting or Excluing endpoints for Services based on Trace Ingest (OTel API) in Dynatrace Classic

sujit_k_singh — Fri, 29 May 2026 11:17:31 GMT

Hi @Fernando_Moreir

You're correct — Span capturing / muting options are not available in the Classic UI for services created purely via Trace Ingest (OTLP). This is a known limitation.

To answer your questions:

Can you mute/exclude endpoints for OTel-ingested services in Classic UI? No. The muting and span capturing settings under Server-side service monitoring → Span capturing only apply to OneAgent-instrumented services. For pure OTel Trace Ingest services, these options are not exposed in the Classic UI.

Is filtering at the source the only option? Yes — for now, filtering must be done at the OTel Collector level before data reaches Dynatrace. Use the Filter Processor in your Collector pipeline.

Thanks,

Sujit

Re: Muting or Excluing endpoints for Services based on Trace Ingest (OTel API) in Dynatrace Classic

Fernando_Moreir — Fri, 29 May 2026 13:22:30 GMT

Hi @sujit_k_singh

Thank you very much for the clear and definitive answer. It confirms my findings that filtering at the source (OTel Collector) is indeed the only robust way to handle this for OTLP-Ingested services in the Classic UI.

I've already advised the client to implement the Filter Processor as suggested.

Best Regards,

Fernando