Service Detection v2
- Classic
- Overview
- 1-min read
Service Detection v2 (SDv2) operates according to a single set of rules that are based on attributes. This includes default rules, and you can additionally define your own custom rules. SDv2 rules are generally available for OpenTelemetry services; for services that are running in Kubernetes and monitored by OneAgent, SDv2 rules are available as a Preview release.
SDv2 is available as a Preview release for services that are running in Kubernetes and monitored by OneAgent. You can join this Preview release via the Service Detection v2 for OneAgent settings page.
- Go to
Kubernetes Classic. - Find and select your Kubernetes cluster. When required, also select the namespace.
- In the upper-right corner of the cluster or namespace overview page, select More (…) > Settings.
- Go to Service detection > Service Detection v2 for OneAgent.
- Turn on Enable Service detection v2 for Kubernetes workloads.
As part of the Preview release, you can use the following attributes to further restrict where the new SDv2 rules should be applied.
dt.agent.module.typek8s.cluster.namek8s.namespace.namek8s.workload.namedt.host_group.id
These are customized within your Kubernetes namespace or cluster settings.
Currently, Java is the only supported language, and you need to keep the default matching condition as dt.agent.module.type == "java". Support for additional languages is currently planned and will be announced via release notes.
SDv2 provides:
- Service detection and naming based on resource attributes and conditions.
- Endpoint detection based on span and resource attributes.
- Service splitting based on resource attributes.
- Failure detection based on HTTP or gRPC codes or other span and resource attributes.
SDv2 behavior can be configured via:
- The Dynatrace web UI, as described in the pages within this section.
- The Settings API.