Event Management Connector Instance - PUSH or PULL which is Better for SolarWinds

[sumanjungay]

Hi All,

We are doing POC on the Event Management for Solarwinds. We would like to understand  which connector instance would be the best  PUSH or PULL? 
Our Concern is if we use the PUSH connector:

1) Do we lose any alert aggregation

2)Does it apply the Alert correlations rules which are created by us and the OOB once?
3)Does Solarwinds team has to do lot of customization so that it will apply all the rules(Event Rules) created for Event Management?

We are looking for long term run where we can use  Advanced AIOps to do analysis and provide the suggestions.

[Tanushree Maiti]

Hi sumanjun 

The PULL method (using the out-of-the-box Event Connector hosted on a MID Server) is generally the preferred approach because:

1. ServiceNow retains full control over the process.
2. Data is securely retrieved via the MID Server from the SolarWinds Orion SQL database, without exposing it to the public internet.
3. Being an out-of-the-box feature, it is simpler to maintain, upgrade, and is backed by official support.

[AndersBGS]

Hi @Tanushree Maiti 

Why would you utilize pull? You will make additional load instead of leading Solarwinds push when there is something to push... You are still in full control according to event rules, alert rules and event correlation rules. 

[sumanjungay]

Hi @AndersBGS ,

So you are saying that when we use the PUSH connector the Alert Correlation Rules and Event Rules will be applied OOB? Also said that PUSH connector will be considered as non OOB script as we develop as per our convenience. ServiceNow will not provide the support on this right?