Need help?

Our experts have had an average response time of 11.7 minutes in August 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

Managing Instances In Nagios Log Server – Let’s discuss

by | May 5, 2021

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.

  • Global Stats

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.

  • Instances

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.

  • Instance Stats

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.

  • Instance ID

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.

  • Instance Information

This table contains information about the underlying operating system parameters/capabilities.

  1. IP address and Hostname
  2. Load over time
  3. Memory and Swap statistics
  4. CPU Statistics
  5. CPU Physical properties
  • Process

Here, we can see the statistics of the current process for this instance.

  1. Open File Descriptors
  2. CPU statistics
  3. Memory status
  • File System

The file system used by the instance is found here.

  1. File Data Path
  2. Mount and Device Paths
  3. Total and Free Space
  4. Disk Writes, Reads and Size
  • Indices

This table provides information about the indices this instance handles.

For example,

  1. Number of Documents and any that have been deleted
  2. Store Size
  3. Totals of Indices, Deletions, Gets, Queries and Fetches
  • Java Virtual Machine (JVM)

This table has statistics about the JVM that runs Elasticsearch.

  1. Heap and Non-Heap usage
  2. Uptime, Thread status
  3. GC Times and Counts
  4. Java version and JVM information
  • Thread Pools

A group of idle threads that stand ready until there is work.

  1. Formatted by Queue/Peak/Active
  2. Each thread title indicates a section of the pool and the current threads we use
  3. Queued pools are waiting to be run
  4. Peak is the most threads the specific type of thread has ran at once
  5. Active is any threads that are currently running
  • System Status

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.

  • Advanced Management

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 50 70 0.08 d * 76e504ad-a6c9-4798
localhost 8 66 0.00 d m d20fa1fa-3a37-4a63
nls-r6x-x64.box293.local 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.


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie


These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.