Semantic Mapping Registry

The Semantic Mapping Registry is a centralized dictionary designed to align attribute naming conventions across diverse observability backends, eliminating semantic fragmentation at the edge.

Eliminating Telemetry Field Fragmentation

Different vendor backends parse different field names for the same attribute (e.g. service.name vs service_name vs application). The Semantic Mapping Registry compiles edge transformation rules to standardize attribute keys before data is ingested into your storage pipeline.

1. Vendor Naming Fragmentation Matrix

Standard Concept	OpenTelemetry Standard	Datadog	Splunk	Elastic	Coralogix (OTel-Native)
Service Name	`service.name`	`service`	`service_name`	`service.name`	`service.name`
Host Name	`host.name`	`host`	`host`	`host.name`	`host.name`
Log Body	`body`	`message`	`_raw`	`message`	`body`
Environment	`deployment.environment`	`env`	`environment`	`service.environment`	`deployment.environment`

2. Dynamic Attribute Translation Rules

When you configure mapping rules in the registry, CollectorCtrl automatically compiles OpenTelemetry transform and attributes processor definitions into your Fleet Policies:

transform-processor.yaml

processors:
transform:
  error_mode: ignore
  log_statements:
    - context: log
      statements:
        - set(attributes["service.name"], attributes["service"]) where attributes["service"] != nil
        - set(attributes["host.name"], attributes["host"]) where attributes["host"] != nil

3. CSV Bulk Schema Management

1. Export Mapping Dictionary

Export active semantic mappings as a CSV spreadsheet.

2. Edit Attributes in Bulk

Modify attribute mappings in bulk using Microsoft Excel or Google Sheets.

3. Import Updated Schema

Upload the modified CSV to immediately recompile transformation processors across all matching fleet nodes.