Florian Chazal
Florian Chazal
Thanks for reporting this. A fix is on his way !
removing the margin section should solve your issue
Thanks for this feedback and proposal, indeed we can do better here. We will look into it
Thanks a lot for those inputs ! We will look into it
Thx for your suggestion ! Interesting idea that can definitely help reducing logging cost while having a verbose output on error. we will look into it .
> Yeah, at this moment we don't support packaging assets out of the box. But you can try using a pre push hook - https://docs.amplify.aws/cli/project/command-hooks/ to package the Lambda assets,...
Current solution only support Code* (Pipeline/Build etc.) as source of metrics for the dashboard but for teams that use github actions as CI/CD solution nothing is pulled from the run...
Inspecting the raw trace, it is linked to the fact that root segment is not in it. So the issue is probably due to the fact that the root segment...
On my side the issue was the way I was setting my regex for `addXRayTraceIdHeader`. Not sure what was wrong with `new RegExp` constructor but going straight for a regex...
On my side, got it fixed by: 1. Reverted manually to old values in SSM (check your CustomCrossRegionExportWriter Lambda logs in cloudwatch to get the old and new value and...