Send application, server, and browser logs as formatted text links with searchable preview instead of broken chat pastes.
Recommended setup
- Name the file clearly before upload.
- Preview the share page before sending it externally.
- Add a password when the file contains customer, account, contract, or operational data.
- Choose an expiry window that matches the real review period.
- Use copy-all handoff text when the recipient needs link, password, and expiry details together.
Capture the useful time window
Logs should show the failure window rather than every event the system has ever produced. Keep the timezone, service name, deployment version, request or trace identifier, and surrounding error lines. Pair the link with a short ticket note that states what was expected, what happened instead, and the exact reproduction time.
Redact before you share
Application logs commonly contain bearer tokens, cookies, email addresses, internal hostnames, customer identifiers, and request payloads. Remove or mask those values before uploading. Password protection is an access control, not permission to distribute credentials or personal data that should never leave the originating system.
Preserve an investigation boundary
Set the expiry to cover the active investigation and create a new share for a later incident or a new capture. This makes the evidence easier to compare and prevents a forgotten diagnostic export from remaining accessible after the issue is closed.
Preserve the signal around the error
Capture enough context to explain the failure: timezone, service and environment, deployed version, request or trace identifier, the action being attempted, and several lines before and after the error. A single error line is often not actionable. Conversely, an unbounded production log makes the important event hard to find and increases the risk of exposing data that does not belong in the ticket.
Redact before uploading
Search for bearer tokens, cookies, authorization headers, email addresses, phone numbers, customer IDs, internal hostnames, and request bodies. Replace values with stable placeholders when a relationship must remain visible, such as user_123 or [redacted-token]. Do not rely on a password to justify sharing live credentials. Rotate an accidentally exposed secret through the owning system, then share a clean capture for debugging.
Make investigation data disposable
Use a title that identifies the incident and capture window, such as checkout-api-error-2026-09-22-utc.log. Pair the link with the expected and actual behavior. Once the incident is resolved, expire the share under the team's retention rules. A later recurrence should receive a new capture so investigators do not confuse separate failures or depend on an old environment state.