SAM 2020.2.5 hf1 & "it’s restricted to the Main Polling Engine"

robertcbrowning

I see in the release notes that

"Application Dependency updates: Queries and connection-matching algorithms were revamped to improve performance by reducing Orion server CPU usage during data processing, as well as CPU usage by the SAM.ADM Connection Detector process. In addition, polling no longer occurs on Additional Polling Engines; it’s restricted to the Main Polling Engine so you see the latest data sooner."

What are the implications for a multi-engine multi-module Orion?

What happens if APEs and MPE are in different locations with different ACLs to reach their target nodes and the MPE does not have access to the target node? 

Would we have to move nodes about or can nodes they stay on their existing APEs and just an internal function happens n the MPE?  

robertcbrowning

In the New features and improvements section of the SAM 2020.2.5 release notes at https://documentation.solarwinds.com/en/success_center/sam/content/release_notes/sam_2020-2-5_release_notes.htm the paragraph of Application Dependency says “In addition, polling no longer occurs on Additional Polling Engines; it’s restricted to the Main Polling Engine so you see the latest data sooner.”

This was a concern to me as, in a multi-engine Orion, differing engine routes and rules could interfere with metric collection. I raised it with support and the devs replied with “ADM polling has not changed; it is still performed by the agent using ADM plugin. Any changes done is simply to improve performance. I agree that the article can generate confusion with the customers, I recommend leaving a feedback on the article.”

So it’s not actually a problem after all, but it does highlight the importance of reading the release notes very carefully and questioning anything that could raise issues in your environment.