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

Separate history/matching failure metrics from cadence failures #488

Merged
merged 1 commit into from
Jan 3, 2018

Conversation

madhuravi
Copy link
Contributor

Cadence Failures are used to determine availability and marking all errors as CadenceFailures were causing availability drops. Created new tags for history/matching that can be tracked independently.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.006%) to 66.801% when pulling 128ec19 on avail into 8a89e91 on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.03%) to 66.829% when pulling 128ec19 on avail into 8a89e91 on master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.2%) to 66.304% when pulling b1f6eac on avail into bb03ce5 on master.

@madhuravi madhuravi requested review from yiminc-zz and vancexu January 3, 2018 18:04
@madhuravi madhuravi merged commit 6ff9cbd into master Jan 3, 2018
@madhuravi madhuravi deleted the avail branch January 3, 2018 19:59
@@ -624,6 +626,7 @@ var MetricDefs = map[ServiceIdx]map[int]metricDefinition{
TaskRequests: {metricName: "task.requests", metricType: Counter},
TaskFailures: {metricName: "task.errors", metricType: Counter},
TaskLatency: {metricName: "task.latency", metricType: Counter},
HistoryFailures: {metricName: "history.errors", metricType: Counter},
Copy link
Contributor

Choose a reason for hiding this comment

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

Probably you want to have these defined under common as all services needs to emit these counters.
I would also suggest a "client" prefix for these client metric.

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.

4 participants