Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Orion polling your additional pollers

We have our main application server and several additional polling engines.
Should we poll (monitor) them all from the main application server or just from any other additional pollers?
Just wondering if there is a best practice to polling additional Orion servers?

Find more posts tagged with

Accepted answers

All comments

bobmarley

Good question, don't know if there is a specific best practice but ours are staggered so no node is polling itself. We don't assign nodes to the main polling engines at all to offload that work onto the APE's. This leaves the extra resources on the main poller available for the website, alerts, reports, and all the other back end processes. It also makes a good landing pad for when new nodes are added, they end up on the main poller by default. So if there are additional tasks needed to fully monitor the node that the end user forgot to add its a good place to review the nodes before you deploy them over to an APE. We use our production Orion to monitor production Orion (itself) but also take advantage of our lab/test environment to provide additional monitoring of the production environment.

Here is an older post but has some ideas on monitoring your environment from outside Solarwinds. If you search Thwack you may find more like this Remotely Monitoring Solarwinds Services - Forum - THWACK EMEA - THWACK