This asks where you find the usage data for how many elements Orion is actively polled. The total number of elements polled is a licensing/usage metric, so it belongs in the license-related area of the web console. The License Details section is designed to show license information, including the total elements allowed and the number currently polled. That makes it the best place to view how many elements are being monitored. Other menus don’t track this metric. Account Limitations may outline restrictions but not the live polled count; DirectLink accounts relate to remote connectivity options, not element polling; Web Console Settings controls UI preferences and console behavior, not license usage.

Troubleshooting an NPM deployment relies on gathering evidence from multiple log sources that cover the Windows OS, the Orion platform itself, and the database that underpins the system. Windows Event Viewer captures OS-level events, service start/stop issues, and errors that can block components from running. Orion logs provide insight into the NPM components and their internal events, helping you see where a deployment or service operation is failing. SQL Server logs are important because the Orion (NPM) database stores configuration data and performance metrics; problems there can show up as connectivity failures, database errors, or query timeouts that halt or slow deployment. Orion-specific logs like Diagnostic and Resource Manager logs deliver detailed telemetry about component health, resource usage, and diagnostic data that can pinpoint misconfigurations or performance bottlenecks. Core and BizLayer events reflect the central services that drive the Orion platform, so issues there often explain why a deployment isn’t functioning as expected. Using this combination gives a complete view of what’s happening, whereas relying on only one source (such as OS logs or only Windows logs) can miss deeper causes.

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.

Regular, comprehensive backups are essential for SolarWinds NPM Orion. The best approach is to back up the Orion database to capture all monitoring data and history, and to take configuration snapshots so you can recreate the deployment, including settings, dashboards, templates, and customizations. A tested disaster recovery plan ensures you can restore service quickly, which means rehearsing the restore process, defining recovery goals (RTO/RPO), and having clear steps and contacts. Keeping the backup version in sync with the exact Orion version in production is important because mismatches can cause restore failures or data integrity problems. Verifying backups means performing restore tests or integrity checks to confirm you can actually recover the data and that the backups aren’t corrupted. In practice, store backups off the primary server, back up on a regular schedule, and follow retention policies to balance risk and storage needs.