feat: Enable emittance of response time metrics (achieving parity with Kratos) #2323
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Currently, Kratos emits response time metrics that can be used to monitor latency as well as Requests Per Second. Kratos's metrics middleware looks like:
Currently, the equivalent in Hydra omits the first and last lines:
Consequently, Hydra doesn't emit the response time metrics that would enable us to monitor latency/RPS.
In our case, being able to monitor these metrics is an absolute necessity, and generally, it would seem desirable to have parity between Hydra and Kratos in this regard.
This PR adds the missing lines to Hydra to enable emittance of these key metrics and achieve parity with Kratos.
Checklist
vulnerability. If this pull request addresses a security. vulnerability, I
confirm that I got green light (please contact
security@ory.sh) from the maintainers to push
the changes.
works.
Further comments