Plenty of posts out there on this topic, but really need to get more attention. How can the discovery job be set via API to enable port discovery for UDT?
Admittedly I have never looked at UDTs API capabilities in Orion. Having recently spent some time digging around discovery profiles let me share what I know and perhaps there may be something of benefit here in the absence of native API features for UDT
The configuration of a scheduled discovery can be considered as 2 elements
1. The definition of the discovery profile attributes such as name, timeout, hops allows ICMP only etc.
2. The configuration of the modules, referred to as plugins, where we will define things like the list of i.ps or ranges, and other module-specific elements for NCM, SAM, VIM etc. These are all saved in the PluginConfigurations field of the DisoveryProfile.
The PluginConfiguration also includes KnownTypes and so UDT ports will be discovered if creating a discovery profile via API (assuming UDT is installed and thus a KnownType)
SolarWinds.Orion.Core.Models.Discovery.CoreDiscoveryPluginConfiguration,SolarWinds.Orion.Core.Models.V1 SolarWinds.VIM.Common.Configuration.VimDiscoveryPluginConfiguration,SolarWinds.VIM.Common SolarWinds.NCM.Contracts.Discovery.NcmDiscoveryPluginConfiguration,SolarWinds.NCM.Contracts SolarWinds.Interfaces.Common.Models.Discovery.InterfacesDiscoveryPluginConfiguration,SolarWinds.Interfaces.Common SolarWinds.APM.BlackBox.Sql.Common.Models.Discovery.ApmBlackBoxSqlDiscoveryPluginConfiguration,SolarWinds.APM.BlackBox.Sql.Common SolarWinds.APM.BlackBox.Exchg.Common.Models.Discovery.ExchangeDiscoveryPluginConfiguration,SolarWinds.APM.BlackBox.Exchg.Common SolarWinds.APM.BlackBox.Wstm.Common.Models.Discovery.DiscoveryPluginConfiguration,SolarWinds.APM.BlackBox.Wstm.Common SolarWinds.APM.BlackBox.IIS.Common.Models.Discovery.IISDiscoveryPluginConfiguration,SolarWinds.APM.BlackBox.IIS.Common SolarWinds.APM.BlackBox.ActiveDirectory.Common.Models.Discovery.ActiveDirectoryDiscoveryPluginConfiguration,SolarWinds.APM.BlackBox.ActiveDirectory.Common SolarWinds.UDT.Common.Models.Discovery.UDTDiscoveryPluginConfiguration,SolarWinds.UDT.Common SolarWinds.Orion.SCM.Models.Discovery.ScmDiscoveryPluginConfiguration,SolarWinds.Orion.SCM.Models
I say discovered rather than imported because there are additional elements in the PluginConfiguration that look to be interesting for UDT
false Up true false Access Trunk Unknown false
There are no API methods available to update these values for UDT, however, I have successfully used direct SQL commands to update other values and behavior.
In my initial testing, updating a DiscoveryProfile with the query below and importing the results did not have the expected port types.
update DiscoveryProfiles set PluginConfigurations = replace(PluginConfigurations,'false','true')
