AWS Step Functions

Dynatrace ingests metrics for multiple preselected namespaces, including AWS Step Functions. 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

an Environment or Cluster ActiveGate version 1.197+
Dynatrace version 1.200+
An updated AWS monitoring policy to include the additional AWS services.
To update the AWS IAM policy, use the JSON below.

Predefined policy in JSON

Download

{
   "Version": "2012-10-17",
   "Statement": [
      {
         "Sid": "VisualEditor0",
         "Effect": "Allow",
         "Action": [
            "ec2:DescribeInstances",
            "support:DescribeTrustedAdvisorCheckResult",
            "athena:ListWorkGroups",
            "elasticbeanstalk:DescribeEnvironmentResources",
            "appsync:ListGraphqlApis",
            "kinesis:ListStreams",
            "elasticbeanstalk:DescribeEnvironments",
            "ec2:DescribeVolumes",
            "support:DescribeTrustedAdvisorCheckSummaries",
            "kinesisanalytics:ListApplications",
            "codebuild:ListProjects",
            "datasync:ListTasks",
            "mediaconnect:ListFlows",
            "cloudformation:ListStackResources",
            "mediatailor:ListPlaybackConfigurations",
            "support:SearchForCases",
            "lambda:ListFunctions",
            "support:DescribeCases",
            "chatbot:DescribeSlackChannels",
            "transfer:ListServers",
            "cloudwatch:GetMetricStatistics",
            "support:DescribeAttachment",
            "chatbot:DescribeSlackWorkspaces",
            "workmail:ListOrganizations",
            "firehose:ListDeliveryStreams",
            "eks:ListClusters",
            "ec2:DescribeSubnets",
            "swf:ListDomains",
            "support:DescribeTrustedAdvisorCheckRefreshStatuses",
            "tag:GetResources",
            "dynamodb:ListTables",
            "qldb:ListLedgers",
            "sns:ListTopics",
            "dynamodb:ListTagsOfResource",
            "dax:DescribeClusters",
            "support:DescribeTrustedAdvisorChecks",
            "cloudwatch:ListMetrics",
            "cloudhsm:DescribeClusters",
            "storagegateway:ListGateways",
            "ec2:DescribeAvailabilityZones",
            "lambda:ListTags",
            "rds:DescribeDBInstances",
            "support:DescribeSeverityLevels",
            "cloudsearch:DescribeDomains",
            "rds:DescribeEvents",
            "dms:DescribeReplicationInstances",
            "route53:ListHostedZones",
            "events:ListEventBuses",
            "chatbot:DescribeChimeWebhookConfigurations",
            "ec2:DescribeSecurityGroups",
            "es:ListDomainNames",
            "rds:ListTagsForResource",
            "s3:ListAllMyBuckets",
            "ec2:DescribeVpcs",
            "opsworks:DescribeStacks",
            "kinesisvideo:ListStreams",
            "chatbot:DescribeSlackChannelConfigurations",
            "chatbot:GetSlackOauthParameters",
            "elastictranscoder:ListPipelines",
            "elasticloadbalancing:DescribeLoadBalancers",
            "autoscaling:DescribeAutoScalingGroups",
            "support:DescribeSupportLevel",
            "support:DescribeCaseAttributes",
            "elasticloadbalancing:DescribeInstanceHealth",
            "apigateway:GET",
            "workspaces:DescribeWorkspaces",
            "support:DescribeServices",
            "support:DescribeCommunications",
            "support:DescribeIssueTypes",
            "elasticloadbalancing:DescribeRules",
            "elasticache:DescribeCacheClusters",
            "fsx:DescribeFileSystems",
            "kafka:ListClusters",
            "cloudwatch:GetMetricData",
            "route53resolver:ListResolverEndpoints",
            "tag:GetTagKeys",
            "ec2:DescribeNetworkInterfaces",
            "elasticloadbalancing:DescribeListeners",
            "elasticmapreduce:ListClusters",
            "appstream:DescribeFleets",
            "elasticfilesystem:DescribeFileSystems",
            "ecs:ListClusters",
            "sqs:ListQueues",
            "logs:DescribeLogGroups",
            "elasticloadbalancing:DescribeTags",
            "mediaconvert:DescribeEndpoints",
            "ec2:DescribeNatGateways",
            "robomaker:ListSimulationJobs",
            "ec2:DescribeSpotFleetRequests",
            "mediapackage:ListChannels",
            "cloudfront:ListDistributions",
            "elasticloadbalancing:DescribeTargetHealth",
            "redshift:DescribeClusters",
            "mediapackage-vod:ListPackagingGroups",
            "mediapackage-vod:ListPackagingConfigurations",
            "sts:GetCallerIdentity",
            "rds:DescribeDBClusters",
            "directconnect:DescribeConnections"
         ],
         "Resource": "*"
      }
   ]
}

Add the service to monitoring

In order to view the service metrics, you must add the service to monitoring in your Dynatrace environment.

To add a service to monitoring

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.

Configure service metrics

Once you add a service, Dynatrace starts automatically collecting a suite of metrics for this particular service. These are recommended metrics.

Recommended metrics:

Are enabled by default
Can't be disabled
Can have recommended dimensions (enabled by default, can't be disabled)
Can have optional dimensions (disabled by default, can be enabled)

Apart from the recommended metrics, most services have the possibility of enabling optional metrics.

Optional metrics:

Can be added and configured manually

To add and configure metrics

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 to the Supporting services section and select Manage services.
To add a metric, select the service for which you want to add metrics.
Select Add metric.
From the menu, select the metric you want.
Select Add metric to add the metric to monitoring.
To configure a metric, select the Edit button associated to it.
Select Apply to save your configuration.

Import preset dashboards

Dynatrace provides preset AWS dashboards that you can import from GitHub to your environment's dashboard page. Once you download a preset dashboard locally, there are two ways to import it.

Import via Dynatrace web UI

On your Dynatrace dashboard page, select Edit and switch to Settings.
Select Advanced settings.
On the Dashboard settings menu, select Dashboard JSON.
Use Upload to choose and upload the dashboard JSON file that you want to import.

Import via Dynatrace API

Create an API token.
When creating the token, enable the Write configuration permission.
To import the dashboard, run the command below, replacing {DYNATRACE_HOST}, {DYNATRACE_TENANT}, {TOKEN}, and {PATH_TO_DASHBOARD} with your own values.

curl --location --request POST 'http://{DYNATRACE_HOST}/e/{DYNATRACE_TENANT}/api/config/v1/dashboards' \
--header 'Authorization: Api-Token {TOKEN}' \
--header 'Content-Type: application/json' \
--data-binary '{PATH_TO_DASHBOARD}'

For more information, see Dashboards API - POST a dashboard

step

Available metrics

Name	Description	Unit	Statistics	Dimensions	Recommended
ActivitiesFailed	The number of failed activities	Count	Sum	Region, ActivityArn	✔️
ActivitiesHeartbeatTimedOut	The number of activities that time out due to a heartbeat timeout	Count	Sum	Region, ActivityArn	✔️
ActivitiesScheduled	The number of scheduled activities	Count	Sum	Region, ActivityArn	✔️
ActivitiesStarted	The number of started activities	Count	Sum	Region, ActivityArn
ActivitiesSucceeded	The number of successfully completed activities	Count	Sum	Region, ActivityArn	✔️
ActivitiesTimedOut	The number of activities that time out on close	Count	Sum	Region, ActivityArn	✔️
ActivityRunTime	The interval, in milliseconds, between the time the activity starts and the time it closes	Milliseconds	Multi	Region, ActivityArn	✔️
ActivityScheduleTime	The interval, in milliseconds, for which the activity stays in the schedule state	Milliseconds	Multi	Region, ActivityArn
ActivityTime	The interval, in milliseconds, between the time the activity is scheduled and the time it closes	Milliseconds	Multi	Region, ActivityArn
ConsumedCapacity	The count of requests per second	Count	Sum	Region, ServiceMetric	✔️
ConsumedCapacity		Count	Sum	Region, APIName	✔️
ExecutionThrottled	The number of StateEntered events and retries that have been throttled	Count	Sum	Region, StateMachineArn	✔️
ExecutionTime	The interval, in milliseconds, between the time the execution starts and the time it closes	Milliseconds	Multi	Region, StateMachineArn	✔️
ExecutionsAborted	The number of aborted or terminated executions	Count	Sum	Region, StateMachineArn	✔️
ExecutionsFailed	The number of failed executions	Count	Sum	Region, StateMachineArn	✔️
ExecutionsStarted	The number of started executions	Count	Sum	Region, StateMachineArn	✔️
ExecutionsSucceeded	The number of successfully completed executions	Count	Sum	Region, StateMachineArn	✔️
ExecutionsTimedOut	The number of executions that time out for any reason	Count	Sum	Region, StateMachineArn	✔️
LambdaFunctionRunTime	The interval, in milliseconds, between the time the Lambda function starts and the time it closes	Milliseconds	Multi	Region, LambdaFunctionArn	✔️
LambdaFunctionScheduleTime	The interval, in milliseconds, for which the Lambda function stays in the schedule state	Milliseconds	Multi	Region, LambdaFunctionArn
LambdaFunctionTime	The interval, in milliseconds, between the time the Lambda function is scheduled and the time it closes	Milliseconds	Multi	Region, LambdaFunctionArn
LambdaFunctionsFailed	The number of failed Lambda functions	Count	Sum	Region, LambdaFunctionArn	✔️
LambdaFunctionsScheduled	The number of scheduled Lambda functions	Count	Sum	Region, LambdaFunctionArn	✔️
LambdaFunctionsStarted	The number of started Lambda functions	Count	Sum	Region, LambdaFunctionArn
LambdaFunctionsSucceeded	The number of successfully completed Lambda functions	Count	Sum	Region, LambdaFunctionArn	✔️
LambdaFunctionsTimedOut	The number of Lambda functions that time out on close	Count	Sum	Region, LambdaFunctionArn	✔️
ProvisionedBucketSize	The count of available requests per second	Count	Multi	Region, ServiceMetric
ProvisionedBucketSize		Count	Multi	Region, APIName
ProvisionedRefillRate	The count of requests per second that are allowed into the bucket	Count	Multi	Region, ServiceMetric
ProvisionedRefillRate		Count	Multi	Region, APIName
ServiceIntegrationRunTime	The interval, in milliseconds, between the time the service task starts and the time it closes	Milliseconds	Multi	Region, ServiceIntegrationResourceArn	✔️
ServiceIntegrationScheduleTime	The interval, in milliseconds, for which the service task stays in the schedule state	Milliseconds	Multi	Region, ServiceIntegrationResourceArn
ServiceIntegrationTime	The interval, in milliseconds, between the time the service task is scheduled and the time it closes	Milliseconds	Multi	Region, ServiceIntegrationResourceArn
ServiceIntegrationsFailed	The number of failed service tasks	Count	Sum	Region, ServiceIntegrationResourceArn	✔️
ServiceIntegrationsScheduled	The number of scheduled service tasks.	Count	Sum	Region, ServiceIntegrationResourceArn	✔️
ServiceIntegrationsStarted	The number of started service tasks	Count	Sum	Region, ServiceIntegrationResourceArn
ServiceIntegrationsSucceeded	The number of successfully completed service tasks	Count	Sum	Region, ServiceIntegrationResourceArn	✔️
ServiceIntegrationsTimedOut	The number of service tasks that time out on close	Count	Sum	Region, ServiceIntegrationResourceArn	✔️
ThrottledEvents	The count of requests that have been throttled	Count	Sum	Region, ServiceMetric	✔️
ThrottledEvents		Count	Sum	Region, APIName	✔️

Limitations

Dynatrace gathers metrics for AWS Step Functions at the custom device group level instead of the custom device level (metrics are service-wide).