resolved
Datadog
datadoghq.com/dashboard/{dashboard-id}/{service}
landed in 38msBookSlash for Datadog · Engineering
Page received.
Dashboard in 40 ms.
On-call engineers do not have time to navigate Datadog’s sidebar at 3 a.m. With BookSlash, every dashboard, trace view, and SLO page has a name the on-call rotation memorises. PagerDuty alerts include the slug in the payload, so engineers go from page to dashboard in one keystroke.
dash-<service>
other shortcuts you might save
b/dash-<service>b/traceb/logsb/apm
Suggested slug patterns
Steal these. They work for most teams.
Battle-tested shortcut conventions for Datadog, with notes on why each one survives the URL changes that break personal bookmarks.
- b/dash-<service>
Per-service dashboard pattern (b/dash-checkout, b/dash-payments).
Pairs with the PagerDuty escalation policy — alerts include the slug, on-call resolves to the dashboard instantly.
https://app.datadoghq.com/dashboard/{dashboard-id}/{service} - b/trace
Default APM trace view for the active service.
Every incident starts with a trace; saving the URL kills the navigation tax.
https://app.datadoghq.com/apm/traces?env={env}&service={service} - b/logs
Default log search across critical services.
Replaces a Slack pin that drifts every time the search query changes.
https://app.datadoghq.com/logs?query=service%3A{service} - b/apm
APM service map.
Engineering leads review this weekly; new engineers reach it day one.
https://app.datadoghq.com/apm/services - b/slo
SLO dashboard with current burn-rate alerts.
Single page that engineering managers and product leadership both watch.
https://app.datadoghq.com/slo - b/synthetics
Synthetic monitoring runs.
On-call uses it to confirm whether an alert is real or a synthetic-test artefact.
https://app.datadoghq.com/synthetics/tests - b/incidents
Datadog Incident Management view.
When SEV-1 hits, b/incidents is the canvas the on-call commander opens first.
https://app.datadoghq.com/incidents
Common workflows
Three patterns that pay back in week one.
01
PagerDuty → b/dash → mitigation in three keystrokes
Configure PagerDuty escalation messages to include "Open b/dash-{{service}}" in the alert payload. The on-call engineer goes from receiving the page on their phone to the live dashboard in two taps. The runbook (see /use-cases/runbooks) lives at b/runbook-<service> on the same naming convention.
02
Cross-team SLO review
Engineering managers and product leadership both review b/slo weekly. The underlying dashboard changes (new services added, burn-rate thresholds tuned) without anyone re-bookmarking. The slug becomes the durable handle.
03
Onboarding the next on-call rotation
New on-call engineers learn five shortcuts in their first shift: b/dash-<their-service>, b/trace, b/logs, b/oncall (the active incident board), b/runbook-<service>. Day one, fully ramped.
With and without
Same Datadog. Different team experience.
Without shortcuts
Each engineer keeps a private bookmark folder of Datadog URLs. The on-call handoff includes a 30-minute "here are the dashboards" tour. Half the dashboards 404 after a service rename.
With BookSlash
b/dash-<service>, b/trace, b/logs, b/slo. Same shortcuts for every engineer, every shift, every browser. PagerDuty payloads carry the slug so the page → dashboard journey is one keystroke.
Frequently asked
BookSlash + Datadog
Yes. Slugs resolve from any browser, including mobile Safari and Chrome on iOS/Android. On-call engineers paged at 3 a.m. type b/dash-checkout in their phone’s address bar and land on the Datadog mobile dashboard in under 40 ms.
No — auth happens at the Datadog destination after the redirect. If the user is signed into Datadog (most teams use SSO), the dashboard loads instantly. If not, Datadog’s own login flow runs.
In PagerDuty, edit the escalation policy’s message template and add "Open b/dash-{{service.name}}". Most teams keep an "audit pass" board to make sure every service has a matching slug; the BookSlash CLI can list missing slugs against your service registry.
For a single dashboard, no. Use namespaced patterns: b/dash-checkout, b/dash-payments, b/dash-search. For an aggregate "all critical services" view, use b/dash-overview.
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