Nagios doing the front desk
I analyzed the pros and cons of Nagios and Nagiosql, based on previous experience and exploration. decided to use Nagios as the monitoring data display layer, temporarily called the "foreground". The nagiosql is the configuration layer of the monitor body, which is called "backstage" temporarily. In short, the backend is a server-side configuration and the foreground is used to view the results.
This takes you to the left-hand menu bar on the Nagios page to merge it with the left-hand menu bar of Nagiosql, where you can now trade off your business needs.
The left menu bar on the Nagios page is shown in Figure 1.3
Friends who need real-time knowledge of Nagios can access the demo:http://nagioscore.demos.nagios.com/of Nagios official website
Nagiosql doing backstage
By investigating Nagios and Nagiosql, my advice was to merge Nagios's related pages into Nagiosql's main framework. Both are developed with PHP, but I am the PHP 0 basis, then learn while selling. For Nagios source code analysis, from index.php (this page first page) The source code is as follows,
[PHP]View Plaincopyprint?
- < Frameset cols= style= >
- <frame src= name= frameborder= style= >
- <frame src= name=" main " frameborder=" 0 " style= >
lines 45th and 46 understand that the left and right pages are displayed through an IFRAME.
Thus the side.php source code is analyzed, the source code is as follows:
[PHP]View Plaincopyprint?
- <?php
- include_once (DirName (__file__). '/includes/utils.inc.php ');
- $link _target="main";
- ?>
- <! DOCTYPE HTML public "-//W3C//DTD HTML 4.0 transitional//en">
- <meta name="ROBOTS" content="NOINDEX, NOFOLLOW">
- <meta http-equiv=' content-type ' content=' text/html;charset=utf-8 '>
- <TITLE>Nagios</TITLE>
- <link href="stylesheets/common.css" type="Text/css " rel="stylesheet" >
- <body Class=' NavBar '>
- <!--<div class="Navbarlogo">-->
- <!--<a href="http://www.nagios.org" target="_blank"><img src="Images/sblogo.png " border=" 0 " alt="Nagios"></a>-->
- <!--</div>-->
- <!--<div class="Navsection">-->
- <!--<div class="Navsectiontitle"> Common </div>-->
- <!--<div class="Navsectionlinks">-->
- <!--<ul class="Navsectionlinks">-->
- <!--<li><a href="main.php" target= "<?php echo $link _target;? >> Home </a></li>-->
4th, 31 line, clear the Click menu, the right areaTarget Controlthe information displayed.
And the nagiosql of the source of the analysis, is completely confused. Because Nagiosql introduced templates (later article analysis). This becomes the main reason to merge Nagios into Nagiosql.
Because of the CGI problem (later in the article), we tried to split the nagiosql into the Nagios page, but tried unsuccessfully because we did not understand the it.php template (later article analysis).
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 (ii)---Nagios and nagiosql merger and trade-offs