Managing Instances In Nagios Log Server can be confusing if we don’t know how to view, manage and troubleshoot them.
A clustered application, it consists of one or more instances of Nagios Log Server.
As part of our Server Management Services, we assist our customers with several Nagios queries.
Today, let us see how to view statistics and manage Nagios Log Server Instances.
Managing Instances In Nagios Log Server
An instance participates in the cluster and acts as a location for the log data to reside. The log data with the use of the Elasticsearch database spreads across the instances.
To manage Nagios Log Server Instances, we navigate to Admin > System > Instance Status.
This provides an overall summary of the instances in the cluster. We use this information to get an overview of the performance of the cluster.
We use this table to get a summary of each instance in the cluster. It gives us an overview of how each instance performs.
In the IP column, we click the IP address to bring up more information about that specific instance.
This table will describe the statistics associated with this Nagios Log Server instance.
We use this information to know what the instance is capable of and the hardware they might need to introduce in a new instance.
We can find the Instance ID in the top right corner of the page. It is useful while we execute commands or when we review log files.
This table contains information about the underlying operating system parameters/capabilities.
- IP address and Hostname
- Load over time
- Memory and Swap statistics
- CPU Statistics
- CPU Physical properties
Here, we can see the statistics of the current process for this instance.
- Open File Descriptors
- CPU statistics
- Memory status
The file system used by the instance is found here.
- File Data Path
- Mount and Device Paths
- Total and Free Space
- Disk Writes, Reads and Size
This table provides information about the indices this instance handles.
- Number of Documents and any that have been deleted
- Store Size
- Totals of Indices, Deletions, Gets, Queries and Fetches
Java Virtual Machine (JVM)
This table has statistics about the JVM that runs Elasticsearch.
- Heap and Non-Heap usage
- Uptime, Thread status
- GC Times and Counts
- Java version and JVM information
A group of idle threads that stand ready until there is work.
- Formatted by Queue/Peak/Active
- Each thread title indicates a section of the pool and the current threads we use
- Queued pools are waiting to be run
- Peak is the most threads the specific type of thread has ran at once
- Active is any threads that are currently running
We can control the Elasticsearch and Logstash services on each Nagios Log Server instance via, Admin > System > System Status.
Under Subsystems, we use the Instance drop-down list to change the instance we want to control.
Then we use the Restart/Stop/Start commands to perform that action on the instance.
For more detailed information about instances, we need to execute commands in a terminal session using a curl command.
To do so, we establish a terminal session to one of the Nagios Log Server instances and run:
curl -XGET ‘http://localhost:9200/_cat/nodes/?v’
This will produce an output similar to the following:
[[email protected] ~]# curl -XGET ‘http://localhost:9200/_cat/nodes/?v’ host ip heap.percent ram.percent load node.role master name nls-c6x-x86.box293.local 10.25.5.85 50 70 0.08 d * 76e504ad-a6c9-4798 localhost 127.0.0.1 8 66 0.00 d m d20fa1fa-3a37-4a63 nls-r6x-x64.box293.local 10.25.5.98 24 86 0.00 d m edde1960-0cc2-4892
[Need help to manage Instances? We’d be happy to assist]
In short, today our Support Techs gave an idea about Instances and how we can manage them.