serverless-plugin-tracing
serverless-plugin-tracing copied to clipboard
Enables AWS X-Ray tracing for Serverless
I suspect this happens because of the new schema validation rules put in place in serverless 2.x. Can we just move `provider.tracing` to `custom.tracing` in the `serverless.yml`?
Seems like in the latest Serverless version(3.19.0), yaml-schema changed for tracing directive (tracing to Tracing ). it is a warning. "DID NOT IMPACT" tracing config ` Incorrect type. Expected "Aws.Tracing".yaml-schema:...
Looks like as per the documentation [here](https://www.serverless.com/framework/docs/providers/aws/guide/plugins/#extending-validation-schema) that plugins can define properties in the `custom:` but not the `provider:` section of `serverless.yml`. Moreover plugin properties cannot be in the top...
In release v1.40 the Serverless Framework included support for lambda X-Ray tracing (https://serverless.com/blog/framework-release-v140/) and subsequently in v1.41 also incorporated API Gateway tracing support (https://serverless.com/blog/framework-release-v141/). Do these SLS releases supersede this...
Hi! Could we configure x-ray groups and annotations using this plugin or any other serverless tool? If no, it will be great feature.
AWS supports X-Ray for API Gateways: https://aws.amazon.com/de/blogs/aws/apigateway-xray/ It would be great to configure the stage property via this serverless plugin. I could not find any hints if cloudformation supports it...
This is just a question. Thanks a lot
Good Day. I just noticed that installing `npm install --save-dev serverless-plugin-tracing` is not enough to use this plugin. I have struggled for serveral days to find the way how to...
Is there a simple way to get the Trace ID from one function and then pass it to a lambda.invoke() to call a second function, to tie chaining lambdas together?
Error: ``` { "errorMessage": "Missing AWS Lambda trace data for X-Ray. Expected _X_AMZN_TRACE_ID to be set.", "errorType": "Error" } ``` Invoked by running: `sls invoke local -f activateTrigger --path trigger.json`...