What is the purpose of dashboards in NPM, and how can you tailor them to operators?

• A. Dashboards provide real-time visuals of performance data; you can customize widgets, layouts, and who can view them via roles.
• B. Dashboards are static reports stored nightly; you can't customize who views them.
• C. Dashboards only show alert events; widgets and layouts cannot be altered.
• D. Dashboards automatically adjust to device type and cannot be customized.

Answer: (A)

Dashboards in NPM are meant to give quick, real-time visuals of how the network is performing, so operators can spot issues, monitor health, and see where to act at a glance. They’re not just static pages; they stream live data and help you understand current conditions across devices, interfaces, and paths.

You can tailor them extensively for operators. This means adding and arranging widgets that show the exact metrics you care about—things like device CPU and memory, interface utilization, latency, packet loss, and top-talkers—and choosing how those metrics are presented (graphs, gauges, tables, maps). You can customize the layout, pick the time range, and apply filters so only relevant devices or groups appear. Important thresholds and color coding can highlight problems automatically. Access is controlled via roles, so you can decide who can view or modify a dashboard, ensuring operators see what’s appropriate for their role. This combination of real-time visuals, flexible widgets and layouts, and role-based visibility makes dashboards a powerful, operator-focused tool.