Probes that support partial graph publishing (incremental discovery) for discovery_server optimization
search cancel

Probes that support partial graph publishing (incremental discovery) for discovery_server optimization

book

Article ID: 232785

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

I am seeing that my probe_discovery queue has a very hard time keeping up with the load placed on it. What probes can I set for incremental discovery?

Environment

Release : 20.x

Component : discovery_server

Cause

After this initial discovery process, the monitoring probes collect and publish data to the Discovery Server on a regular schedule. You can optimize the efficiency of this publishing process by configuring the probe to publish only the delta values for the data it sends to the Discovery Server.

 

Resolution

List of probes supporting partial graph publishing:

aws
azure
cohesity
celerra
clariion
cloudera
docker_monitor
flume_monitor
hitachi
hp_3par
ibm_svc
meraki
nutanix_monitor
office365
openstack
oozie_monitor
purestorage
redis
solr_monitor
vmware
xenserver
xtremio
zones

Steps to enable partial discovery:

- select the probe in Admin Console
- click Raw Configure
- select the setup section
- click on the plus to the right of the Value title (to add a new key as needed)
- create a key with the following details

Key = discovery_server_version
Value = 8.51

- select Update
- deactivate/activate the probe

After making this change you should see the following in the probes log with loglevel=5:

DefaultDiscoveryPublisherEngineService.start: Discovery publishing is running in PUBLISH_INDIVIDUAL_DEVICE_UPDATE_GRAPHS mode