Share a log

What is Log Share?

The fastest way to hand someone a log without pasting hundreds of lines into chat. Paste output from kubectl logs, docker logs, journalctl, a CI job or an application stack trace, choose how long the link should live, and send it. The viewer adds line numbers, syntax highlighting, in-page search, word wrap and a download button.

Supported log types

The type is detected automatically as you paste and you can override it: JSON, YAML, Nginx, Apache, Docker, Kubernetes, shell sessions, Python and Java tracebacks, JavaScript, PostgreSQL, and a generic timestamped application log format. Plain text always works.

How to share a log file with a teammate or with support

1. Copy the relevant window: the last few hundred lines around the error, not the whole day. On a server, tail -n 300 app.log is usually enough.
2. Paste it above. The type is detected as you paste; correct it if the highlighting looks wrong.
3. Pick how long the link should live. Support tickets often want 7 days; a quick question needs 30 minutes.
4. Click Create Share Link, copy the link, and send it. The recipient needs no account and sees line numbers, colours and search.
5. Point at the exact line by clicking its number in the viewer: the copied link opens scrolled to it.

Share kubectl, docker and journalctl output

Pipe the command into your clipboard and paste, or redirect to a file and copy that. On macOS use pbcopy, on Linux xclip -selection clipboard or wl-copy, on Windows clip.

kubectl logs deploy/api -n prod --tail=300 --timestamps | pbcopy
docker logs web-1 --since 15m 2>&1 | xclip -selection clipboard
journalctl -u nginx --since "1 hour ago" --no-pager | clip
kubectl logs api-7d9f -n prod --previous > crash.log   # the container that just died

Include the timestamps flag where the tool offers one; the viewer highlights them and whoever reads the log will thank you.

Strip secrets before you share

Logs leak: bearer tokens in request dumps, database URLs with passwords, session cookies, customer emails. Search the paste for token, password, secret, Authorization and @ before you click create, and replace values with [redacted]. If the content is sensitive by nature, use a Private Room instead: it opens only with a PIN and expires within 24 hours.

What the viewer gives the reader

• Line numbers that double as permalinks, so "look at line 212" becomes a link.
• Syntax highlighting per log type, with ERROR, WARN and INFO levels coloured.
• In-page search with match counts (Ctrl+F is captured), word wrap and a full-screen mode.
• Copy all, copy the selection, or download the original as a file.
• A visible expiry countdown, so nobody bookmarks something that is about to vanish.

Privacy

Shares are stored on the server only until they expire, then permanently deleted. Links use random, non-sequential tokens, the pages are excluded from search engines, and content is never sent to a third party. Anyone with the link can view it, so strip credentials before sharing.

Frequently asked questions