• Home
  • Manage
  • Monitoring consumption
  • Extending Dynatrace (Davis data units)
  • DDUs for serverless functions

DDUs for serverless functions

Dynatrace monitors serverless compute technologies through integration with cloud platform providers and tracing integrations.

Metrics captured from cloud provider integrations

Cloud services (including serverless functions and serverless containers) that are monitored using cloud vendor integrations for Amazon CloudWatch, Azure Monitor, or Google Cloud Operation Suite typically consume custom metrics. For details, see DDUs for custom metrics.

Application and platform Logs

Dynatrace allows for the ingestion of log files from your serverless cloud services, which consumes Davis data units. For details, see DDUs for log files.

AWS Lambda tracing

For AWS Lambda tracing integration, monitoring consumption is based on Davis data units. Dynatrace counts the total number of invocations (for example, requests) of the monitored functions. For each invocation, .002 DDUs are deducted from your available quota.

For example, if you monitor 1 function and that function is invoked 1 million times, DDU consumption will be calculated as follows: 1 function x 1 million invocations x 0.002 DDU weight = 2,000 DDUs per month per function.

Azure Function tracing

Azure Functions provide many different hosting options, with different tracing integration possibilities. Tracing Azure Functions on the App Service (Dedicated) plan consumes host units.

For Tracing Azure Functions on consumption plan, monitoring consumption is based on Davis data units. Dynatrace counts the total number of invocations (for example, requests) of the monitored functions. For each invocation, .002 DDUs are deducted from your available quota.

For example, if you monitor 1 function and that function is invoked 1 million times, DDU consumption will be calculated as follows: 1 function x 1 million invocations x 0.002 DDU weight = 2,000 DDUs per month per function.

Google Functions tracing

For Google Functions tracing, monitoring consumption is based on Davis data units. Dynatrace counts the total number of invocations (for example, requests) of the monitored functions. For each invocation, .002 DDUs are deducted from your available quota.

For example, if you monitor 1 function and that function is invoked 1 million times, DDU consumption will be calculated as follows: 1 function x 1 million invocations x 0.002 DDU weight = 2,000 DDUs per month per function.

Tracing integrations with application-only monitoring

Tracing serverless compute services such as Azure container instances or AWS Fargate consumes host units. For more information, see Serverless functions.

For details on host unit calculation and monitoring consumption for serverless monitoring using Application-only monitoring – including PaaS and some Serverless.

Related topics
  • Dynatrace pricing
  • Monitoring consumption

    Understand how Dynatrace monitoring consumption is calculated based on various types of monitoring units that are consumed by your Dynatrace environment during the course of monitoring.

  • Extending Dynatrace (Davis data units)

    Understand how Dynatrace monitoring consumption is calculated based on Davis data units (DDU).

  • DDUs for metrics

    Understand how to calculate Davis data unit consumption and costs related to monitored metrics.

  • Extend metric observability

    Learn how to extend metric observability in Dynatrace.