Issues
- 5
- 1
- 1
Availability of link support in AWS SDK
#518 opened - 8
- 12
- 2
End of support for X-Ray SDK?
#515 opened - 4
- 2
False positive critical vulnerabilities reported when packaging aws-xray-sdk in a container
#507 opened - 2
Configure captureHttps behaviour
#506 opened - 2
- 3
- 2
xray daemon terminating on Elastic Beanstalk
#498 opened - 6
Traces from Lambda to StepFunction to Lambda
#497 opened - 2
`downstreamXRayEnabled` / `traced` property behavior doesn't seem to align with X-Ray documentation
#493 opened - 2
- 3
- 5
- 2
- 2
- 13
- 5
- 2
- 9
memory Leak Nodejs - Timedout requests
#483 opened - 4
- 5
- 1
captureAWS is not working
#479 opened - 1
- 6
Node version of aws-xray-sdk-node loses trace when asynchronously invoking another lambda function
#477 opened - 4
- 1
Segment exceptions are not assigned an ID
#473 opened - 1
- 5
- 0
- 5
- 4
- 1
Postgres: instrument making the connection
#463 opened - 2
grouping http requests
#461 opened - 11
xray whitelist for additional data capture does not work with AWS Javascript v3 SDK clients
#460 opened - 3
Bug in generation of the http.url
#455 opened - 1
- 3
- 6
- 3
Networking-level http instrumentation
#451 opened - 6
- 1
Cannot read property 'unshift' of undefined
#448 opened - 1
Cant capture v3 clients
#447 opened - 11
- 8
- 3
- 8