ServiceServicetypeA BTP service you subscribe to and bind, rather than install. It has plans and regions, not versions, and may deliver a product that lives outside the atlas.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →

Agent Activation for Dynatrace Service for SAP BTP

Injects the Dynatrace agent into Java applications on SAP BTP, so their metrics, events and end-to-end traces go to a Dynatrace SaaS monitoring environment the customer already runs.

A Java application on SAP BTP that should report to Dynatrace needs the Dynatrace agent inside its process and a connection to the customer's own monitoring environment. Agent Activation for Dynatrace Service for SAP BTP binds the Java applications in a subaccount to an existing Dynatrace SaaS monitoring environment, and once the service is configured the agent is injected into every application at its next restart. The agent collects metrics, events and end-to-end traces and sends them to that environment, which runs in data centres hosted by Dynatrace; tags and process group IDs of the Java processes are set with JVM arguments. It stops at the connection: it is described for Java applications only, and the monitoring environment is an existing one at Dynatrace, not something the service creates.

Retirement announcedThe regions the Discovery Center record marks as Neo, on the Standard plan's Cloud Credits entitlement for productive useThis Cloud Service, in the region/data center marked as "Neo", is being removed from the Eligible Cloud Services List on December 31, 2028 ("Retired Service").SAP Discovery Center — Agent Activation for Dynatrace Service for SAP BTP, plan availability

Where it sits

Lives in
Provides
TelemetryBTPTelemetrycapabilitySeeing what a running service did — traces across handlers and database calls, metrics, and correlation that survives an async boundary.

Who is behind it

SAPSAPOrganisationMaintains this
In the atlas: maintains 142, wrote 14
@SAP
maintainer

What it declares

Every artifact

Type
Service
Origin
By SAP

Connections1

Telemetry
  1. SAP Cloud LoggingOpenSearch-based store for logs, metrics and traces
  2. SAP Monitoring Service for SAP BTPMetrics, availability checks and alerts for apps in Neo regions
  3. @sap/e2e-traceSAP Passport handling for Node.js components
  4. @saptools/cf-metricsRead-only query tool for metrics in SAP Cloud Logging
  5. @saptools/cf-otelRead-only query tool for OpenTelemetry spans in SAP Cloud Logging

Details

Sources1
Added by handdiscovered herechecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainbtp, operations-and-runtime
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:btp-dynatrace-agent-activation
JSON
/artifacts/btp-dynatrace-agent-activation.json
MCP
Connecting an agent