API Pollers for Pingdom Stopped Working After Upgrade to 2023.2

We use Solarwinds API pollers to gather data from Pingdom so we can log alerts for web sites that have become unavailable externally to our network.

As soon as we upgraded from 2020.2.6 to 2023.2 all of the pingdom API pollers stoped working. SWQL shows the LastPollTimestamp for the Pingdom pollers as just before the upgrade.

Other API pollers (e.g. for RabbitMQ) are still running and updating the LastPollTimestamp.

If I load up one of the pingdom API pollers and hit Send request it's pulling data back. I can see the unix timestamp is set correctly to the current time.

I've tried changing the timeout on the API pollers, I've moved the node to different polling engines. Rebooted the main polling engine.

What gives?

Find more posts tagged with

sam

api_poller

api poller

Accepted answers

BaldFeegle

We have the answer. It was a bug that caused API pollers to fail if the node was set to external. Fixed in 2023.2.1.

SAM 2023.2.1 Release Notes (solarwinds.com)

All comments

bmrad

Check out the known Poller issue for 2023.2.1 and see if that matches your issue- applies to both 2023.2 and 2023.2.1.
https://documentation.solarwinds.com/en/success_center/orionplatform/content/release_notes/solarwinds_platform_2023-2-1_release_notes.htm

Try applying the workaround.

It that doesn't match your issue, the workaround doesn't work or if you don't want to apply the workaround, then open a support case and post the ticket number back here.

Brian

marcrobinson

I was hoping this bug hadn't affected the API polling. I work with Pingdom and the SAM API monitor also. Are you able to test with something like Postman too?

BaldFeegle

We have a support case open already but sometimes the community knows more than support about bugs like this.

The known issue doesn't fit our symptoms, but we tried the workaround anyway. No effect.

BaldFeegle

It's not a problem with Pingdom, when I'm in the API poller I can hit Send request and it pulls the data back. Other API pollers like RabbitMQ are running so this update has somehow broken Pingdom API pollers.

marcrobinson

How many api requests are in the Pingdom poller that you have setup? I have noticed similar with one of the two pingdom pollers that I have setup. Your post provided some new thinking about what is happening. Other API pollers are generally fine also.

bmrad

Can you share the case number? I'd like to take a look.

BaldFeegle

Sure, it's 01394024.

BaldFeegle

We have the answer. It was a bug that caused API pollers to fail if the node was set to external. Fixed in 2023.2.1.

SAM 2023.2.1 Release Notes (solarwinds.com)

BaldFeegle

Our workaround was to set the nodes to ICMP only for now.

marcrobinson

Good catch. Never thought that an external node would be the problem.

BaldFeegle

Yeah, finding that as a known issue was quite the surprise.