AWS X-Ray

• Introduction
• Configuration
  • Format
  • Example
• End to end example
  • Running OpenCensus Service
  • Running Application Code
• Results
  • All traces
  • Single trace
  • Trace detail
  • Service Map
• References

Introduction

The OpenCensus Service allows one to export traces to AWS X-Ray

Configuration

In the Service’s YAML configuration file, under section “exporters” and sub-section “aws-xray” configure fields:

Format

exporters:
  aws-xray:
    default_service_name: "<an optional service name for unknown service names>"
    version: "<the version of the AWS X-Ray service to use>"
    buffer_size: <the number of spans that should be batched>

Example

exporters:
  aws-xray:
    default_service_name: "opencensus"
    version: "latest"
    buffer_size: 200

End to end example

In this end-to-end example, we’ll have OpenCensus Service running and a couple of Go applications that use the Go ocagent-exporter to send over traces to OpenCensus Service and then to AWS X-Ray.

Running OpenCensus Service

Here, the OpenCensus Service will run with AWS-XRay as the only trace exporter, but receive traffic from ocagent-exporter-using applications.

On starting the OpenCensus Service with the configuration below:

exporters:
  aws-xray:
    default_service_name: "opencensus"
    version: "latest"
    buffer_size: 200

On running the OpenCensus Service:

{"level":"info","ts":1550290707.0522702,"caller":"config/config.go:428","msg":"Trace Exporter enabled","exporter":"aws-xray"}

Running Application Code

And then running the ocagent-go-exporter main.go application

$ GO111MODULE=on go run example/main.go
#0: LineLength: 559By
#1: LineLength: 199By
#2: LineLength: 218By
#3: LineLength: 898By
#4: LineLength: 795By
Latency: 359.066ms
#0: LineLength: 292By
#1: LineLength: 339By
Latency: 669.318ms
#0: LineLength: 412By
Latency: 86.700ms

Results

On navigating to the AWS X-Ray at https://console.aws.amazon.com/xray/home

All traces

Single trace

Trace detail

Service map

References