... | @@ -37,7 +37,7 @@ Since you're logged in as super-admin, you can see the `Configuration` menu and |
... | @@ -37,7 +37,7 @@ Since you're logged in as super-admin, you can see the `Configuration` menu and |
|
|
|
|
|
Go to `Services`->`Machines` and click `Add New Machine`, type in `agent-bind9`.
|
|
Go to `Services`->`Machines` and click `Add New Machine`, type in `agent-bind9`.
|
|
|
|
|
|
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 that and the agent looked for Kea and BIND and found only BIND. It should detect BIND app running there.
|
|
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.
|
|
|
|
|
|
5. **Inspect the agent-bind9 machine**.
|
|
5. **Inspect the agent-bind9 machine**.
|
|
|
|
|
... | | ... | |