Page MenuHomePhabricator

[blob][backup] Remove blob_hash from log span
ClosedPublic

Authored by bartek on Jan 25 2023, 2:38 AM.
Tags
None
Referenced Files
F3350114: D6388.id21302.diff
Fri, Nov 22, 8:49 PM
F3349118: D6388.diff
Fri, Nov 22, 5:15 PM
Unknown Object (File)
Sun, Nov 10, 2:00 PM
Unknown Object (File)
Fri, Nov 8, 5:02 AM
Unknown Object (File)
Fri, Nov 8, 4:52 AM
Unknown Object (File)
Thu, Nov 7, 5:38 PM
Unknown Object (File)
Oct 2 2024, 6:44 PM
Unknown Object (File)
Sep 27 2024, 9:09 AM
Subscribers

Details

Summary

When testing D6387, I was overwhelmed by log span metadata fields. The blob hash is very long and takes too much space when displayed with every tracing log message.
I replaced it to be displayed only once when received.

Test Plan

Both services start and display logs correctly

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

bartek held this revision as a draft.
bartek published this revision for review.Jan 25 2023, 2:49 AM
services/backup/src/service/handlers/create_backup.rs
106

I think hash is a part of sensitive data that should not be logged in any case, but I'm not sure what the decision was made to debug this service. If this is for the local debug only, maybe we should remove this logging.

Blob hash is probably fine to log, since it's not tied to a specific user

This revision is now accepted and ready to land.Jan 26 2023, 7:52 AM