Hi,
I'm currently testing out Icinga 1.3 on a development server using the classic UI and Icinga Web with IDOUTILS, but I'm having
trouble grasping how the backend of things work.
I was under the impression that all the monitoring data is stored in a database, but I just had my MySQL service stop, and I was suprised that, although the Icinga Web stopped working, the classic UI still seemed to be functioning fine.
Is the classic UI still using flat files and the new Web using a database? If so, isn't this going to put more load on the server with I/O?
Also, if this situation happens again (the SQL service dying), when I start it again, will the classic and new web be out of sync with service acknowledgments, comments etc that happend whilst the service had stopped?
I'm currently testing out Icinga 1.3 on a development server using the classic UI and Icinga Web with IDOUTILS, but I'm having
trouble grasping how the backend of things work.
I was under the impression that all the monitoring data is stored in a database, but I just had my MySQL service stop, and I was suprised that, although the Icinga Web stopped working, the classic UI still seemed to be functioning fine.
Is the classic UI still using flat files and the new Web using a database? If so, isn't this going to put more load on the server with I/O?
Also, if this situation happens again (the SQL service dying), when I start it again, will the classic and new web be out of sync with service acknowledgments, comments etc that happend whilst the service had stopped?