-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doesn't work with Vapor? #52
Comments
@msnegurski Were you able to figure this out? |
@emaadali unfortunately not, basically gave up on this idea I made some custom trace id generation and got it working somewhat, however that means traces from Laravel will not be linked to traces automatically generated by Lambda (from screenshot) |
Yes, it supports vapor out of the box. You have to configure the submitter in config/xray.php to:
|
Anyone made it work? Or is this dead. I can only see lambda invocations and http response codes but nothing else is being logged even though I followed the doc for vapor. |
Hey, curious if anyone encountered this issue. It just straight up doesn't work with Vapor. From doing some digging issue seems to be that HTTP_X_AMZN_TRACE_ID and LAMBDA_INVOCATION_CONTEXT variable are not present in either $_SERVER or $_ENV.
The text was updated successfully, but these errors were encountered: