Docs » Getting Started » Concepts » About the mapping service transition impact report

About the mapping service transition impact report 🔗

To make migration of your data and metadata from dashboards, charts, and detectors into OTel as seamless as possible, the application’s Mapping Service automatically translates collectd (Smart Agent) conventions into the syntax used by the Open Telemetry (OTel) collector.

Mapping applies OTel naming standards to the following components:

  • Metrics and Metric Time Series (MTSs)
  • Dimensions
  • Properties

For example, if you track CPU utilization for your Kubernetes pod, your analytics may use the legacy name kubernetes.container_cpu_limit. In this example, the mapping service will update your existing queries to include both legacy semantics and new semantics, meaning that you will also receive an equivalent metric called k8s.container.cpu_limit. The mapping service creates equivalencies between your Smart Agent and OpenTelemetry metric names with the appropriate semantic conventions for each. Both can be queried at any time.

Mapping logic treats any of the names for a metric or property as referring to that same metric or property, without tracking versions.

You can find a table outlining OTel values and their legacy equivalents in GitHub at: Legacy to OTel semantics mapping table

Whether you’re using the Smart Agent or OpenTelemetry Collector, your original dashboards and detectors will continue to function as they always have. Infrastructure Navigator views use the mapping service to show metrics captured by both the Smart Agent and the OpenTelemetry Collector.

If you decide as a Splunk admin to turn off the mapping service, you can still generate and download a Mapping and OTel Transition Impact Report specific to migration for your cloud computing environment.

You access the migration transition impact report through a Download button in the Billing and Usage > Usage Reports > OpenTelemetry Migration dialog.

Interpreting the mapping impact report 🔗

The Mapping and OTel Transition Impact Report summarizes the mapping changes associated with your migration to OpenTelemetry. It lists the tokens currently used as metric, dimension, property or tag names, and highlights migration rules that could generate conflicts during the mapping process.

The mapping impact report explains when migration from an old metric time series to a new metric time series (MTS) will trigger detectors, and which detectors those are. For example, heartbeat detectors working with un-aggregated MTSs are affected by design, but if a heartbeat detector is working with a dimension that continues across the transition to OTel, then the mapping service ensures continuity so that you do not have to restart that detector.

The mapping transition impact report assesses migration effects across three categories:

  • Data object types
  • Team responsibilities
  • Migration mitigation steps you should take

Data object type information 🔗

The mapping impact report explains migration impacts within your organization to the following object types:

  • Dashboards
  • Charts
  • Detectors

The report shows how many objects of each type are affected, and includes tables that show where to find the affected objects. You can read the report to see, for example, a list of all affected charts on a given dashboard or within a dashboard group.

Team information 🔗

The mapping impact report extracts information from your data set about the stakeholders of a particular metric. When applicable, the report shows the names of teams linked to particular detectors. The report also identifies people or teams linked to particular dashboard groups.

Migration mitigation steps 🔗

The mapping impact report explains what effect migration will have on the content highlighted in it, so that you can modify that content as needed to ensure a smoother transition.

Flagged items that need to be modified include the following (as listed in the report):

  • Wildcards used in a plot, filter, or function.
  • Direct references to Smart Agent metrics.
  • Filters that use Smart Agent dimensions.
  • Aggregates that use Smart Agent dimensions.

While the report highlights items that need revising because they use legacy syntax or conventions, it also pairs those items with the OTel-based metrics and dimensions that you can use as substitutes.

The mapping transition impact report helps take guesswork out of migration tasks.