Feasibility of File-Based Telemetry Enrichment in OpenTelemetry Collector

[Vishnuvj07]

Our application currently emits telemetry that contains a groupid attribute. To improve observability and make dashboards easier for teams to interpret, we want to enrich telemetry with the corresponding Group Name.

We’ve evaluated doing this inside the application code, but the instrumentation pre-hooks do not have access to Group Names, and making additional queries from the application side is not ideal.

We want to explore implementing this enrichment inside the OpenTelemetry Collector, and we’d like feedback from the community on feasibility and best practices.

Our Constraints:

• No database or external network calls allowed for lookup
• Mapping must come from a JSON or YAML file
• 5000 group mappings (Group ID → Group Name)

JSON/YAML mapping file, e.g.:

{
"12345": "Acme Corp",
"67890": "Globex Inc",
...
}

Is there an existing processor or recommended alternative that supports external mapping files? Any feedback, examples, or guidance would be greatly appreciated.