Skip to content

Latest commit

 

History

History
 
 

jaeger-go

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
vendor
vendor
 
 
Gopkg.lock
Gopkg.lock
 
 
Gopkg.toml
Gopkg.toml
 
 
README.md
README.md
 
 
main.go
main.go
 
 

README.md

OpenTracing and Jaeger in AWS Lambda Go 1.x Runtime

This is an example of a simple, traced Lambda function using the Jaeger Go tracer with SignalFx. See main.go for the example code.

Building and Creating a Deployment Package

A Go deployment package for AWS Lambda is a .zip file consisting of your built project's executable. To build this application and create the deployable archive follow these instructions from the root tracing-examples directory:

$ pwd  # Confirm this is <your_local_path/tracing-examples>
$ mkdir -p $GOPATH/src/github.com/signalfx
$ ln -s $(pwd) $GOPATH/src/github.com/signalfx/tracing-examples
$ cd $GOPATH/src/github.com/signalfx/tracing-examples/aws-lambda/jaeger-go
$ GOOS=linux go build .  # GOOS=linux is needed for the Lambda runtime environment
$ zip my_traced_golang_lambda.zip ./jaeger-go

The resulting my_traced_golang_lambda.zip can be uploaded to S3 or in your browser via the AWS Console during function creation. Register your handler as jaeger-go and don't forget to set the SIGNALFX_INGEST_URL environment variable to point to your Gateway. You should be able test the application with the following test event:

{
  "queryStringParameters": {
    "choice": "00"
  }
}

The execution result should succeed with a response similar to:

{
  "statusCode": 404,
  "body": "{\"TraceId\":\"2296bd21606fc2e4\",\"Result\":\"You Lost! The ball landed on 35.\",\"Choice\":\"00\"}"
}

Resources