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.

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

Fix remote write metrics #300

Merged

Conversation

squat
Copy link
Contributor

@squat squat commented Jan 22, 2020

Today, we only track the number of errors encountered when forwarding requests from the v1 upload endpoint to thanos. We don't track the total amount of requests made from the v1 upload endpoint handler. We also don't track any requests made when forwarding requests from the v2 endpoint to thanos.

This PR adds these metrics to give us better visibility during another incident.

cc @metalmatze @brancz @bwplotka @kakkoyun

Previously, only failed requests were tracked; this makes it difficult
to know how many requests were actually attempted.

Signed-off-by: Lucas Servén Marín <lserven@gmail.com>
This commit adds a new metric to track the number of remote write
requests made when handling the v2 endpoint. It also disambiguates the
metric name for forwarded v1 requests.

Signed-off-by: Lucas Servén Marín <lserven@gmail.com>
@openshift-ci-robot openshift-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jan 22, 2020
Help: "Total amount of samples successfully forwarded",
})
forwardErrors = prometheus.NewCounter(prometheus.CounterOpts{
Name: "telemeter_forward_request_errors_total",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we have alerts for these metrics? If so we should probably change these as well?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll investigate. In any case, there are no other references to those metrics in this repo, so we'lll need to make adjustments in either obs/cfg or the deployment repos

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ack, confirmed we don't have any alerts or recording rules referencing these metrics today. eventually we'll want to add some alerts based on the error rates tho

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ack

@brancz
Copy link
Contributor

brancz commented Jan 22, 2020

/retest

3 similar comments
@brancz
Copy link
Contributor

brancz commented Jan 22, 2020

/retest

@squat
Copy link
Contributor Author

squat commented Jan 22, 2020

/retest

@squat
Copy link
Contributor Author

squat commented Jan 23, 2020

/retest

@metalmatze
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 23, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: metalmatze, squat

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-robot openshift-merge-robot merged commit 71e6c60 into openshift:master Jan 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants