Estimate your Nagios Log Server needs by inputting data collection and storage details.
GB
GB
Days
Optional
Days
*This is a baseline estimation for licensing and should be used only as a guide. We encourage you to speak with a Nagios representative for an accurate assessment.
Nagios, the Nagios logo, and Nagios graphics are the servicemarks, trademarks, or registered trademarks owned by Nagios Enterprises. All other servicemarks and trademarks are the property of their respective owner. Website Copyright © 2009-2023 Nagios Enterprises, LLC. All rights reserved.
Nagios Log Server (NLS) employs a system that partitions logs into ‘shards,’ replicates them, and distributes them across available NLS instances in the cluster. This process not only reduces the load on any single system but also ensures data redundancy.
The total data stored is categorized into ‘indices’ which live on the NLS cluster for querying and dashboarding, and ‘Index Snapshots,’ which consist of archived data. These snapshots are stored separately from the Log Server instances to reduce individual instance disk size and memory requirements but can be easily reloaded onto the instances for querying when needed.
Furthermore, it’s important to note that this calculator does not recommend a single instance license. Single instance NLS clusters lack the redundancy of multi-instance clusters. If your ‘Instances Needed’ value is less than 1, or if you have questions about your environment and the suggested instance count, please consult a Nagios representative.
See our documentation on Installation Requirements on Nagios Log Server to learn more.
Daily Log Collection refers to the average volume of data anticipated to be added to the system each day. The process of breaking down logs and adding fields for querying increases the actual data volume by 10-15% beyond the initial intake.
The calculator automatically adjusts for this increase in log size, so there’s no need to manually calculate these adjustments.
This refers to the system’s available storage capacity for data. The minimum recommended storage is 40 GB, though most customers prefer significantly more than this minimum.
Adjusting the available storage is an effective method for managing the required number of instances in a cluster. Increasing storage capacity can decrease the number of needed instances, while reducing storage capacity may necessitate more instances.
Also referred to as the “Hot Retention” period.
This represents the number of days that an index will remain open and accessible for queries by Log Server. Data within these indices is stored on the Log Server cluster and will utilize the available drive space on each instance.
Also referred to as “Cold Storage” or “Data Recall Provision”.
Index Snapshots provide a method for storing and accessing log data without requiring extensive fast storage. This data is stored separately from the ‘Index Retention’ data but can be reloaded onto the system as needed.
Here’s an insight into how this calculator generates its numbers. You’ll notice that some values are set higher than strictly necessary to accommodate potential growth or to counteract any underestimation of input values. It is important to retain extra space on systems in case data intake increases or if there’s a need to retrieve data from storage.
