AWS X-ray

This page describes StackState version 4.1.

The StackState 4.1 version range is End of Life (EOL) and no longer supported. We encourage customers still running the 4.1 version range to upgrade to a more recent release.

Go to the documentation for the latest StackState release.


AWS X-Ray is a service that collects data about requests that your application serves, and provides tools you can use to view, filter, and gain insights into that data to identify issues, and opportunities for optimization.

AWS services provide integration with AWS X-Ray by adding a tracing header to requests, running the X-Ray daemon, or making sampling decisions, and uploading trace data to X-Ray. The X-Ray SDKs include plugins for additional integration with AWS services.


The StackState AWS X-Ray integration provides the following functionality:

  • Enriches AWS components with X-Ray trace service data.

  • Allows mapping the relations between X-Ray services, and ultimately AWS resources.

  • Provides performance metrics on relations between X-Ray services, as well as local anomaly detection on all performance metrics.


To get X-Ray traces you need to attach policy AWSXrayFullAccess to the AWS service roles in the IAM console. For more information about setting up X-Ray, check the AWS X-Ray Developer guide.


The AWS X-Ray check is included in the Agent V2 StackPack. You also need to install the AWS StackPack to see rest of you AWS topology and metrics.


  1. Edit the Agent integration configuration file /etc/stackstate-agent/conf.d/aws.d/conf.yaml to start collecting your Tomcat metrics and logs. See the sample aws.d/conf.yaml.example for all available configuration options.

     # Section used for global AWS check config
         # optional
         # cache_file: '/opt/stackstate-agent/tmp'
       # mandatory AWS credentials and config
       - aws_access_key_id: 'abc'
         aws_secret_access_key: 'cde'
         role_arn: 'arn:aws:iam::0123456789:role/RoleName'
         region: 'ijk'
         # optional
         # min_collection_interval: 60
  2. Restart the StackState Agent(s) to publish the configuration changes.

Need help? Please contact StackState support.

Last updated