Amazon Application and Network Load Balancer (built-in)
Dynatrace ingests metrics for multiple preselected namespaces, including Amazon Application and Network Load Balancer. You can view metrics for each service instance, split metrics into multiple dimensions, and create custom charts that you can pin to your dashboards.
Prerequisites
To enable monitoring for this service, you need:
-
Any version of ActiveGate in both Dynatrace SaaS and Managed deployments.
-
An updated AWS monitoring policy to include the additional AWS services.
To update the AWS IAM policy, use the JSON below, containing the monitoring policy (permissions) for all cloud services.
If you don't want to add permissions to all services, and just select permissions for certain services, consult the table below. The table contains a set of permissions that are required for all services (All monitored Amazon services) and, for each cloud service, a list of optional permissions specific to that service.
Example of JSON policy for one single service.
In this example, from the complete list of permissions you need to select
"apigateway:GET"for Amazon API Gateway"cloudwatch:GetMetricData","cloudwatch:GetMetricStatistics","cloudwatch:ListMetrics","sts:GetCallerIdentity","tag:GetResources","tag:GetTagKeys", and"ec2:DescribeAvailabilityZones"for All monitored Amazon services.
To disable monitoring of built-in services you need:
- ActiveGate version 1.245+, Dynatrace version 1.247+
Enable monitoring
To enable monitoring for this service, you need to integrate Dynatrace with Amazon Web Services:
Add the service to monitoring
To view service metrics, the service needs to be monitored in your Dynatrace environment.
This is a built-in service. It’s monitored out-of-the-box once a new AWS integration instance is created. For built-in services, all metrics are recommended (changing configuration is not possible).
- In the Dynatrace menu, go to Settings and select Cloud and virtualization > AWS.
- On the AWS overview page, select the Edit
icon for the AWS instance. - Under Services, select Manage services.
- Select Add service, choose the service from the list, and select Add service.
- Select Save changes.
All cloud services consume Davis data units (DDUs). The amount of DDU consumption per service instance depends on the number of monitored metrics and their dimensions (each metric dimension results in the ingestion of 1 data point; 1 data point consumes 0.001 DDUs).
Monitor resources based on tags
You can choose to monitor resources based on existing AWS tags, as Dynatrace automatically imports them from service instances. Nevertheless, the transition from AWS to Dynatrace tagging isn't supported for all AWS services. Expand the table below to see which cloud services are filtered by tagging.
To monitor resources based on tags
- In the Dynatrace menu, go to Settings and select Cloud and virtualization > AWS.
- Select the Edit icon for the AWS instance.
- Set Resources to be monitored to Monitor resources selected by tags.
- Enter key/value pairs to identify resources to exclude from monitoring or include in monitoring.
You can enter multiple key/value pairs: each time you enter a pair, another empty row is displayed for you to edit as needed. - Select Save to save your configuration.
View service metrics
You can view the service metrics in your Dynatrace environment either on the AWS account page or on your Dashboards page.
View metrics on the AWS account page
To view metrics on the AWS account page
- In the Dynatrace menu, go to Infrastructure > AWS
- Choose AWS account you want to check metrics for.
- Select Service box. Metrics for the selected service are visible under the infographic in the service section.
View metrics on the Dashboard
You can also create your own dashboard. For more information on how to create dashboards, go to Create and edit Dynatrace dashboards
Example of AWS built-in monitoring service
Available metrics
Application Load Balancer metrics
| Metric key | Name | Unit | Aggregations | Monitoring consumption |
|---|---|---|---|---|
| builtin:cloud | ALB number of active connections | Count | autoavgmaxmin | DDUs |
| builtin:cloud | ALB number of new connections | Count | autovalue | DDUs |
| builtin:cloud | ALB number of 4XX errors | Count | autovalue | DDUs |
| builtin:cloud | ALB number of 5XX errors | Count | autovalue | DDUs |
| builtin:cloud | ALB number of 4XX target errors | Count | autovalue | DDUs |
| builtin:cloud | ALB number of 5XX target errors | Count | autovalue | DDUs |
| builtin:cloud | ALB number of rejected connections | Count | autovalue | DDUs |
| builtin:cloud | ALB number of target connection errors | Count | autovalue | DDUs |
| builtin:cloud | ALB number of client TLS negotiation errors | Count | autovalue | DDUs |
| builtin:cloud | ALB number of processed bytes | Count | autovalue | DDUs |
| builtin:cloud | ALB number of consumed LCUs | Count | autovalue | DDUs |
| builtin:cloud | ALB number of requests | Count | autovalue | DDUs |
| builtin:cloud | ALB target response time | Second | autoavgmaxmin | DDUs |
Network Load Balancer metrics
| Metric key | Name | Unit | Aggregations | Monitoring consumption |
|---|---|---|---|---|
| builtin:cloud | NLB number of active flows | Count | autoavgmaxmin | DDUs |
| builtin:cloud | NLB number of new flows | Count | autovalue | DDUs |
| builtin:cloud | NLB number of client resets | Count | autovalue | DDUs |
| builtin:cloud | NLB number of resets | Count | autovalue | DDUs |
| builtin:cloud | NLB number of target resets | Count | autovalue | DDUs |
| builtin:cloud | NLB number of processed bytes | Count | autovalue | DDUs |
| builtin:cloud | NLB number of consumed LCUs | Count | autovalue | DDUs |