Skip to content

fix(grafana): container inventory published the compose file path - #115

Merged
Gerrrt merged 2 commits into
mainfrom
fix/inventory-panel-leak-and-screenshots
Aug 21, 2026
Merged

fix(grafana): container inventory published the compose file path#115
Gerrrt merged 2 commits into
mainfrom
fix/inventory-panel-leak-and-screenshots

Conversation

@Gerrrt

@Gerrrt Gerrrt commented Aug 21, 2026

Copy link
Copy Markdown
Owner

Two commits: a panel fix, and the screenshots for #12 that pass the checklist.

The panel fix

The Container inventory table on the Docker dashboard excluded fields by
name (Time, __name__, job, id, image, site, monitor, instance).
cAdvisor attaches every Docker label as a container_label_* field, and two of
them carry the absolute path of the compose file:

container_label_com_docker_compose_project_config_files = /home/robo/code/Gerrrt/HomeLab/stacks/observability/compose.yaml
container_label_com_docker_compose_project_working_dir  = /home/robo/code/Gerrrt/HomeLab/stacks/observability

So the panel rendered a username as two table columns — item 3 on the
pre-publish checklist in docs/images/README.md — and it went straight into the
first screenshot taken of it.

A denylist is the wrong shape: it needs updating every time a label appears, and
nothing fails when it isn't. Replaced with an allowlist of the three fields the
panel is for, so a new label cannot leak in by itself.

Verified by re-rendering — the table is now Container | Host | Uptime.

The screenshots

Two of four, not four.

File Verdict
network-snmp.png Included — full 24h, RFC1918 only, no MACs, no WAN address
ups-power.png Included — full 24h; the "no battery is installed" panel renders as intended
host-overview.png Held back — 14-hour hole (02:00→16:00) where the agent was down
docker-containers.png Held back — 22 of 24 hours empty; cAdvisor only started reporting correctly in #62

The two held back are a re-shoot, not a repair, which is what
docs/images/README.md has always said to do about a bad window: "Re-running
it tomorrow is the correct fix for a bad window, not cropping."
Committing them
with a caveat would publish two dashboards that read as "this stack does not
work".

The root README.md screenshot block stays commented until all four exist.

Refs #12.

Your Name added 2 commits August 21, 2026 21:58
The Container inventory table excluded fields by name — Time, __name__,
job, id, image, site, monitor, instance — and cAdvisor attaches every
Docker label as a container_label_* field. Two of those carry the
absolute path of the compose file:

  container_label_com_docker_compose_project_config_files
  container_label_com_docker_compose_project_working_dir

Both render as /home/robo/code/Gerrrt/HomeLab/..., so the panel put a
username on screen and into the first screenshot taken of it — item 3 on
the pre-publish checklist in docs/images/README.md.

A denylist is the wrong shape here: it has to be updated every time a
label appears, and nothing fails when it isn't. Replaced with an
allowlist of the three fields the panel is actually for, so a new label
cannot leak in on its own.

Verified by re-rendering: the table is now Container, Host, Uptime.
network-snmp.png and ups-power.png have a full 24 hours of data, no WAN
address, no MAC addresses, and no hostnames beyond the ones docs/hardware.md
already publishes.

The other two are deliberately absent rather than committed with a
caveat. host-overview.png has a 14-hour hole where the agent was down;
docker-containers.png is 22/24 empty because cAdvisor only started
reporting correctly in #62. Both are a re-shoot once the stack has a
clean day behind it, which is what docs/images/README.md has always said
to do about a bad window.

Refs #12
@Gerrrt
Gerrrt merged commit afe6a85 into main Aug 21, 2026
3 checks passed
@Gerrrt
Gerrrt deleted the fix/inventory-panel-leak-and-screenshots branch August 21, 2026 22:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant