Keep the goal narrow
Share one task-specific artifact: Preserve stack traces, timestamps, and long diagnostic lines.
A log pastebin for stack traces and diagnostics
A diagnostic paste should capture the smallest useful time window around a failure. The goal is to preserve evidence - Timestamps, error types, correlation, and stack structure - While removing credentials and personal data.
Share logs at a glance
Use these three checks before you turn share logs into a link for another person.
Start with the least exposure
Recommended first step: Choose plain text or the closest log syntax
Remove risky details
Before upload: Review the share logs checklist below to replace live values while preserving the context a recipient needs.
Share logs tip: How to share error logs safely adds this format-specific context: Select the causal window and redact diagnostic data systematically.
Share logs workflows
A well-scoped share logs artifact preserves the task-specific context below and can expire when that task ends.
Support tickets
Include the complete error and a short lead-up window; give recurring hosts and users consistent redaction labels so relationships remain visible.
Build failures
Keep the failing command, toolchain version, first causal error, and nearby output instead of uploading an entire repetitive build log.
Incident handoffs
Use the paste as a temporary conversation artifact while the approved logging and incident platforms remain the system of record.
Recommended paste settings
- 1Choose plain text or the closest log syntax
- 2Keep the paste unlisted
- 3Expire it after the support window
- 4Preserve original timestamps and line breaks
What not to include
Search for authorization headers, cookies, tokens, connection strings, email addresses, customer identifiers, internal hostnames, and signed URLs before uploading.
For share logs, a made-up but representative example is safer than a production export. Expiration can end future access to the source link, but it cannot recall a recipient’s copy.
Compare privacy controls →Use encryption when share logs must not be readable in storage
For a private share logs artifact, encrypted mode applies AES-GCM in the browser before upload. Its key stays after # in the share URL and outside the normal server request.
Understand client-side encryption →BEFORE UPLOADReadable content
→AES-GCM
IN STORAGEEncrypted bytes
Share logs questions
Practical answers about the access, retention, and context choices for share logs.
How much of a log should I share?+
Include enough events before and after the failure to establish cause, but remove unrelated hours of repetitive output.
Does secret scanning make a log safe?+
No. Pattern detection can miss contextual data and unknown credential formats, so a human redaction pass is still required.