Nagios Two-time development (v)---the relationship between Nagios and Nagiosql

based on the understanding of Nagios and Nagiosql, the author briefly combs the relationship between the two, as shown in the following:

 

 

 

  As you can see from the diagram above, Nagios and Nagiosql share hosts, host groups, services, service groups, and so on. CFG configuration files, while in Nagiosql, you can freely control the start and stop of nagios processes. Due to the need to specify the Nagios configuration and the path of the application during the Nagiosql installation configuration, and the need to mask its original default configuration directory in Nagios and modify it to the new path in Nagiosql, this provides a strong condition for tacit understanding.  

From this point of view, the two share only the configuration file, and there is no database dependency. Maybe that's why nagiosql can't have an impact on Nagios's architecture, after all, they're relatively independent projects.

As to whether or not the Nagios architecture needs to be changed during the two development process, so that its support for configuration files is changed to a dependency on the database, this needs our assessment. However, from yesterday's blog, the author found that if Nagios will fully read and write data to the database, it will bring serious performance impact. This requires the actual test to be turned over.  

 

Please mention the source when the friends reprint, because I am in order to better facilitate everyone to discuss with me. Thank you, sir.

comments and suggestions: [email protected]

 

Nagios two development (v)---the relationship between Nagios and Nagiosql