How to Blur Hosts, Logs and Metrics in Datadog While Screen Sharing
Hide Datadog hostnames and IPs, log lines with PII and tokens, APM traces and monitor contents before you present. A pixel blur with a panic hotkey for the live log stream.
To hide hosts, logs and metrics in Datadog while screen sharing, cover them with a pixel-level browser blur like BlurFirst before you present. Blur hostnames and IPs in the Infrastructure List and Host Map, log lines that carry PII or tokens, APM traces with endpoints and user IDs, and any monitor or alert contents on screen. The blur is painted into the page, so it survives Zoom, Google Meet, Microsoft Teams, Loom and every recorder — and a panic hotkey is on hand for the live-tailing log stream.
Everything Datadog surfaces on a shared screen
Datadog concentrates your most sensitive operational data — who your hosts are, what your users do, and what your logs happen to contain — into a handful of dense views. The risk is spread across infrastructure, logs, traces and alerting.
- Hostnames and IPs in the Infrastructure List and Host Map — the full inventory of your fleet, tagged by environment, service and team.
- Log lines containing PII, tokens or internal URLs — the Log Explorer shows raw payloads, and a single line can carry an email, a bearer token or a private endpoint.
- APM traces with endpoints and user IDs — flame graphs and span detail expose route names, query parameters and identifiers.
- Monitor and alert contents — thresholds, notification messages and the tags that describe how you page on-call.
- Dashboard tiles — the same metric widgets you would guard in any observability tool.
- The org name in the top navigation, which can reveal a customer or an internal codename.
The most volatile surface is the log stream. When live-tailing is on, new lines scroll in continuously, so a token or email can appear a fraction of a second after you glance away. That is exactly the moment to reach for the panic hotkey rather than trying to hide one line at a time.
Why sensitive-data scanners and roles don't cover presenting
Datadog's Sensitive Data Scanner and RBAC are worth configuring, but scanners run on ingestion rules you may not control for every source, and roles govern who can log in — neither stops a private value from appearing on your screen when you present from a full-access account. A pixel blur is a presenter-side control: it keeps the live views exactly as you use them and covers only the hosts, log lines and trace detail that shouldn't reach the recording. Treat it as one layer alongside your ingestion-side redaction, not a replacement.
- 1
Install and open the view you'll share
Add BlurFirst from the Chrome Web Store and open your Datadog dashboard, Log Explorer or APM view while it is still on your screen.
- 2
Turn off live tailing, then box-blur the stream
Pause the log stream if you can, press
Ctrl/⌘ ⇧ Y, and drag a rectangle over the log panel or the columns that carry payloads. The box stays anchored as you scroll. - 3
Element-blur hostnames, trace detail and the org name
Click a hostname or IP in the Infrastructure List, a span's endpoint or user-ID field, a monitor's message, or the org label to blur just that element. Click again to reveal one value on purpose.
- 4
Save a per-site profile
Save the blur for your Datadog host so it auto-applies. It stores only CSS selectors and re-applies after Datadog re-renders, so covered panels stay covered as data updates.
- 5
Keep Panic on your fingertips
With live tailing on, keep
Ctrl/⌘ ⇧ Hready — one keystroke blurs the entire page the instant a sensitive log line scrolls in, and you can reveal safely afterward.
| Datadog view | Sensitive content | Best gesture |
|---|---|---|
| Infrastructure List / Host Map | Hostnames, IPs, tags | Element + box blur |
| Log Explorer | PII, tokens, internal URLs | Box blur + Panic hotkey |
| APM traces | Endpoints, query params, user IDs | Element blur on spans |
| Monitors / alerts | Thresholds, messages, tags | Element blur |
| Dashboards | Metric tile values | Box blur per tile |
| Top nav | Org name | Element blur |
It all runs locally. BlurFirst's content script lives in an isolated world with namespaced CSS, so it won't interfere with Datadog, and nothing you blur leaves the browser — the only network call is a license check. In the Log Explorer, run Scan to detect and blur emails, phone numbers, credit-card numbers, SSNs and API keys in one pass; it matches patterns, not free-text names. One honest limit: BlurFirst only covers content inside the browser tab, not other windows or the whole desktop, so share the Datadog tab rather than your full screen.