-
Notifications
You must be signed in to change notification settings - Fork 2
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
feature: move to telemetry events to report stats #24
Conversation
b269213
to
83cbf4b
Compare
README.md
Outdated
|
||
- `[krc_pb_client, request, stop]` emitted at the end of a request to riak | ||
- Measurement: `#{duration => integer(), monotonic_time => integer()}` | ||
- Metadata: `#{request => map(), response => ok | error, error => term()}` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doesn't this one always include bucket as well? It looks like it reading the metadata
helper in the code below.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does, it's inside the request
map.
To extend on this a little bit, having the whole spec in there would make it a bit hard to read. The idea was to just have a high level idea of what's in the event
Description
At the moment, the library uses
stdlib2
to report metrics which doesn't work as the system moved toprometheus
.In this PR, the metrics are replaced with
telemetry
events that allow the main application to decide what to do with them: create metrics or logs.