Configure service detection for OneAgent in Service Detection v2

  • Latest Dynatrace
  • How-to guide
  • 4-min read
  • Published Apr 20, 2026
  • Early Access

Service Detection v2 (SDv2) for OneAgent is available as an Early Access release for Kubernetes and AWS Lambda services monitored by OneAgent. You need to manually activate this functionality in the Dynatrace web UI or via the Settings API.

Configuration scopes

You can activate SDv2 for Kubernetes and AWS Lambda services for the following configuration scopes:

  • Environment
  • Host group
  • Cluster
  • Namespace

Activate SDv2 for Kubernetes services

Dynatrace SaaS version 1.323+

SDv2 is available as an Early Access release for services that are running in Kubernetes and monitored by OneAgent. This feature is disabled by default, but you can activate SDv2 for your Kubernetes services in the Dynatrace web UI or via the Settings API (builtin:service-detection-v2-for-oneagent schema ID).

To activate SDv2 for Kubernetes workloads

  1. Navigate to the Service Detection v2 for OneAgent page for the required configuration scope.

    Environment

    Latest Dynatrace

    Go to Settings Settings > Process and contextualize > Services > Service Detection v2 for OneAgent.

    Dynatrace Classic

    Go to Settings > Service detection > Service Detection v2 for OneAgent.

    Host group

    Latest Dynatrace

    1. Go to Settings Settings.
    2. In the upper-left corner of the page, select Go to entity >, filter by Host group, and select the required host group.
    3. Go to Process and contextualize > Services > Service Detection v2 for OneAgent.

    Dynatrace Classic

    1. Go to Deployment Status Deployment Status > OneAgents.

    2. On the OneAgent deployment page, turn off Show new OneAgent deployments.

    3. In the Filter by field, enter Host group, and then select the host group you want to configure from the dropdown list.

      The host list is now filtered by the selected host group. Each listed host has a Host group: <group name> link, where <group name> is the name of the host group that you want to configure.

      The Host group property is not displayed when the selected host doesn't belong to any host group.

    4. Select the host group name in any row.

      As you have filtered by host group, all displayed hosts go to the same host group.

    1. Go to Service detection > Service Detection v2 for OneAgent.
    Cluster and namespace

    Latest Dynatrace

    1. Go to Kubernetes (new) Kubernetes.
    2. Find and select the required namespace or cluster.
    3. In the upper-right corner of the cluster or namespace pane, select (Actions menu) > Service detection settings. The Service detection page opens.
    4. Go to Process and contextualize > Services > Service Detection v2 for OneAgent.

    Dynatrace Classic

    1. Go to Kubernetes Kubernetes Classic.
    2. Find and select the required namespace or cluster.
    3. In the upper-right corner of the cluster or namespace overview page, select More (…) > Settings.
    4. Go to Service detection > Service Detection v2 for OneAgent.

  2. Turn on Enable Service detection v2 for Kubernetes workloads.

  3. Specify the required DQL matcher in Matching condition for Kubernetes workloads.

    This matching condition limits the scope of service detection by filtering Kubernetes workloads with the provided DQL matcher. The following attributes are allowed: resource attributes and custom attributes. For instance, you can use one of the following attributes to further restrict where the new SDv2 rules should be applied: dt.agent.module.type, k8s.cluster.name, k8s.namespace.name, k8s.workload.name, or dt.host_group.id.

    For example, to activate SDv2 only for the java language and the unguard namespace, use the following matching condition:

    dt.agent.module.type == "java" AND
    k8s.namespace.name == "unguard"

  4. Select Save changes.

You've activated SDv2 for the services that are running in Kubernetes and monitored by OneAgent.

Activate SDv2 for AWS Lambda services

Dynatrace SaaS version 1.337+

SDv2 is available as an Early Access release for AWS Lambda services monitored by OneAgent. This feature is disabled by default, but you can activate SDv2 for your AWS Lambda services in the Dynatrace web UI or via the Settings API (builtin:service-detection-v2-for-oneagent schema ID).

To activate SDv2 for AWS Lambda services

  1. Navigate to the Service Detection v2 for OneAgent page for the required configuration scope.

    Environment

    Latest Dynatrace

    Go to Settings Settings > Process and contextualize > Services > Service Detection v2 for OneAgent.

    Dynatrace Classic

    Go to Settings > Service detection > Service Detection v2 for OneAgent.

    Host group

    Latest Dynatrace

    1. Go to Settings Settings.
    2. In the upper-left corner of the page, select Go to entity >, filter by Host group, and select the required host group.
    3. Go to Process and contextualize > Services > Service Detection v2 for OneAgent.

    Dynatrace Classic

    1. Go to Deployment Status Deployment Status > OneAgents.

    2. On the OneAgent deployment page, turn off Show new OneAgent deployments.

    3. In the Filter by field, enter Host group, and then select the host group you want to configure from the dropdown list.

      The host list is now filtered by the selected host group. Each listed host has a Host group: <group name> link, where <group name> is the name of the host group that you want to configure.

      The Host group property is not displayed when the selected host doesn't belong to any host group.

    4. Select the host group name in any row.

      As you have filtered by host group, all displayed hosts go to the same host group.

    1. Go to Service detection > Service Detection v2 for OneAgent.
    Cluster and namespace

    Latest Dynatrace

    1. Go to Kubernetes (new) Kubernetes.
    2. Find and select the required namespace or cluster.
    3. In the upper-right corner of the cluster or namespace pane, select (Actions menu) > Service detection settings. The Service detection page opens.
    4. Go to Process and contextualize > Services > Service Detection v2 for OneAgent.

    Dynatrace Classic

    1. Go to Kubernetes Kubernetes Classic.
    2. Find and select the required namespace or cluster.
    3. In the upper-right corner of the cluster or namespace overview page, select More (…) > Settings.
    4. Go to Service detection > Service Detection v2 for OneAgent.

  2. Turn on Enable Service detection v2 for FaaS.

  3. Specify the required DQL matcher in Matching condition for FaaS.

    This matching condition limits the scope of service detection by filtering services with the provided DQL matcher. The following attributes are allowed: resource attributes and custom attributes.

    The default matching condition is isNotNull(aws.region) AND isNotNull(aws.account.id).

  4. Select Save changes.

You've activated SDv2 for AWS Lambda services that are monitored by OneAgent.

Next steps

SDv2 for AWS Lambda services only works when the [Built-in] FaaS name service detection rule is enabled. You might want to check whether this rule is activated for your environment. For details, see Default service detection rules.

Related tags
Application Observability