A problem-monitoring dashboard in Checkmk gives operators one screen for current host and service issues, unhandled counts, and the views needed during triage. It fits wall displays, shift handovers, and team workspaces where the default dashboard is too broad or too private.
Customize → Visualization → Dashboards creates the dashboard shell. The Unrestricted dashboard type works for a shared problem dashboard because dashboard and widget filters can narrow the content later, while Specific host or Custom limits the available data before widgets are added.
Built-in dashboards are protected from direct editing, so clone one when it already has the right shape or create a new dashboard for a focused operations view. The Anchored layout works in all editions, while Responsive layout is a commercial-edition option in current Checkmk releases; choose the layout before saving because the layout type controls how widgets are placed.
Related: How to acknowledge a problem in Checkmk
Related: How to inspect a Checkmk service metric graph
Related: How to schedule Checkmk downtime
Clone a built-in dashboard instead when the existing Problems dashboard already has most of the widgets and filters the operations team needs.
A name such as Operations problem watch is easier to recognize in dashboard menus than a generic team or location name.
Use Anchored for Checkmk Community or for dashboards that must work across editions. Use Responsive only when the site edition provides it and manual drag-and-drop placement is required.
New dashboards are private by default until access is widened.
For host names, Checkmk evaluates regex filters. Use a precise pattern such as ^web- when the dashboard should show only hosts whose names start with web-.
Do not test shared access with an administrator session only; administrator permissions can hide missing access rules for normal operators.
https://monitoring.example.net/mysite/check_mk/dashboard.py?name=ops_problem_watch