How to use i-Vertix Autodiscovery

i-Vertix Autodiscovery is one of the features that are included in our i-Vertix Monitoring solution. Its job is to optimise the monitoring configuration by automatically recognising services and adding them to your monitoring system, thus guaranteeing a 100% coverage while also helping you save a lot of time.

The Autodiscovery feature can detect hundreds of different services, but here is a list of the most popular ones:

  • Basics: network interfaces across different devices and OS
  • Basics: disks, volumes, datastores, partitions etc. across different devices, OS, VMWare, Nutanix
  • Basics: services and processes for different OS
  • Storages: Volumes, groups, pools, LUN’s, FC Ports, shares etc.
  • Cloud: instances, virtual machines, resources etc. on AWS, MS Azure
  • Office 365: services, One Drive sites, SharePoint sites
  • Databases: Instances, Databases, Tablespaces etc. for MS SQL, Oracle, Informix, MongoDB, PostgreSQL etc.
  • Kubernetes & Prometheus: daemon sets, deployments, namespaces, nodes, pods etc.
  • Tomcat: data sources, web apps, applications



Manual & automatic mode

There are two main ways to use i-Vertix Autodiscovery, which mostly differ for one important aspect:


  1. Manual mode: the user manually selects a host and runs the discovery whenever needed. Both the support for i-Vertix Poller and the MSP mode are included.
  2. Automatic mode: the user can completely automatise the monitoring configuration by creating one or more autodiscovery jobs and programming a schedule that will tell the system when to automatically run the discovery. Moreover, it is possible to run a massive autodiscovery on hundreds of thousands of hosts without any kind of performance limitation on the system. The automatic mode also offers support for both i-Vertix Poller and the MSP mode.




How to create an autodiscovery job

Creating an autodiscovery job is quite simple. There are 5 main option fields that need to be filled out:


  1. Job Name (we recommend a name that describes its purpose)
  2. Host selection
  3. Host Group selection
  4. Discovery template
  5. Scheduling


One job can execute the discovery of one or more hosts/host groups and it is possible to configure more than one job simultaneously.



For further information please contact us at info(at)