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 metrics to monitor task validation. #5466

Merged
merged 3 commits into from
Dec 6, 2023

Conversation

agautam478
Copy link
Contributor

What changed?

  • Introduced the metric monitoring to the taskvalidator service.
  • We are counting the number of workflows that enter the service for validation. This will give us a perspective of how many workflows are suspected to be corrupted when going through it's respective processing.
  • Currently we are only monitoring the workflows from history update where the maximum attempts exceeded to update history.
  • The plan is to roll it out for other task processing flows as well.

Why?
Made these changes to get a sense of how many workflows are assumed to be corrupted.

How did you test it?
tested locally.
Wrote a unit test.

Potential risks
NA

Release notes
NA

Documentation Changes
NA

Copy link
Member

@ketsiambaku ketsiambaku left a comment

Choose a reason for hiding this comment

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

LGTM

tag.WorkflowRunID(runID),
tag.WorkflowDomainID(domainID))
// Emit the number of workflows that have come in for the validation.
w.metricsClient.Scope(metrics.TaskValidatorScope).IncCounter(metrics.ValidatedWorkflowCount)
Copy link
Member

Choose a reason for hiding this comment

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

which tags will this metric have? can you share example from local run?

@agautam478 agautam478 merged commit 186d253 into cadence-workflow:master Dec 6, 2023
16 checks passed
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.

3 participants