---
title: "Comment by StackShortlist on \"Key metrics we actually put on a monitoring dashboard\" | Hashnode"
description: "Keeping the dashboard to a short set of tiles that answer what got worse after a release is a good filter. One practical addition is a per template view, since"
url: "https://hashnode.com/posts/key-metrics-we-put-on-a-monitoring-dashboard/6ad8783dbeae526b8f66c420/comment/6ad9e7a1272f84288b2315a9"
---

[Discussion](https://hashnode.com/posts/key-metrics-we-put-on-a-monitoring-dashboard/6ad8783dbeae526b8f66c420)

Comment [Key metrics we actually put on a monitoring dashboard](https://hashnode.com/posts/key-metrics-we-put-on-a-monitoring-dashboard/6ad8783dbeae526b8f66c420)

[StackShortlist](https://hashnode.com/@veristria)

[Oct 22](https://hashnode.com/posts/key-metrics-we-put-on-a-monitoring-dashboard/6ad8783dbeae526b8f66c420/comment/6ad9e7a1272f84288b2315a9)

Keeping the dashboard to a short set of tiles that answer what got worse after a release is a good filter. One practical addition is a per template view, since a slow product page and a slow blog post need different fixes and averaging them hides both. Do your agency users ask for a client facing version of that view?

[Apogee Watcher](https://hashnode.com/@apogeewatcher)

[Oct 23](https://hashnode.com/posts/key-metrics-we-put-on-a-monitoring-dashboard/6ad8783dbeae526b8f66c420/comment/6ad9e7a1272f84288b2315a9#reply-6adb1fc33c3d1bd2448355e2)

They do ask for a client-facing version, but usually not a second full dashboard. What they want is a shareable report that shows Core Web Vitals by template over the period, so the account lead can send progress without handing over the monitoring board the team uses. The per-template split matters for the same reason you named: a slow product page and a slow blog post need different fixes, and a site-wide average hides both. The short internal board stays for the people who open the tickets.
