GDMA FAQs

Version 3 by Bren Eckles
on Sep 17, 2017 18:20.

compared with
Current by Bren Eckles
on Sep 23, 2017 10:34.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (2)

View Page History
h6. *Q:* How can I speed up auto-registration?

* *A:* Regarding auto-registration processing, if an auto-registration request doesn't yield any positive results, the poller won't keep banging on the server every iteration, it waits for at least an hour before trying again as the interval is currently hardcoded. To speed things up for testing, especially to avoid the initial 10-minute wait before the first auto-registration attempt after the poller starts and finds it has no local copy of the host configuration file, you will probably want to set the processing interval to 60 (which is one minute). To change the directive go to _Configuration_ > _Hosts_ > _Host externals_ > _Modify_ > {_gdma-linux}_ > _Poller_Proc_Interval = "60"_. If you do change this value for testing, be sure to change it back (typically to 600) for production use. If auto-registration fails on a given attempt and you don't want to wait the extra hour for the following attempt, just bounce GDMA on the client machine, the [DOCDEV:How to stop and start services?] page describes the various platform-specific commands used to start and stop the GDMA client.

h6. *Q:* What is the role of profiles in Auto Registration?

* *A:* You can rename the host within Monarch (_Configuration_ > _Hosts_ > _hostgroup_ > _host_ > _Detail_ > _Rename_). After doing so, go to _Configuration_ > _Control_ > _Build externals_, to rebuild the externals file using the modified hostname. After some time, the GDMA client will recognize that its externals file is no longer available on the server under the old name, and that will eventually cause it to exercise the auto-registration logic. At that time, the client should be recognized by the auto-registration request as being already in Monarch (given that the IP address has not changed, even though the hostname did), and the new name will be returned to the client for further operations.
** If need be, you can speed up this process by bouncing GDMA on the client after the externals are rebuilt on the server, see the [DOCDEV:How to stop and start services?] page describes the various platform-specific commands used to start and stop the GDMA client. It will take about 10 minutes (one {{Poller_Proc_Interval}}) for the auto-registration to occur on the client.
** Of course, you will need to run a Commit operation (_Configuration_ > _Control_ > _Commit_) for Nagios to understand that the hostname has changed, so it doesn't start dropping the data for this host on the floor.
** Renaming an existing host like this is subject to a caveat, namely that in the current release of GroundWork Monitor, performance data collected under the old hostname will not be transferred to the new hostname. The old data still exists, but it is stored in RRD files using the old hostname, while new performance data will be stored in RRD files using the new hostname. We don't currently have a utility to merge the old data into the new RRD files.