I've picked up the management of our existing Solarwinds environment which has been in place for close to 10 years.
We are a global firm with office (and virtualized servers) across the globe, but IMO we only have a small set of nodes, interfaces and volumes relative to our size and what a single Solarwinds can handle.
Our current architecture is set up as seen below.
NETWORK ELEMENTS | 5663 |
NODES | 887 |
INTERFACES | 3173 |
VOLUMES | 1603 |
| |
ALERTS | 406 |
EVENTS | 145644 |
POLLERS | 22592 |
POLLING ENGINES | 2 |
MPE | 2nd Poller |
---|
ENGINE STATUS | Status Polling Engine Active | ENGINE STATUS | Status Polling Engine Active |
---|
TYPE OF POLLING ENGINE | Primary | TYPE OF POLLING ENGINE | Additional |
POLLING ENGINE VERSION | SolarWinds Orion Core Services 2016.2 | POLLING ENGINE VERSION | SolarWinds Orion Core Services 2016.2 |
IP ADDRESS | 10.10.10.24 | IP ADDRESS | 10.10.10.25 |
LAST DATABASE SYNC | 16 seconds ago | LAST DATABASE SYNC | 15 seconds ago |
POLLING COMPLETION | 99.85 | POLLING COMPLETION | 99.99 |
ELEMENTS | 4446 | ELEMENTS | 1211 |
NETWORK NODE ELEMENTS | 591 | NETWORK NODE ELEMENTS | 296 |
VOLUME ELEMENTS | 1143 | VOLUME ELEMENTS | 454 |
INTERFACE ELEMENTS | 2712 | INTERFACE ELEMENTS | 461 |
SAM APPLICATION POLLING RATE | 29% of its maximum rate.» Learn more | SAM APPLICATION POLLING RATE | 6% of its maximum rate.» Learn more |
POLLING RATE | 55% of its maximum rate.» Learn more | POLLING RATE | 14% of its maximum rate.» Learn more |
HARDWARE HEALTH POLLING RATE | 4% of its maximum rate.» Learn more | HARDWARE HEALTH POLLING RATE | 1% of its maximum rate.» Learn more |
VIM.VMWARE.POLLING | 2 | VIM.VMWARE.POLLING | 15 |
TOTAL JOB WEIGHT | 2595 | TOTAL JOB WEIGHT | 1038 |
NUMBER OF HW HEALTH MONITORS | 102 | NUMBER OF HW HEALTH MONITORS | 36 |
NUMBER OF HW HEALTH SENSORS | 3496 | NUMBER OF HW HEALTH SENSORS | 1434 |
Now i know that we need to upgrade to the latest software version and that is already on my road map.
Second to this is that the environment needs to be rebuilt using Server 2016 and SQL 2017.
But i have a few other questions:
- Do we need the additional poller based on the above number of nodes, interfaces and volumes?
- Can SQL run happily on a SQL AlwaysOn cluster?
- If we run the DB on a AlwaysOn cluster then for true HA we would also need to purchase an HA license/setup HA on the Solawrinds side. Correct?
- Would we benefit from a simplified polling infrastructure but have additional web interfaces?
thanks