GDMA Auto Setup is an advanced facility for having each GDMA client discover the facilities that need monitoring on that machine, reporting back that data, and having the server use it to configure or reconfigure the GDMA monitoring on that client. Discovery is based on instructions managed and provided on the GroundWork server. It is run on the client when triggered from the server, typically when the customer knows that the applications running on the GDMA client have changed. GDMA Auto Setup is available starting with the GDMA 2.6.1 release. It requires support on the server side, which is natively available starting with the GroundWork Monitor Enterprise 7.2.1 release. Server-side support can be made available for GroundWork Monitor 7.2.0 as well.

As a comparison of the two methods, GDMA Auto Setup is a generalization of the previous implementation of a similar feature which we called Automated Agent Registration (or Auto Registration, for short). Auto Registration allows a GDMA client to send in a small amount of basic information about itself, have that client machine be registered in Monarch, and have initial externals built so the client can begin monitoring. Nagios will begin accepting monitoring results from the GDMA client the next time a Commit is run.

The basic information sent in for Auto Registration is essentially the hostname and IP address, and the name of a host profile and optional service profile to apply. The profiles are a good start and may suffice if you have a fleet of identical machines.  A few automated server-side adjustments are possible, but there is no significant per-host customization reflecting the exact set of services being run on each GDMA client. GDMA Auto Setup adds the capability for the GDMA client to run a guided discovery of resources available on the client, making it possible to automatically adapt to the particulars of that client when monitoring is configured on the GroundWork server.