-
Notifications
You must be signed in to change notification settings - Fork 248
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
Telemetry fixes #2857
Telemetry fixes #2857
Conversation
Signed-off-by: Caleb Schoepp <[email protected]>
This is relied on by other parts of spin-telemetry Signed-off-by: Caleb Schoepp <[email protected]>
Signed-off-by: Caleb Schoepp <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like an improvement. As for your questions:
- re: DB addresses - this seems like a smart idea to remove
- key-value: I think we definitely want to remove values - I can see the argument both for keeping and removing keys. Perhaps we keep them for now, and see what people think over time?
We could perhaps drop it by default but allow opting-in by level, e.g. #[instrument(..., fields(key = Empty))]
...
// I believe this would allow e.g. RUST_LOG=spin_factor_key_value=debug
if tracing::enabled!(Level::DEBUG) {
span.record("key", key);
} |
Ready for another round of review. I think that we should just keep keys for now and we can handle feedback in the future. I feel that it is a reasonable requirement that PII should be kept out of keys. |
I tried this and it didn't work. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I still have questions, but nothing that should block if you feel this is ready to merge.
7652220
to
c4aeff8
Compare
Ready for one more review and then for someone to merge it if they think it's good to go. |
@calebschoepp looks like the failure in CI is legit:
|
Signed-off-by: Caleb Schoepp <[email protected]>
c4aeff8
to
7ee2579
Compare
Fixed |
Summary
Questions
Fixe #2816