Call Us! 1-800-383-5193
Call Us! 1-800-383-5193
Call Us! 1-800-383-5193

Need Help?

Emergency Response Time custom

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

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

Manage Indices in Nagios Log Server – How we do

by | Apr 19, 2021

Wondering how to Manage Indices in Nagios Log Server? We can help you.

An index in Nagios Log Server is how the Elasticsearch database stores log data. The log data is spread across the instances using the Elasticsearch database.

Here at Bobcares, we handle Nagios Log servers of our customers as a part of Server Management Services. Today let’s see how to manage indices in Nagios Log Server.

How to manage indices in Nagios log server

Before going into the details for managing indices, we will have a glimpse of what Indices is.

Index/Indices in Nagios

Nagios Log Server creates an index for every day of the year. As a result, it becomes easy to age out old data when no longer required.

Each index contains 5 Shards. A shard is a portion of the log data in that index. Elasticsearch spreads the data out for redundancy and replication with Shards and Replicas.

Generally, when an index contains 5 shards and 1 replica. If one of Nagios Log Server instances has a disk failure we can recover it with the help of the copy of shards. This will be available in another instance.

Steps to manage indices in Nagios log server

Index Status

For managing Nagios Log Server Indices we can go to Admin and take System then Index Status.

Also, the index status page allows administrators to see the current statistics and behavior of their Nagios Log Server indices.

Index Statistics

We can check the statistics, it allows us to see the following aspects:

1. The number of indices in our instance

2. Total documents over all our indices

3. The total shards in the index

4. Number of shards that were successful, and the primary and total size of the index.

Seeing the statistics of our index can be useful if we plan to add, remove or temporarily remove an instance.

Furthermore, it gives us a good idea of the number of files, shards, and disk space an index is using.


The Indices table shows the indices that have been created.

Each index has the following information about it:

1. Index

The first column is the index name.

2. # Docs

It shows how many documents each index currently contains.

3. Primary Size

The actual size of the index is the primary size.

4. # Shards

The number of primary shards that have been allocated to the index.

5 # Replicas

The number of replicas assigned to the index.

6. Action

This column allows to perform the following actions to an index:

a) Closing an index

It means that the log data will no longer be searched in queries. However, it will not replicate across instances.

b) Opening an index

It will allow the log data to be searched in queries.

c) Delete the index entirely

We can click an index to see the following details:

1. The number of documents the index is made up of, shards, indices, and the total size of the index
2. Search Totals
3. Get Totals
4. Documents
5. Indexing Totals
6. Operations

Advanced Management

If we need more details regarding the indices, we can execute few commands in the terminal.

We can check the index shard status using the following command:

curl -XGET 'http://localhost:9200/_cat/shards/?v'

To check the status of a specific index we specify the name of the index as given in the following command:

curl -XGET 'http://localhost:9200/_cat/shards/logstash-2017.10.31?v'

When one of the Nagios Log Server instances is offline, it will be seen as UNASSIGNED.

[Need assistance? We can help you]


In short, we saw how our Support Techs manage indices in Nagios log server.


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.