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.

Sign up for GitHub

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

Jump to bottom

Collect higher resolution of cht_feedback_total data #39

Open
jkuester opened this issue May 3, 2023 · 0 comments
Open

Collect higher resolution of cht_feedback_total data #39

jkuester opened this issue May 3, 2023 · 0 comments

Comments

@jkuester
Copy link
Collaborator

jkuester commented May 3, 2023

By itself, this metric is not super useful since you do not know the composition of what types of errors are being recorded.

When I think about client feedback/error rate what we really want to know about is new patterns of failures! That'd an awesome alert. These error rates need to change by quite a lot before it'd actually change how we respond.

We should also record additional meta-data about the errors either as labels on the cht_feedback_total metric or as separate metrics.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jkuester