Skip to content
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

Don't capture queue time for websocket requests #494

Merged
merged 3 commits into from
Mar 27, 2024

Conversation

jrothrock
Copy link
Contributor

With the use of libraries such as Stimulus Reflex, which under the hood utilize Turbo Streams, we can run into issues where the queue times that we report are very inaccurate.

They appear to have the same queue time header/timestamp as when the connection was first created, and is not changed for subsequent data sent over the websocket. This leads to an ever growing queue time as long as the connection isn't terminated.

@jrothrock jrothrock merged commit cdaa532 into master Mar 27, 2024
76 checks passed
@jrothrock jrothrock deleted the dont-capture-queue-time-for-websocket-requests branch March 27, 2024 22:53
@Zajn
Copy link

Zajn commented Apr 1, 2024

Hey y'all, thanks for fixing and merging this ❤️ Our scout graphs look so much better now.

Any chance there will be a minor version bump soon to the gem that includes this?

@jrothrock
Copy link
Contributor Author

Hey @Zajn, sorry for the delay on this. We just released 5.3.8 with this change

@Zajn
Copy link

Zajn commented Apr 3, 2024

@jrothrock No worries, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants