This line was removed.
This word was removed. This word was added.
This line was added.
Changes (6)View Page History
|Similarly, you need to name trigger files to end with "_trigger", so we will use "winpattern_trigger". |
|h5. Install the instructions and trigger files for your first host |
Autosetup needs to have the instructions and trigger files in a specific location, and manage them itself. You always install the instructions first, then the trigger. This is so the trigger can be used and then ignored until re-installed (thus triggering another discovery). Here's how you do it, with the autosetup command:
|Use the hostname for the windows host where you have GDMA installed, set to use autosetup, and not running. |
|h5. Start the GDMA |
|Now, whenever you are ready, start the GDMA and the host will show up in Monarch with the following services: |
gdma_wmi_disk_Q (remember, we had drive letters C: and Q:, so yours may vary)
|gdma_wmi_disk_ _(This will expand on commit to have instances for C: and Q: in our case. Your system may be different.)_ |
|Run a Control->Commit operation to instantiate the services. |
|You will have also imported performance definitions with the profile, so all these services should have graphs associated in Status Viewer and Grafana. |
How does it work? Well, the detected drive letter is found by the autosetup discovery program on the Windows host, and passed as a macro to the service definition in Monarch. Then, it's used as an _instance_ name for a service _instance_ on the gdma_wmi_disk\_ service. That's why we left the trailing underscore, but more importantly, that trailing underscore is something we like to use to signal that the service is intended to be used with autosetup and instances. You certainly *could* not do it and carry along the underscore in the instructions, like this: