We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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?
to your account
I believe we're unable to track time-in-queue for apps that directly receive traffic from AWS ALBs as these requests lack a supported x-request-start-like header.
However, it looks like we can parse this information from the X-Amzn-Trace-Id header.
67891234 is the epoch time, in seconds.
Our parsing logic would need to be updated as this is a significantly different format.
The text was updated successfully, but these errors were encountered:
Actually would this even be useful? Time since epoch in seconds isn't high-resolution enough.
Sorry, something went wrong.
You are right, it doesn't seem to be very precise, is that actually the state of it today?
Seems like a request for X-Request-Start has been hanging out for nine years: https://forums.aws.amazon.com/message.jspa?messageID=396283
We're running behind AWS ALBs and anything would help us.
The only thing I've seen work is for you to run your own reverse proxy on each individual instance. e.g nginx, passenger standalone, apache, etc.
Measuring in seconds is too granular and it doesn't look like AWS will be adding ms any time soon. Closing
No branches or pull requests