Amazon Simple Workflow Service (SWF)

Dynatrace ingests metrics for multiple preselected namespaces, including Amazon Simple Workflow Service (SWF). 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.201+
  • 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 supporting 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 supporting 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.

Enable monitoring

To enable monitoring for this service, you first need to integrate Dynatrace with Amazon Web Services:

Add the service to monitoring

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

Cloud-service monitoring consumption

Beginning in early 2021, all cloud services will 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 for 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.

To monitor resources based on tags

  1. Go to Settings > Cloud and virtualization > AWS and select the AWS instance.
  2. For Resource monitoring method, select Monitor resources based on tags.
  3. Enter the Key and Value.
  4. Select Save.

tags-aws

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

View service metrics

Once you add the service to monitoring, you can view the service metrics in your Dynatrace environment either on your dashboard page or on the custom device overview page.

Import preset dashboards

Dynatrace provides preset AWS dashboards that you can import from GitHub to your environment's Dashboards page.
Note: To save a preset dashboard locally, create a new JSON file on your local machine and copy-paste the content of the JSON file from GitHub into the new file.
Once you save a preset dashboard locally, there are two ways to import it.

swf

Available metrics

Name Description Unit Statistics Dimensions Recommended
ActivityTaskScheduleToCloseTime The time interval, in milliseconds, between the time when the activity was scheduled and when it closed Milliseconds Multi Domain, ActivityTypeName, ActivityTypeVersion ✔️
ActivityTaskScheduleToStartTime The time interval, in milliseconds, between the time when the activity task was scheduled and when it started Milliseconds Multi Domain, ActivityTypeName, ActivityTypeVersion ✔️
ActivityTaskStartToCloseTime The time interval, in milliseconds, between the time when the activity task started and when it closed Milliseconds Multi Domain, ActivityTypeName, ActivityTypeVersion ✔️
ActivityTasksCanceled The count of activity tasks that were canceled Count Sum Domain, ActivityTypeName, ActivityTypeVersion
ActivityTasksCompleted The count of activity tasks that completed Count Sum Domain, ActivityTypeName, ActivityTypeVersion
ActivityTasksFailed The count of activity tasks that failed Count Sum Domain, ActivityTypeName, ActivityTypeVersion
ConsumedCapacity The count of requests per second Count Sum Region, APIName
ConsumedCapacity Count Sum Region, DecisionName ✔️
DecisionTaskScheduleToStartTime The time interval, in milliseconds, between the time that the decision task was scheduled and when it was picked up by a worker and started Milliseconds Multi Domain, WorkflowTypeName, WorkflowTypeVersion ✔️
DecisionTaskStartToCloseTime The time interval, in milliseconds, between the time that the decision task was started and when it closed Milliseconds Multi Domain, WorkflowTypeName, WorkflowTypeVersion ✔️
DecisionTasksCompleted The count of decision tasks that have been completed Count Sum Domain, WorkflowTypeName, WorkflowTypeVersion
PendingTasks The count of pending tasks in a one minute interval for a specific task list Count Sum Domain
ProvisionedBucketSize The count of available requests per second Count Minimum Region, APIName
ProvisionedBucketSize Count Minimum Region, DecisionName
ProvisionedRefillRate The count of requests per second that are allowed into the bucket Count Minimum Region, APIName
ProvisionedRefillRate Count Minimum Region, DecisionName
ScheduledActivityTasksTimedOutOnClose The count of activity tasks that were scheduled but timed out on close Count Sum Domain, ActivityTypeName, ActivityTypeVersion
ScheduledActivityTasksTimedOutOnStart The count of activity tasks that were scheduled but timed out on start Count Sum Domain, ActivityTypeName, ActivityTypeVersion
StartedActivityTasksTimedOutOnClose The count of activity tasks that were started but timed out on close Count Sum Domain, ActivityTypeName, ActivityTypeVersion
StartedActivityTasksTimedOutOnHeartbeat The count of activity tasks that were started but timed out due to a heartbeat timeout Count Sum Domain, ActivityTypeName, ActivityTypeVersion
StartedDecisionTasksTimedOutOnClose The count of decision tasks that started but timed out on closing Count Sum Domain, WorkflowTypeName, WorkflowTypeVersion
ThrottledEvents The count of requests that have been throttled Count Sum Region, APIName
ThrottledEvents Count Sum Region, DecisionName ✔️
WorkflowStartToCloseTime The time, in milliseconds, between the time the workflow started and when it closed Milliseconds Multi Domain, WorkflowTypeName, WorkflowTypeVersion ✔️
WorkflowsCanceled The count of workflows that were canceled Count Sum Domain, WorkflowTypeName, WorkflowTypeVersion ✔️
WorkflowsCompleted The count of workflows that completed Count Sum Domain, WorkflowTypeName, WorkflowTypeVersion ✔️
WorkflowsContinuedAsNew The count of workflows that continued as new Count Sum Domain, WorkflowTypeName, WorkflowTypeVersion ✔️
WorkflowsFailed The count of workflows that failed Count Sum Domain, WorkflowTypeName, WorkflowTypeVersion ✔️
WorkflowsTerminated The count of workflows that were terminated Count Sum Domain, WorkflowTypeName, WorkflowTypeVersion ✔️
WorkflowsTimedOut The count of workflows that timed out, for any reason Count Sum Domain, WorkflowTypeName, WorkflowTypeVersion ✔️