Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.7

Nagios XI

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	Nagios XI is an information technology (IT) infrastructure monitoring and alerting solution for servers, network devices, applications, and services. This technology can monitor various operating system resources, network services, network devices (routers, switches), generic devices (printers, workstations), and provides alerts for problems and resolutions. Nagios XI is related to Nagios Core. Nagios XI is the full-featured, vendor-supported version and Nagios Core is the open source version. This assessment only covers Nagios XI. Nagios XI is available in two editions: Standard and Enterprise. This assessment covers both editions.
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v23.12
Decision Date:	12/28/2023 at 20:12:17 UTC
Aliases:	infrastructure monitoring; network monitor; application monitor; operating system monitor; system monitor; service monitor
Introduced By:
Vendor Name:	Nagios Enterprises

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
2011	02/28/2011
2012	09/04/2012
2014R1.1	05/01/2014
2014R2.7	04/23/2015
5R1.0	09/28/2015
5.2.x	10/08/2015
5.3.x	10/03/2016
5.4.x	12/28/2016
5.5.x	06/28/2018
5.6.x	04/18/2019
5.7.x	06/08/2020
5.8.x	01/13/2021
2024R1	12/06/2023

Current Decision Matrix (12/27/2023)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved w/Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unapproved: This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Divest: VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint:The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology approved with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology approved with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

<Past

CY2024

CY2025

CY2026

Future>

Release

2011

Unapproved

2012

Unapproved

2014R1.1

Unapproved

2014R2.7

Unapproved

5R1.0

Unapproved

5.2.x

Unapproved

5.3.x

Unapproved

5.4.x

Unapproved

5.5.x

Unapproved

5.6.x

Unapproved

5.7.x

Unapproved

5.8.x

Divest
[19, 20, 22, 23, 25, 26, 27]

Unapproved

2024R1

Approved w/Constraints
[19, 20, 22, 23, 25, 26, 27]

Decision Constraints


[1]	Product must remain patched and its configuration hardened with approved VA guidelines in order to mitigate known and future vulnerabilities. Extensive testing also highly recommended before deployment to end users. See reference tab for additional product specific security best practices.

[2]	As of April 23, 2015, per the Deputy CIO of Architecture, Strategy and Design (ASD), all technologies in use by the VA require an assessment by the VA Section 508 office. Section 508 of the Rehabilitation Act Amendments of 1998 is a federal law that sets the guidelines for technology accessibility. A VA Section 508 assessment of this technology has not been completed at the time of publication. Therefore, as of April 23, 2015 only users of this technology who have deployed the technology to the production environment, or have project design and implementation plans approved, may continue to operate this technology. In the case of a project that has implemented, or been approved for a specific site or number of users, and that project needs to expand operations to other sites or to an increased user base, it may do so as long as the project stays on the existing version of the technology that was approved or implemented as of April 22, 2015. Use of this technology in all other cases is prohibited.

[3]	Users must ensure they are using Nagios XI 2012R2.4 or later to mitigate security vulnerabilities. This technology depends on MySQL which may only be used for Intranet applications and my not be used with PII/PHI/VA Sensitive information as of this writing. See the MySQL TRM entry for more information.

[4]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[5]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[6]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities.

[7]	Users must ensure they are using Nagios XI 2014R1.1 or later to mitigate security vulnerabilities. This technology depends on MySQL which may only be used for Intranet applications and cannot be used with PII/PHI/VA Sensitive information as of this writing. See the MySQL TRM entry for more information.

[8]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[9]	Users must ensure they are using Nagios XI 2014R1.1 or later to mitigate security vulnerabilities. This product can be configured with a MySQL Database which currently has TRM constraints for intranet use only due to its many known security issues. If MySQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High Risk system. See the MySQL Database TRM entry for more details. Use of this product to store Protected Heath Information (PHI), Personally Identifiable Information (PII) or VA-sensitive information is unapproved until VA develops and approves a security configuration baseline to meet VA`s security requirements for PHI/PII/VA-sensitive information. See the VA baseline website site referenced above for more information. Any use of this product for PHI/PII/VA-sensitive information must be waivered for use through the waiver process. At the time of this writing, NIST and NSOC had not made a distinction if any known vulnerabilities have been remediated in the enterprise edition. This will need to be considered if VA were to develop a security configuration baseline for either edition. Users must not utilize MariaDB with this product. All systems must be patched/hardened with approved VA guidelines along with extensive testing in a closed network environment before it can be connected to the VA network due to the vulnerabilities and known issues. In addition, server links must be monitored to ensure confidentiality, integrity, availability.

[10]	Technology must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities.

[11]	Users must ensure they are using Nagios XI 2014R1.1 or later to mitigate security vulnerabilities. This product can be configured with a MySQL Database which currently has TRM constraints for intranet use only due to its many known security issues. If MySQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High Risk system. See the MySQL Database TRM entry for more details. Use of this product to store Protected Heath Information (PHI), Personally Identifiable Information (PII) or VA-sensitive information is unapproved until VA develops and approves a security configuration baseline to meet VA`s security requirements for PHI/PII/VA-sensitive information. See the VA baseline website site referenced above for more information. Any use of this product for PHI/PII/VA-sensitive information must be waivered for use through the waiver process. At the time of this writing, NIST and NSOC had not made a distinction if any known vulnerabilities have been remediated in the enterprise edition. This will need to be considered if VA were to develop a security configuration baseline for either edition. Users must not utilize MariaDB with this product. All systems must be patched/hardened with approved VA guidelines along with extensive testing in a closed network environment before it can be connected to the VA network due to the vulnerabilities and known issues. In addition, server links must be monitored to ensure confidentiality, integrity, availability.

[12]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure they are using Nagios XI 2014R1.1 or later to mitigate security vulnerabilities. This product can be configured with a MySQL Database, which at the time of writing has TRM constraints for intranet use only due to its many known security issues. If MySQL is selected for use with this product, these factors should be considered especially when an instance of this product will be considered a Moderate or High Risk system. Please refer to MySQL Database TRM entry for more details. Use of this product to store Protected Heath Information (PHI), Personally Identifiable Information (PII) or VA-sensitive information is unapproved until VA develops and approves a security configuration baseline to meet VA`s security requirements for PHI/PII/VA-sensitive information. See the VA baseline website site referenced above for more information. Any use of this product for PHI/PII/VA-sensitive information must be waivered for use through the waiver process. At the time of this writing, NIST and NSOC had not made a distinction if any known vulnerabilities have been remediated in the enterprise edition. This will need to be considered if VA were to develop a security configuration baseline for either edition. Users must not utilize MariaDB with this product. All systems must be patched/hardened with approved VA guidelines along with extensive testing in a closed network environment before it can be connected to the VA network due to the vulnerabilities and known issues. In addition, server links must be monitored to ensure confidentiality, integrity, availability.

[13]	Users should check with their supervisor, Information Security Office (ISO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations.

[14]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[15]	Users must ensure that PostgreSQL is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure they are using Nagios XI 2014R1.1 or later to mitigate security vulnerabilities. This product can be configured with a MySQL Database, which at the time of writing has TRM constraints for intranet use only due to its many known security issues. If MySQL is selected for use with this product, these factors should be considered especially when an instance of this product will be considered a Moderate or High Risk system. Please refer to MySQL Database TRM entry for more details. Use of this product to store Protected Heath Information (PHI), Personally Identifiable Information (PII) or VA-sensitive information is unapproved until VA develops and approves a security configuration baseline to meet VA`s security requirements for PHI/PII/VA-sensitive information. See the VA baseline website site referenced above for more information. Any use of this product for PHI/PII/VA-sensitive information must be waivered for use through the waiver process. At the time of this writing, NIST and NSOC had not made a distinction if any known vulnerabilities have been remediated in the enterprise edition. This will need to be considered if VA were to develop a security configuration baseline for either edition. Users must not utilize MariaDB with this product. All systems must be patched/hardened with approved VA guidelines along with extensive testing in a closed network environment before it can be connected to the VA network due to the vulnerabilities and known issues. In addition, server links must be monitored to ensure confidentiality, integrity, availability.

[16]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[17]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[18]	Users must ensure that PostgreSQL is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure they are using Nagios XI 2014R1.1 or later to mitigate security vulnerabilities. Use of this product to store Protected Heath Information (PHI), Personally Identifiable Information (PII) or VA-sensitive information is unapproved until VA develops and approves a security configuration baseline to meet VA`s security requirements for PHI/PII/VA-sensitive information. See the VA baseline website site referenced above for more information. Any use of this product for PHI/PII/VA-sensitive information must be waivered for use through the waiver process. At the time of this writing, NIST and NSOC had not made a distinction if any known vulnerabilities have been remediated in the enterprise edition. This will need to be considered if VA were to develop a security configuration baseline for either edition. All systems must be patched/hardened with approved VA guidelines along with extensive testing in a closed network environment before it can be connected to the VA network due to the vulnerabilities and known issues. In addition, server links must be monitored to ensure confidentiality, integrity, availability.

[19]	This product can be configured with a PostgreSQL Database, which currently has TRM constraints limiting its use to Red Hat Enterprise Linux (RHEL) only due to its many known security issues on other platforms. If PostgreSQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system. See PostgreSQL Database TRM entry for more details.

[20]	If this product uses a MySQL database, the product must be configured with a commercial edition of the MySQL Database, which currently has TRM constraints limiting its use for intranet and non-sensitive data only due to its many known security issues. If a commercial edition of MySQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system. See MySQL Database – Commercial Edition TRM entry for more details.

[21]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500.

[22]	Users should check with their supervisor, Information System Security Officer (ISSO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations.

[23]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities.

[24]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[25]	Users must ensure that PostgreSQL and My Structured Query Language (MySQL) Database - Commercial Editions are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Users must ensure they are using Nagios XI 2014R1.1 or later to mitigate security vulnerabilities. Use of this product to store Protected Heath Information (PHI), Personally Identifiable Information (PII) or VA-sensitive information is unapproved until VA develops and approves a security configuration baseline to meet VA`s security requirements for PHI/PII/VA-sensitive information. See the VA baseline website site referenced above for more information. Any use of this product for PHI/PII/VA-sensitive information must be waivered for use through the waiver process. At the time of this writing, NIST and NSOC had not made a distinction if any known vulnerabilities have been remediated in the enterprise edition. This will need to be considered if VA were to develop a security configuration baseline for either edition. All systems must be patched/hardened with approved VA guidelines along with extensive testing in a closed network environment before it can be connected to the VA network due to the vulnerabilities and known issues. In addition, server links must be monitored to ensure confidentiality, integrity, availability.

[26]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500.

[27]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 or its successor to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 or 140-3 compliant full disk encryption (FOE) must be implemented on the storage device where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). By September 22, 2026, all FIPS 140-2 certificate validations will be placed on the Historical List, please refer to FIPS Transition Effort for further guidance and timeline of changes.

Note:

Note: The vendor changed the versioning format in 2023. At the time of writing, the most current version is 2024R1, released 12/06/2023.

The following reference(s) are associated with this entry:
Type	Name	Description
Best Practice	Nagios Configuration Hardening	This website links to the recommended configuration settings in order to operate Nagios XI in a secure manner.
Vendor Provided*	Nagios XI Documentation	This links to a Nagios XI documentation website.
Vendor Provided*	Nagios XI User Guide	This guide is designed to provide users with basic features and functions of this software.
Vendor Provided*	Nagios XI Changelog	This website links to the release history of Nagios XI.
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
Alertstream Visualization Component (Optional)	The alertstream component for Nagios XI allows users to quickly and easily spot problematic hosts and services over time in a `streamgraph` format.
Auto-Discovery Component (Optional)	This component adds auto-discovery capabilities to Nagios XI 2011R1 or later.
Auto-Discovery Wizard	This Nagios XI configuration wizard allows users to easily choose which hosts and services from an auto-discovery job should be monitored.
Auto-Discovery Wizard (Optional)	This Nagios XI configuration wizard allows users to easily choose which hosts and services from an auto-discovery job should be monitored.
Bulk Host Import Wizard (Optional)	This wizard allows user to easily import new hosts and services into Nagios XI using a comma separated values (CSV) dump. Imported hosts are imported and have services replicated to match an already existing host the user selects. This import tool is useful for large environments that want to quickly setup several hosts to be monitored in the same manner.
Dashboard Deployment Component (Optional)	This Nagios XI component allows admins to deploy one or more of their own dashboards to other users. This can be useful when users design a dashboard that other users may want access to. Includes the ability to keep user`s dashboards synchronized with the source dashboard.
Graph Explorer Component (Optional)	The Graph Explorer component utilizes javascript libraries to create interactive graphing tools for Nagios XI, including zoomable performance graphs, time-stacked performance graphs to compare data for periods of time, custom time and selections. This is a Nagios XI Customer-only download.
Hypermap Component (Optional)	This Nagios XI component provides a newly designed hypermap for Nagios XI makes it easier to get a quick overview of the status of users network. The hypermap support dynamic updates via ajax, scrolling and zooming.
Latest Alerts Component (Optional)	This Nagios XI component allows users to quickly see the latest host and services alerts in their monitored environment. The alert dashboard shows which problems are handled or unhandled and which services are impacted by problems. It also allows users to quickly investigate and react to problems that are discovered.
Network Replay Component	This component adds a network replay report to Nagios XI. The replay reports allows users to quickly visualize the changing state of the network over time. The report allows users to specify custom start and end times and supports dynamic updates via ajax, scrolling, and zooming.
Simple Network Management Protocol (SNMP) Walk Wizard (Optional)	This configuration wizard allows users to easily scan an Simple Network Management Protocol (SNMP)-enabled device for object identifiers (OIDs) to monitor. Users can select specific object identifiers (OIDs) from the scan results and configure monitoring based on counter values, string matches, and more.


Systems Management Systems Management Tools	Monitoring

- The information contained on this page is accurate as of the Decision Date (12/28/2023 at 20:12:17 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (12/27/2023)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (12/27/2023)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES