Why are service id's in log lines leading to unknown services in Kubernetes?

mreider — Wed, 17 Dec 2025 11:37:35 GMT

Sometimes, in the logs app, when I'm looking at the attributes of a log line, I see dt.entity.service with the service's entity ID and the Context menu (⋮) to "Open with" using that ID.

If I open the Services app, for instance, the service ID is invalid.

This occurs when:

The log is coming from a Kubernetes workload
The log is coming from a OneAgent instrumented service (SDv1)

What is happening and when will this be fixed?

Re: Why are the service id's in log lines leading to unknown services in k8s?

mreider — Mon, 01 Sep 2025 12:01:44 GMT

Answer

Service Linking Issue - Kubernetes Workloads Only

We recently introduced service linking functionality in the new Dynatrace SaaS experience. This feature adds an underlined link in log properties that shows all log attributes, including dt.entity.service (the calculated service ID).

Current Issue

The lookup service that calculates service IDs for services running in Kubernetes uses Service Detection v2 (SDv2). However, all OneAgent services currently use Service Detection v1 (SDv1). This mismatch causes the system to generate incorrect service IDs for OneAgent services running in Kubernetes.

Impact

When you click "Open With" to access the Services app, you'll see "Service not found" for OneAgent services.

The service linking feature currently works only for:

OpenTelemetry services (which use SDv2)
OneAgent Adobe Experience Manager (AEM) based services
OneAgent services targeted for SDv2 support
- Public preview coming soon
- Several caveats apply

We're developing a solution and will share details as we make progress.

topic Re: Why are the service id's in log lines leading to unknown services in k8s? in Container platforms

Why are service id's in log lines leading to unknown services in Kubernetes?

Re: Why are the service id's in log lines leading to unknown services in k8s?