Solarwinds Additional pollar

why we are required to connect Solarwinds main pollar to additional pollar

Find more posts tagged with

Comments

The additional polling engine is used to a)increase the number of nodes that can be polled or b)locate a poller closer geographically to the nodes being polled or c) locate a poller in a security enclave with the nodes being polled.

There may be other reasons as well but these are the three main considerations I am aware of.

The main polling engine can be used without an APE if there are not too many nodes and all are accessible without too much delay or security concerns.

verwin_u

SolarWinds requires connecting the main polling engine to additional polling engines (APEs) to increase monitoring capacity and distribute load. This helps prevent the main poller from becoming overloaded and allows it to focus on core functions like the web console, alerting, and reporting. Additional polling engines can also be used for centralized deployment and to run discovery from a specific engine.

Here's a more detailed explanation:

Increased Capacity:
By distributing the workload, you can monitor a larger number of devices without straining the main polling engine, according to SolarWinds.
Load Balancing:
APEs can be used to offload certain monitoring tasks from the main engine, allowing it to perform better, says SolarWinds.
Centralized Deployment:
APEs can be used to create a centralized deployment where multiple nodes are monitored by different pollers, as explained by SolarWinds.
Specific Engine Discovery:
You can run a discovery process from a specific APE, which can be useful for certain network configurations or when you need to isolate discovery activities, according to SolarWinds.

verwin_u

Ranjit1

what information getting shared between MPe to APe?

dilbert1234

The main poller handles tasks that require communication with the APE. Things like HA, alerting, job scheduling, and messaging are handled at the main poller level.

Ranjit1

Thanks for the answer, this what I was looking for

verwin_u

The Main Polling Engine (MPE) and Additional Polling Engines (APEs) in SolarWinds share information for various tasks, including High Availability (HA), alerting, job scheduling, and messaging. The MPE handles core functions like the web console, reporting, and APE management, while APEs focus on polling and gathering device statistics.

Here's a more detailed breakdown of the information exchanged:

HA:
If the MPE fails, the APEs can take over its functions, ensuring continued monitoring and reporting.
Alerting:
The MPE receives alerts from APEs, which are then processed and displayed in the SolarWinds console.
Job Scheduling:
The MPE schedules tasks for APEs, such as polling and data collection.
Messaging:
The MPE communicates with APEs through RabbitMQ for data exchange and other operational tasks, says a SolarWinds documentation article.
Data:
APEs collect device statistics and send them to the MPE, which stores them in the SolarWinds Platform database.
Configuration:
The MPE manages the configuration of APEs, including their tasks and settings.
Installation:
During the installation of new SolarWinds Platform products, data can be transferred from the MPE to APEs.

ShriniwasJ

The main reason is to distribute the load of polling data from a large number of nodes.
The Main Poller has resource limitations (CPU, memory, network).
Additional Pollers help avoid performance degradation when the monitored environment grows.