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
Store

Check latency between polling engines (Poller Health)

Hi Team,

I am having latency between polling engines (Poller Health) issues in my environment, due to this we are getting multiple alerts. Can you someone help to fix this issue?

I have checked port 17777 and telnet is working.

TITLE: Check latency between polling engines (Poller Health)
DISCOVERED: 5/24/2024 6:26:41 AM
RESOLUTION: Please ensure port 17777 is available for communication between all polling engines. Slowness/delays/other issues may occur if there is a high latency between polling engines. See KB MT34656.
DESCRIPTION:
Polling Latency Check Results from Main Poller (XXXX). Threshold values set are Warning Threshold : 100 ms and Failure Threshold : 300 ms.

Destination Server : Additional Poller (XXXX)
Response Time : 533 ms
Status : FAILURE

Find more posts tagged with

Accepted answers

adam.beedell

Or to fix.
Move them closer together?
Retuce contention across the route?
Something at capacity along the way? Upgrade that
Reduce the network flow of something
fix a route that's routing somewhere long if there's a shorter route available somehow.

something like that

All comments

vinay.by

1. Did you try rebooting your Main Poller and Additional Poller ? That isn't the fix, but then did you try rebooting them and then running a check ?

2. Do you have anything running on your VM's ? (Main Poller or Additional Poller). Like say suppose any anti virus software or Windows Defender/Firewall etc ? Next step would be to disable your Windows Defender/Firewall. If that can't be done then allow a pass through for all your SolarWinds Services and Folders on it.

3. Its not always the network that is the reason for latency, it could be something to do with the performance/capacity issues of your Main/Additional Poller itself, which is why I am asking you to check the above things.

4. As well revisit SolarWinds pre-requisites, check if your hardware sizing is fine, check if your poller is not overloaded etc

Naresh.Inala

Thanks Vinay for your suggestions, let me check and see if this can fix my issue.

adam.beedell

Given that this in in the NPM forum. Node per poller, monitored from the MPE or one closest to the DB, track he latency stat from there

adam.beedell

something like that

Naresh.Inala

Thanks Adam, let me check your points.