Dynatrace ingests metrics for multiple preselected namespaces, including AWS Elemental MediaTailor. You can view graphs per service instance, with a set of dimensions, and create custom graphs that you can pin to your dashboards.
Prerequisites
To enable monitoring for this service, you need
An Environment or Cluster ActiveGate version 1.197+ Note: For role-based access (whether in a SaaS or Managed deployment), you need an Environment ActiveGate installed on an AWS EC2 host.
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 supporting service, a list of optional permissions specific to that 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.
Enable monitoring
To enable monitoring for this service, you first need to integrate Dynatrace with Amazon Web Services:
In the Dynatrace menu, go to Settings > Cloud and virtualization and select AWS.
On the AWS overview page, scroll down and select the desired AWS instance. Select the Edit button.
Scroll down and select Add service. Choose the service name from the drop-down and select Add service.
Select Save changes.
Cloud-service monitoring consumption
As of 2021, 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). For DDU consumption estimates per service instance (recommended metrics only, predefined dimensions, and assumed dimension values), see DDU consumption estimates per cloud service instance.
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 supporting services are filtered by tagging.
Filter by service name and select the relevant custom device group.
Once you select the custom device group, you're on the custom device group overview page.
The custom device group overview page lists all instances (custom devices) belonging to the group. Select an instance to view the custom device overview page.
View metrics on your dashboard
After you add the service to monitoring, a preset dashboard containing all recommended metrics is automatically listed on your Dashboards page. To look for specific dashboards, filter by Preset and then by Name. Note: For existing monitored services, you might need to resave your credentials for the preset dashboard to appear on the Dashboards page. To resave your credentials, go to Settings > Cloud and virtualization > AWS, select the desired AWS instance, and then select Save.
You can't make changes on a preset dashboard directly, but you can clone and edit it. To clone a dashboard, open the browse menu (…) and select Clone.
To remove a dashboard from the dashboards page, you can hide it. To hide a dashboard, open the browse menu (…) and select Hide. Note: Hiding a dashboard doesn't affect other users.
To check the availability of preset dashboards for each AWS service, see the list below.
The count of ads included in ad decision server (ADS) responses for the time period that you specified
Count
Sum
ConfigurationName
AdDecisionServer.Duration
The total duration, in milliseconds, of all ads that MediaTailor received from the ADS for the time period that you specified
Milliseconds
Average
ConfigurationName
AdDecisionServer.Errors
The number of non-HTTP 200 status code responses, empty responses, and timed-out responses that MediaTailor received from the ADS in the time period that you specified
Count
Sum
ConfigurationName
AdDecisionServer.FillRate
The simple average of the rates at which the responses from the ADS filled the corresponding individual ad avails for the time period that you specified
Count
Average
ConfigurationName
AdDecisionServer.Timeouts
The number of timed-out requests to the ADS in the time period that you specified
Count
Sum
ConfigurationName
AdNotReady
The number of times that the ADS pointed at an ad that wasn't yet transcoded by the internal transcoder service in the time period that you specified
Count
Sum
ConfigurationName
Avail.Duration
The total duration, in milliseconds, of all ad avails that MediaTailor encountered in the time period that you specified
Milliseconds
Average
ConfigurationName
Avail.FillRate
The simple average of the rates at which MediaTailor filled the individual ad avails for the time period that you specified
Count
Average
ConfigurationName
✔️
Avail.FilledDuration
The total duration, in milliseconds, of ad avail time that MediaTailor filled with ads in the time period that you specified
Milliseconds
Average
ConfigurationName
✔️
GetManifest.Errors
The number of errors received while MediaTailor was generating manifests in the time period that you specified
Count
Sum
ConfigurationName
Origin.Errors
The number of non-HTTP 200 status code responses and timed-out responses that MediaTailor received from the origin server in the time period that you specified
Count
Sum
ConfigurationName
Origin.Timeouts
The number of timed-out requests to the origin server in the time period that you specified
Count
Sum
ConfigurationName
Limitations
AdDecisionServer.FillRate and Avail.FillRate should be expressed in percentage, however, AWS reports it as a value from 0 to 1. They are defined for the time being as Count values.
