... | ... | @@ -36,9 +36,9 @@ Since you're logged in as super-admin, you can see the `Configuration` menu and |
|
|
|
|
|
## 4. Add new BIND9 machine to monitor
|
|
|
|
|
|
Go to `Services`->`Machines` and click `Add New Machine`, type in `agent-bind9`.
|
|
|
Go to `Services`->`Machines` and switch to `Unauthorized` machines view (top-right corner). Now click the action button in `agent-bind9` machine and then click `Authorize` in the menu.
|
|
|
|
|
|
Normally you would type in an FQDN or an IP address of the machine you want to monitor. By default Stork is being deployed using Docker. There are several docker containers simulating machines with Kea and BIND in various modes of operation. agent-bind9 is a name of one of such containers. Note that you didn't specify what kind of software is running on the `agent-bind9` machine. Stork server connected to the stork agent running there and the agent looked for Kea and BIND and found only BIND. It should detect BIND app running there.
|
|
|
In the demo, there are several docker containers simulating machines with Kea and BIND in various modes of operation. agent-bind9 is the name of one of such containers. Note that you didn't specify what kind of software is running on the `agent-bind9` machine. Stork server connected to the stork agent running there and the agent looked for Kea and BIND 9 and found only BIND 9. It should detect BIND 9 app running there.
|
|
|
|
|
|
## 5. Inspect the agent-bind9 machine
|
|
|
|
... | ... | |