Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.logbrew.co/llms.txt

Use this file to discover all available pages before exploring further.

When you run into an error that needs a second pair of eyes, LogBrew gives you three ways to get the details out quickly. You can copy a formatted plain-text version to your clipboard, send it through any iOS app via the Share Sheet, or create a shareable web link you can drop into a Linear issue, a Slack thread, or a support ticket. All three options are available from the Share button on any event detail screen.

​
Three ways to share

Copy to clipboard

Copies the error title, message, and full stack trace as plain text. Paste it anywhere: your terminal, a note, a chat message.

iOS Share Sheet

Opens the native iOS share sheet so you can send the error to Slack, iMessage, Mail, Notes, or any app installed on your device.

Shareable link

Creates a web URL that shows the event details. No login required to view. Choose an expiry of 24 hours, 7 days, or 30 days.
1

Open the event detail screen

Tap any event in your feed to open it.
2

Tap Share

Tap the Share button in the event detail toolbar.
3

Tap Create Link

In the share options sheet, tap Create Link.
4

Choose an expiry

Select how long the link should stay active: 24 hours, 7 days, or 30 days.
5

Copy or send the link

The generated URL is copied to your clipboard automatically. You can also pass it directly to the iOS Share Sheet from the same screen.
The shareable page includes the event title, severity level, full stack trace, and event metadata (environment, OS version, app version, and any other fields captured at ingestion time). The page is read-only and does not require the recipient to create a LogBrew account.
The link is accessible to anyone who has the URL for the duration you set. Treat it like any other link to sensitive error data. Do not post it in public channels if your stack traces contain private information.
When the expiry time passes, the link shows a “This link has expired” message. The underlying event data is not deleted. You can create a new link from the same event at any time.
When you create a bug ticket in Linear for an error you spotted in LogBrew, paste the shareable link into the issue description. Your teammate can see the full stack trace without needing a LogBrew account or access to your Sentry organization.
Drop the link into the relevant Slack channel. Anyone in the channel can open it and read the error context directly, keeping the conversation focused.
If a customer reports a specific error and you have the event in LogBrew, share the link with a support engineer so they can understand the full context without needing provider access.