Cluster Hosts Tab

The Cluster Hosts tab allow you to apply actions to one or more Host in the Cluster as well to check individual host metrics and health.

We will explain various features IDSTower offer by explaining each section in the image below

../_images/cluster_hosts_tab.png

1. The Hosts Action Button allows you to run certain actions on one or more selected host as well on all hosts in the cluster as seen in the image below:

../_images/cluster_hosts_actions.png

Some of the actions that IDSTower offers are:

  • Add New Hosts: use this action to add new Host(s) to the cluster, IDSTower will do all of the necessary packages installation and configuration to make sure the newly added hosts have the same configurations as other hosts in the cluster. For clusters of type “Fresh Installation”, IDSTower first checks whether Suricata is already installed on each new host. If it finds one, it stops without changing anything on that host and tells you which host is affected, so you don’t accidentally replace a working Suricata installation. If you did intend to replace it, tick the “Take over the existing Suricata installation” option that appears in the Add New Hosts dialog and try again.

  • Change Config Group: use this action to re-assign host to different config Groups.

  • Refresh stale config: use this action to apply the configuration changes that have not reached the host(s) yet, and to restore a configuration that got lost on a host. Most changes you make in IDSTower — renaming, adding or deleting instances, editing a config group, changing a configuration profile — are saved first and reach a host only when its configuration is applied; until then the host is marked with a warning icon, and the cluster page shows a Config Update Required banner with an Update Config button that does the same for every such host. Applying the configuration returns each Suricata instance to its recorded state — instances recorded as running are restarted on the new configuration, instances recorded as stopped are stopped — and restarts Filebeat; on an onboarded cluster without the Service Control capability it leaves the services as they are. On a Fresh cluster a newly added instance is recorded as stopped and stays stopped after the configuration is applied; start it from its row. On an onboarded cluster a newly added instance is recorded as running, so the apply starts it. If a service cannot be started or stopped afterwards, the configuration still counts as applied and the dialog shows a warning naming the host and the reason.

  • Start/Stop/Restart a service: use this action to start/stop the services in each host. It is not available on a host whose configuration changes are not applied yet: its services do not match the ones IDSTower would act on until they are (a renamed instance has no service under its new name, a deleted one is still running). An action on several hosts skips those hosts and names them, in the confirmation dialog before it runs and in its result afterwards. Apply their changes with Refresh stale config first to include them. For the same reason, a Suricata or Filebeat version upgrade is refused while any host it covers has changes that are not applied yet.

  • remove From Cluster: use this action to remove a host from the cluster, please note that this will delete services/configuration that has been installed by IDSTower.


2. The Cluster Hosts Lists, along with their Config Groups, FQDNs, Monitored interfaces and key metrics.