Skip to main content
Instrumentation bloat consists of fields added by SDKs, agents, collectors, and exporters. These fields describe the telemetry tooling rather than the observed system. Some instrumentation fields, such as service.name, are operational metadata for system identity and routing. Tooling metadata such as telemetry.sdk.version, otel.library.name, and collector build strings has low value in logs.

Signals

  • Fields that describe SDKs, agents, collectors, exporters, or instrumentation libraries.
  • Version fields for telemetry tooling.
  • Internal Kubernetes UIDs when human-readable Kubernetes names are also present.
  • Fields the telemetry pipeline adds on its own rather than fields from application code.
  • Fields you query only when debugging the telemetry tooling itself.

Example

Enforce at edge

Remove low-value instrumentation metadata before data leaves your network.
Use edge enforcement when telemetry tooling, not application code, adds the fields.

Detection notes

  • Tero maps dependencies and instrumentation metadata to distinguish tooling fields from application fields.
  • Tero flags fields such as telemetry.sdk.version and otel.library.name when they come from telemetry tooling.
  • It does not classify system identity fields such as service.name as instrumentation bloat.
  • Tero removes Kubernetes UID fields when it keeps the human-readable names.