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

[Wf-Diagnostics] use current clustername for emission of usage logs #6678

Merged
merged 2 commits into from
Feb 19, 2025

Conversation

sankari165
Copy link
Member

What changed?
current clustername used in data for emission of usage logs

Why?
to provide insights into where diagnostics is used

How did you test it?

Potential risks

Release notes

Documentation Changes

Copy link
Contributor

@3vilhamster 3vilhamster left a comment

Choose a reason for hiding this comment

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

Ok. I guess it was missed before. Do you mind adding a test to make sure that nothing else is missing?

@sankari165 sankari165 merged commit 0383b18 into cadence-workflow:master Feb 19, 2025
22 checks passed
@sankari165
Copy link
Member Author

saw the comment slightly late but it is hard to add a test since the data sent to emission of usage logs includes the time taken for the child wf execution and felt like too much info for unit tests

@sankari165 sankari165 deleted the CDNC-12428 branch February 19, 2025 11:51
Assem-Uber pushed a commit that referenced this pull request Feb 20, 2025
…6678)

* [Wf-Diagnostics] use current clustername for emission of usage logs

* Update module.go
Assem-Uber pushed a commit that referenced this pull request Feb 20, 2025
…6678)

* [Wf-Diagnostics] use current clustername for emission of usage logs

* Update module.go
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