-
Notifications
You must be signed in to change notification settings - Fork 144
How to distribute load between pollers
Oleksandr Manetskyi edited this page May 1, 2024
·
1 revision
HCO provides ability to distribute load between Polling engines. Node polling is assigned to a specific Poller Engine and can be moved between Poller Engines later via SDK.
https://{IP}:17778/SolarWinds/InformationService/v3/Json/Query?query=SELECT EngineID, ServerName, IP, ServerType, Elements FROM Orion.Engines
Authorization: {{basicAuthorization}}
Content-Type: application/json
{
"results": [
{
"EngineID": 1,
"ServerName": "Hostname1",
"IP": "10.10.10.10",
"ServerType": "Primary",
"Elements": 3
},
{
"EngineID": 2,
"ServerName": "Hostname2",
"IP": "10.10.10.11",
"ServerType": "Additional",
"Elements": 6
}
]
}
Elements property shows the number of elements (Nodes, Interfaces, etc.) assigned to the Polling engine.
Orion.Nodes.Uri
is needed to specify the Node to change Polling engine for.
https://{IP}:17778/SolarWinds/InformationService/v3/Json/{NodeUri}
Authorization: {{basicAuthorization}}
Content-Type: application/json
{
"EngineID": 2
}
Returns null with Status 200 OK.
- About SWIS
- Connecting to SWIS
- SWQL Functions
- REST
- PowerShell
- Alerts
- Creating custom properties
- Poller Types
- Network Performance Monitor
- NetFlow Traffic Analyzer
- Network Configuration Manager
- IP Address Manager
- Server & Application Monitor
- Log Analyzer
- Schema reference