Closed slaskawi closed 3 years ago
Not familiar with the code base but the metic examples look good to me.
@maleck13 @pb82 I changed the algorithm to scrape the last two matched URIs. From my testing it looks good but I also added an "emergency turn off button".
@slaskawi thanks, i'll take another look
@pb82 @maleck13 Can I can to review and merge this one? Once it's in, Peter, could I ask you for a release?
:eyes:
@pb82 @maleck13 @abstractj Last chance to get this merged and onboarded into the production. After Wednesday, I'd say it's too late.
Motivation
https://issues.redhat.com/browse/MGDSTRM-1664
In order to support better observability, all the performance metrics need to support resources. This way, we know exactly which endpoints are fine and which cause some problems.
What
This Pull Request introduces a new "resource" field into the latency metrics. Here's an example:
Why
This feature is require for better understanding the performance problems.
How
An additional "resource" field is added to the metrics.
Verification Steps
$KC/standalone/deployments
Checklist:
Progress