-
Notifications
You must be signed in to change notification settings - Fork 57
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
clean up post-Hijack code #530
Comments
jmhodges
added a commit
that referenced
this issue
Jul 9, 2023
Now that we don't rely on hijack, we can use the statWriter to write our metrics. This probably would be better a deeper integration of our tracing work, but this at least makes the metrics consistent. Updates #530
jmhodges
added a commit
that referenced
this issue
Jul 9, 2023
Now that we don't rely on hijack, we can use the statWriter to write our metrics. This probably would be better a deeper integration of our tracing work, but this at least makes the metrics consistent. Updates #530
jmhodges
added a commit
that referenced
this issue
Jul 9, 2023
Now that we don't rely on Hijack, we can use the statWriter to write our metrics. This probably would be better a deeper integration of our tracing work, but this at least makes the metrics consistent. Updates #530
jmhodges
added a commit
that referenced
this issue
Jul 9, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should rename hijackHandle and fix up the logging in it to include the new name. Or refactor the JSON API and HTML handlers to not use a central func anymore since the new code needs much less handholding
The text was updated successfully, but these errors were encountered: