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

APM on Additional Poller

We have an open ticket on this, but I wanted to touch base with the community as well. We have NPM with an additional poller. APM is running on the server with NPM and it works fine. However, any device that is polled by the additional poller cannot be monitored correctly with APM. We have installed an instance of APM on the additional poller. Some of the troubleshooting has had us verify connectivity between the two pollers, repair Job Scheduler on the Primary and Job Engine and Orion Module Engine on both pollers. Nothing has worked yet. Maybe somebody out there can lead me in the right direction. Thanks.

Find more posts tagged with

Accepted answers

All comments

martin.susil

What is the support ticket number?

So you have APM installed on both - main Orion and Additional Poller?

What polling engine mode are you using (can be set in APM Settings - Data & Database Settings) - Local-Only or Poller-Bound?

FormerMember

Case # 224718 and we have changed the polling engine mode to Poller-Bound per instruction. Yes we have APM installed on both main and additional poller. It works correctly on main but not on additional.

Donald_Francis

I have historically stuck with local only polling settings as every time I have tried poller bound something bad happens. And basically every time I put a ticket in for trouble with it I was advised to just leave it as local.

FormerMember

Thanks Donald. We originally had it local only, but one of the troubleshooting steps had us change it to poller bound. I just changed it back and that unfortunately did not resolve the issue. It was worth a try.