Auto discovery for APM Plugin


Plugin discovery allows you to discover and monitor servers and applications automatically during the initial startup of the Plugin setup. You can specify the total count of applications that are to be added for the discovery along with their discovery order for performing plugin-discovery. The Default Maximum Applications count is 50. If the count of added applications remains under the default limit, MS SQL monitors will be added accordingly. For eg: Consider added applications count to be 25. Here 25 more MS SQL monitors can be added. This occurs only upon the initial startup of the Plugin for Trial and Professional Edition users in Windows. Using NMap discovery, apps running in default port will be detected. Whereas NETSTAT discovery detects actual running port using credentials provided for OPM servers, even if default port is changed.

By default, plugin-discovery will be enabled in Applications Manager. If users need to disable or discovery only servers, they can configure by specifying appropriate values for the property AUTODISCOVERY in the AutomaticDiscovery.properties file. In addition, you can also specify additional criteria with which the plugin-discovery is to be performed by updating the values for their respective properties in the file. Upon updating the values, discovery profile will be created to start discovery on added servers and applications.

Note: While syncing credentials with OpManager, if a Windows server is added to OpManager with its credentials, those credentials will be synced with the Exchange server, Active Directory, MS SQL, and IIS monitor during the initial plugin startup.

Following are the list of properties that can be configured in the AutomaticDiscovery.properties file located under the OpManager\AppManager\working\conf\itomdiscovery directory:

Note: Since plugin-discovery occurs only on initial startup, the required properties should be configured in the file before initial/first startup.

Property Description and possible values
AUTODISCOVERY Allows you to enable or disable the plugin-discovery feature in Applications Manager. Possible values are:
  • enable - Both server and applications will be discovered during initial startup.
  • disable - Plugin discovery feature will be disabled.
  • servers_only - Only servers will be discovered during initial startup, application discovery will be skipped.

Note: Default value for this property will be enable.

TOTAL_APPLICATION_COUNT_TO_BE_ADDED_VIA_AUTODISCOVERY Allows you to specify the count of applications to be added via plugin-discovery, By default, 50 applications will be added.

Note: Default value for this property will be 50.

ORDER_OF_APPLICATIONS_TO_BE_ADDED_VIA_DISCOVERY Allows you to prioritize applications added via plugin-discovery by changing the priority order. By default, the first given application will have highest priority.

Note: Refer to the Priority order of plugin-discovery section for default priority order.

On performing the above configurations and starting Applications Manager for the first time, plugin discovery will occur and discovery profile will be created, wherein all servers and applications that are added via plugin-discovery can be viewed under the profile name Auto discovery.

In this newly-created discovery profile, only the View Report Page option will be enabled, whereas other options such as View Discovered Details, Edit, Delete, Rediscover now, and Schedule discovery will be disabled.

Priority order of Plugin discovery

The following are the servers and applications auto-discovered in Applications Manager Plugin, arranged priority-wise:

  1. Active Directory
  2. Exchange Server
  3. MS SQL
  4. Oracle
  5. IIS Server
  6. Tomcat Server
  7. JBoss Server
  8. MySQL
  9. PostgreSQL
  10. MongoDB
  11. Apache Server
  12. WebLogic Server
  13. Redis
  14. RabbitMQ
  15. DB2
  16. WebSphere Server
  17. Docker
  18. Nginx
  19. Memcached
  20. GlassFish
  21. Sybase ASE
  22. Cassandra
  23. Resin
  24. JDK 1.5