Skip to content
BlurFirst

How to Blur Infrastructure Metrics and Hostnames in Grafana While Screen Sharing

6 min read

Hide Grafana panel values, hostnames and IPs in labels and legends, datasource names, and alert contents before you present. A pixel blur that survives Zoom, Meet and Loom.

To hide infrastructure metrics and hostnames in Grafana while screen sharing, cover them with a pixel-level browser blur like BlurFirst before you present. Blur panel values, the hostnames, IPs and pod names in labels and legends, your datasource and connection names, and any alert contents on screen. The blur is painted into the page, so it holds up on Zoom, Google Meet, Microsoft Teams, Loom and every recorder — even though your panels keep refreshing live.

What a Grafana dashboard leaks to everyone watching

Grafana is where your topology lives in the open. Legends, labels and variable dropdowns spell out exactly how your infrastructure is named and segmented — a gift to anyone probing for a way in. The sensitive detail is scattered across the panels and the chrome around them.

  • Panel values — the current numbers on time-series, stat and gauge panels: error rates, request volumes, saturation and cost.
  • Hostnames, IPs and pod names in labels and legends — series labels like instance, pod, node and namespace that expose your internal naming and network layout.
  • Datasource and connection names — shown in panel editors and the datasource picker; they hint at your Prometheus, Loki or cloud setup.
  • Alert contents — firing alert rules, annotations and messages that describe thresholds and on-call detail.
  • Template-variable dropdowns — the variable pickers at the top of a dashboard that list every environment, cluster and service by name.
  • Dashboard names — often named after a team, customer or internal system.

Grafana metrics stream live and panels refresh on their own interval. That means a value you glanced past a moment ago is repainted with new data on the next tick — you can't rely on it having scrolled out of view.

Why a snapshot or a viewer role doesn't cover it

You could export a snapshot or hand out a read-only Viewer role, but neither helps when you are the one presenting the live dashboard from your own account to answer questions in real time. Permissions decide who can open Grafana; they don't decide what leaves your screen. A pixel blur keeps the live dashboard exactly as you use it and covers only the hostnames, values and alert text that shouldn't end up in the recording.

  1. 1

    Install and open your dashboard

    Add BlurFirst from the Chrome Web Store and open the Grafana dashboard you plan to share while it is still on your screen.

  2. 2

    Box-blur the panel values

    Press Ctrl/⌘ ⇧ Y, then drag a rectangle over each panel whose numbers should stay private. The box stays anchored to that panel even as the metric refreshes underneath it.

  3. 3

    Element-blur legends, labels and variable dropdowns

    Click a legend row, a label containing a hostname or IP, the template-variable picker, or the dashboard title to blur just that element. Click again to reveal one value on purpose.

  4. 4

    Save a per-site profile

    Save the blur for your Grafana host so it auto-applies. It stores only CSS selectors — never the metric data — and re-applies after Grafana re-renders, so covered panels stay covered across auto-refreshes.

  5. 5

    Keep Panic ready

    Press Ctrl/⌘ ⇧ H to blur the whole page instantly if an alert fires or you switch to a dashboard you hadn't prepared.

Grafana surfaceSensitive contentBest gesture
PanelsError rates, volumes, cost valuesBox blur per panel
Legends and labelsHostnames, IPs, pod/namespaceElement blur
Template variablesEnvironment and service listsElement blur on the dropdown
Datasource pickerDatasource and connection namesElement blur
Alerts / annotationsRules, thresholds, messagesBox + element blur
Dashboard titleTeam or customer nameElement blur
What to cover in Grafana

Everything happens locally. BlurFirst's content script runs in an isolated world with namespaced CSS, so it won't disturb Grafana's panels or interactions, and nothing you blur leaves the browser — the only network call is a license check. If a log or table panel contains addresses or keys, run Scan to detect and blur emails, phone numbers, credit-card numbers, SSNs and API keys locally. One honest limit: BlurFirst only covers content inside the browser tab, not a separate window or the whole desktop, so share the Grafana tab specifically.

Frequently asked questions

Will the blur stay in place as Grafana panels auto-refresh?

Yes. Saved blurs are stored as CSS selectors in a per-site profile and re-apply after each re-render, so a covered panel stays covered even as its metric streams new values.

Can I hide hostnames and IPs in the legend without hiding the graph line?

Yes. Use an element blur on the legend rows or the label text. The plotted lines stay visible so you can still discuss the trend without exposing which host is which.

Does blurring affect the dashboard for other viewers?

No. BlurFirst only covers pixels in your own browser tab. Other users, snapshots and the underlying metrics are unaffected.

Does the blur survive OBS, Loom and Zoom?

Yes. It is painted into the page as real pixels, so any recorder or screen-share captures it and it remains in screenshots of the shared feed.

Is any metric data sent anywhere?

No. BlurFirst is 100% local. What you blur never leaves the browser; the extension's only network request is a license check.

Blur it before you share it.

Hide any field, region or message on a page before your next call. Nothing you blur leaves your browser.

Add to Chrome