resolved
Sentry
sentry.io/
landed in 38msBookSlash for Sentry · Engineering
b/errors.
b/performance. b/releases.
Sentry catches the bugs production sees first. The error queue, the performance dashboard, the release health view — each gets a flat name your engineering team types.
sentry
other shortcuts you might save
b/sentryb/errorsb/performanceb/releases
Suggested slug patterns
Steal these. They work for most teams.
Battle-tested shortcut conventions for Sentry, with notes on why each one survives the URL changes that break personal bookmarks.
- b/sentry
Sentry organisation home.
New engineers learn it day one; saves the workspace-switching tax.
https://{org}.sentry.io - b/errors
Open error queue / Issues view.
On-call reaches it dozens of times per shift.
https://{org}.sentry.io/issues - b/performance
Performance dashboard / Web Vitals.
Engineering leads track p95 latency; saving as a slug ends the navigation.
https://{org}.sentry.io/performance - b/releases
Release health tracking.
Pair with deploy slugs; engineers verify release health post-deploy.
https://{org}.sentry.io/releases - b/alerts
Active alert rules.
On-call reaches it during incident response; ops reaches it during alert tuning.
https://{org}.sentry.io/alerts/rules - b/sentry-replays
Session replays for error investigation.
Engineers reach it to understand the user session that triggered an error.
https://{org}.sentry.io/replays
Common workflows
Three patterns that pay back in week one.
01
On-call error triage
On-call engineers open b/errors at shift start. Pairs with b/sentry-replays for user-session context. The slug ends the recurring "where is the right Sentry view?" friction.
02
Post-deploy verification
After every release, engineers reach b/releases to confirm error rates haven’t regressed. The slug carries through every deploy cycle; the URL stays current as Sentry evolves the release UI.
03
Quarterly performance review
Engineering managers reach b/performance during quarterly reviews. The slug carries the team to the same view; the underlying dashboard evolves silently.
With and without
Same Sentry. Different team experience.
Without shortcuts
Each engineer has private Sentry bookmarks. On-call shifts include a 30-minute "here are the dashboards" walkthrough. Release verification involves five sidebar clicks.
With BookSlash
b/sentry, b/errors, b/performance, b/releases, b/alerts, b/sentry-replays. Six slugs cover Sentry for engineering and on-call together.
Frequently asked
BookSlash + Sentry
Most teams use both. Namespace cleanly: b/dash-{service} (Datadog) for system metrics, b/errors (Sentry) for application errors. The b/ pattern unifies both tools.
Yes — slugs are URL → URL. Self-hosted Sentry URLs work identically; just point the slug at your internal Sentry instance.
No — Sentry handles issue management. BookSlash gets engineers to the issue queue; the resolution still happens in Sentry.
Same pattern as Datadog: edit the escalation message template to include "Open b/errors" or a service-specific slug.
Start with one team. Roll out when it sticks.
Your stack. Your shortcuts.
One keystroke for everyone.
2,400+ teams reach every important destination in their stack with a single keystroke. Save the first slug in 30 seconds.
Free for personal use · No credit card · 14-day team trial