Today the service runtime dashboards are selected by the agent name (differentiating between classic Elastic APM Agents and OTel SDKs).
With the new ingestion path through the OTel collector the metrics data format is different and will require new runtime dashboards.
To achieve that we need a way to select the dashboard not only based on the agent.name but also through the ingestion path (i.e. through APM Server vs. through OTel Collector directly).
Service runtime metrics ingested through the OTel Collector will always have the field resource.attributes.service.name (plus service.name as alias), same metrics ingested through the APM server won't have the resource.attributes.service.name field, but only service.name.
Today the service runtime dashboards are selected by the agent name (differentiating between classic Elastic APM Agents and OTel SDKs).
With the new ingestion path through the OTel collector the metrics data format is different and will require new runtime dashboards.
To achieve that we need a way to select the dashboard not only based on the
agent.name
but also through the ingestion path (i.e. through APM Server vs. through OTel Collector directly).Service runtime metrics ingested through the OTel Collector will always have the field
resource.attributes.service.name
(plusservice.name
as alias), same metrics ingested through the APM server won't have theresource.attributes.service.name
field, but onlyservice.name
.