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 Nexus failure_reason metric tag #1671

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

bergundy
Copy link
Member

A follow up for #1664 where we decided to add more information on Nexus task failures.

@bergundy bergundy requested a review from a team as a code owner October 14, 2024 18:38
// NexusTaskFailureTags returns a set of tags for Nexus Operation failures.
func NexusTaskFailureTags(reason string) map[string]string {
return map[string]string{
FailureReasonTagName: reason,
Copy link
Member

Choose a reason for hiding this comment

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

Is it possible to, somewhere, clarify all possible enumerate values here? Some spec or something for SDKs to follow. I want to make sure it's a fixed enumerate, that all SDKs share them, and we are ok with the casing of the values.

Copy link
Member Author

Choose a reason for hiding this comment

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

My plan was to put this in our docs in /sdk-metrics. Does that work for you?

Copy link
Member

Choose a reason for hiding this comment

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

Sure! I would like to confirm the values before merging this (can add them in here if easiest).

Copy link
Member Author

Choose a reason for hiding this comment

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

Copy link
Member

Choose a reason for hiding this comment

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

So to confirm, it's handler_error_NOT_IMPLEMENTED not all consistent cased, correct? I don't mind, just checking.

@Quinn-With-Two-Ns
Copy link
Contributor

On the test failure TestNonDeterminismFailureCauseReplay is flaky , @yuandrew is looking into it

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