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

Add a 'save failed by service' metric, as currently a counter is only… #1064

Merged
merged 2 commits into from
Sep 18, 2018

Conversation

objectiser
Copy link
Contributor

… used to keep track of successful span saves

Signed-off-by: Gary Brown [email protected]

Which problem is this PR solving?

Currently a counter is only available to record successfully saved spans. An error is reported if the write fails, but no counter is provided.

Short description of the changes

Add a counter to record the number of span write failures.

@objectiser
Copy link
Contributor Author

"save-failed-by-svc" is just a placeholder - happy to change to a better name.

BatchSize: hostMetrics.Gauge("batch-size", nil),
QueueLength: hostMetrics.Gauge("queue-length", nil),
ErrorBusy: hostMetrics.Counter("error.busy", nil),
SavedBySvc: newMetricsBySvc(serviceMetrics, "saved-by-svc"),
Copy link
Contributor

Choose a reason for hiding this comment

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

I'd prefer if we used tags instead: metric name = saved-by-svc, tag = success|fail

Copy link
Contributor

Choose a reason for hiding this comment

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

although, technically it'll be a breaking change but we've gone ahead with metric changes without considering it a breaking change

Copy link
Contributor Author

Choose a reason for hiding this comment

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

If we want to take this approach, then there are some other places that should be changed also - e.g. jaeger_find_traces_errLatency_count and jaeger_find_traces_okLatency_count. But I agree it would be better to have it as a tag on the metric.

… used to keep track of successful span saves

Signed-off-by: Gary Brown <[email protected]>
@black-adder black-adder merged commit 5f1318b into jaegertracing:master Sep 18, 2018
@ghost ghost removed the review label Sep 18, 2018
@objectiser objectiser deleted the writefailed branch October 4, 2018 10:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants