Log Monitoring Classic
Dynatrace version 1.230+
DDU pricing applies to cloud Log Monitoring. See DDUs for Log Monitoring for details.
Stream or forward your logs from Amazon CloudWatch, AWS S3 or other AWS sources.
Dynatrace integration with Amazon Data Firehose provides a simple and safe way to ingest AWS logs.
To enable AWS log forwarding,
To learn more, see Stream logs via Amazon Data Firehose (Logs Classic).
You can stream logs from AWS S3 to Dynatrace using a serverless architecture.
The log forwarder offers:
For detailed instructions on how to set up log ingestion from AWS S3, see documentation on GitHub.
You can collect logs directly from your AWS Lambda functions and send them to Dynatrace for analysis. The solution is an alternative to the CloudWatch log forwarder with benefits in terms of cost and latency, and is also easier to set up, particularly if AWS Lambda tracing is already in place. As part of the OneAgent installation process, this feature provides a streamlined solution for collecting logs from your Lambda functions. For more information, see AWS Lambda documentation page.
You can stream logs from Amazon CloudWatch into Dynatrace logs via an ActiveGate.
To enable AWS log forwarding, you need to deploy our special-purpose CloudFormation stack into your AWS account. The stack consists of a Kinesis Firehose instance and a Lambda function. These resources incur AWS costs according to standard AWS billing policy. The same applies to included self-monitoring resources (CloudWatch dashboards and metrics).
For detailed instructions on how to set up AWS log forwarding, see Log monitoring with AWS log forwarder.
Dynatrace integration with Amazon Data Firehose provides a simple and safe way to ingest AWS logs.
To enable AWS log forwarding, you need to create Amazon Data Firehose instance and configure it with your Dynatrace environment as a destination. Then you can connect your CloudWatch log groups by creating a Subscription Filter or send logs directly to Firehose from services that support it (e.g. VPC flow logs). Firehose and other created cloud resources incur AWS costs according to the standard AWS billing policy.
Azure log forwarding allows you to stream Azure logs from Azure Event Hubs into Dynatrace logs via an Azure Function App instance. It supports both Azure resource logs and activity logs.
Azure log forwarding is performed directly through Cluster API. If you don't want to use direct ingest through the Cluster API, you have to use an existing ActiveGate for log ingestion.
Deployment of Azure log forwarder results in creating the following resources:
Microsoft.Storage/storageAccounts)Microsoft.Storage/storageAccounts/blobServices)Microsoft.Web/serverfarms)Microsoft.Web/sites)Azure log forwarder uses Linux based Azure function by default. Windows based function is not supported.
For details about the resources created, see the Azure Resource Manager file on GitHub
For detailed instruction on how to set up Azure log forwarding see, Azure Logs.
To set up Google Cloud monitoring for metrics and logs, you'll run the deployment script in Google Cloud Shell. During setup, a new Pub/Sub subscription will be created. GKE will run two containers: a metric forwarder and a log forwarder. After installation, you'll get metrics, logs, dashboards, and alerts for your configured services in Dynatrace. Instructions will depend on the location where you want the deployment script to run:
Depending on where you want log ingestion to be performed, you may need additional resources. For example, for Managed deployments, there is a possibility to use an AG for log ingestion. But you have to do it manually since the installation script does not deploy it.
For all log ingestion options, see Log ingestion.