How to disable SG-Solarwind?

[Anyhow]

I have a straight forward requirement to disable solarwind so there is no CI created with discovery source SolarWind

[Anyhow]

There is no record for SG-Solarwind in the flow context engine. I have shared the screenshot of flow context engine,Import schedules for SG-Solarwind and CIs with discovery source as SG-Solarwind

[Kieran Anson]

Your screenshots don't show CIs being created. Existing CIs being updated could be by different data sources...the discovery sources reflects the first data source to bring in that config item 

[Sean Webster]

This is not fully correct. discovery_source off the cmdb_ci table is set by the most recent defined IRE data source that has updated that respective CI, that is native platform of course as you could always just force that value via GlideRecord method from some scripted resource.
The only way to track the created will be with sys_audit record for the original values and/or sys_created_by on the XML of the CI record; both being dependent on following best practices on using a dedicated user for the discovery source's respective transformation transactions, namely as the Run-As for the scheduled import. 

[Sean Webster]

We have an out-of-box feature for this, cmdb_ire_data_source_rule is where we store those rules. If you have a rule for Discovery Source of SG-SolarWinds, and set it 'Insert Not Allowed' to true, for example:

NOTE: I did set this for Computer class, this will allow inheritence to the Child classes, like Server, Windows Server, etc... I did this as an example, you could just set this at Configuration Item or Hardware class and get a larger scope of a deny for INSERT. 

Another important note is this is a data source rule, this prevents INSERTS of new CIs in to the CMDB. This does not prevent updates, we control that with the reconciliation rules for the respective class. The IRE(Identification and Reconciliation Engine) uses this to determine what discovery source, in which order, can update what attribute and when it can overide something stale from a more prioritized discovery source. This can be managed in the 'CI Class Manager' or with a record on cmdb_reconciliation_definition, for example:

Please mark this is an accepted solution if this has resolved your issue.

Cheers,

Sean