Skip to content

cvm_tracing: Allow untagged tracing statements by default (#1402) #1406

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

Merged

Conversation

smalis-msft
Copy link
Contributor

After long discussions we have decided to flip the default of our tracing filter, and to allow untagged tracing statements by default. We believe that the risks and costs of being unable to debug incidents in production are too high, and that we can manually scrub our tracing statements to ensure that no sensitive information is leaked.

Cherry-pick of #1402.

Part of #852.

…1402)

After long discussions we have decided to flip the default of our
tracing filter, and to allow untagged tracing statements by default. We
believe that the risks and costs of being unable to debug incidents in
production are too high, and that we can manually scrub our tracing
statements to ensure that no sensitive information is leaked.

Part of microsoft#852.
@smalis-msft smalis-msft requested a review from a team as a code owner May 23, 2025 17:25
@github-actions github-actions bot added Guide release_2505 Targets the release/2505 branch. labels May 23, 2025
@smalis-msft smalis-msft enabled auto-merge (squash) May 23, 2025 17:25
@smalis-msft smalis-msft merged commit e1be258 into microsoft:release/2505 May 28, 2025
24 checks passed
@smalis-msft smalis-msft deleted the cvm-tracing-backport branch May 28, 2025 21:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Guide release_2505 Targets the release/2505 branch.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants