Module report 

Bug reports with the client’s own logs attached - CLOUDPUB-577.

Support used to open every ticket by asking the user for their logs. The client already keeps a rolling log set next to its cache, so clo report packs that set together with its own metadata and a redacted copy of the config, and uploads the archive to /api/contact/report/.

The redaction is the part that matters: the config carries the account token and may carry a PKCS#12 password, and a bug report is read by a human and kept in our media store. Nothing secret may leave the machine.

Structs

ReportMeta

Client-side facts support needs to make sense of the logs.

Constants

REDACTED

What a redacted value is replaced with.

Functions

log_dir

The rolling log set lives here; init in base.rs writes into the same dir.

log_files

The rolling log set: client.log plus whatever the appender rotated out of it. Sorted so the archive is reproducible.

pack_report

Pack a report archive and answer its size in bytes.

redact_config

Strip every secret out of a client config before it is packed.

report_url

Where the report is POSTed for a given server URL.

send_report

Pack the rolling logs plus a redacted config and upload them.

upload_report

Upload a packed archive. The caller supplies the HTTP client so the report travels over the same TLS setup (custom roots included) as everything else.