We’ve already written a blog post about how to integrate Alyvix 3 and Alyvix Server into NetEye 4. Some time has passed and a few things have changed, so here are some new HOWTO’s that can make your life easier.
The first thing is that the active service check for asking the status of the last Alyvix test case run has a flaw in it, where it will go into HARD status (sending a notification) before it effectively has been checked again. This is because the Icinga service check does not know exactly when the test case will next be run on the server, and synchronizing this is quite hard.
It’s better to have an active/passive approach for the integration. This means that the Icinga service for a single Alyvix test case will not actively check its status, but that an additional service will be needed to do this, injecting the check result inside the single test case service.
So the additional service can thus decide whether the testcase has already been run again and inject the passive result ONLY if a new status/run is found. This will mitigate the problem I explained above, and a HARD state is now “real” as we know the test case has been run again.
You can download the needed plugin for this approach here.
From the Service Output HTML link you can access the log for a single test case execution which is available from the Alyvix Server host.
For security reasons we don’t want to allow open access to the Alyvix Server webservices, just to the NetEye Server and maybe some selected users.
Now how will we configure this? Well, you can use NetEye’s Apache server ReverseProxy Feature. Create an Apache configuration file like the one below in /etc/http/conf.d/alyvix-proxy.conf on the NetEye Server(s) where you change the alyvixserver01(.example.com) text to the server name of your Alyvix Server Host.
SSLProxyEngine on SSLProxyVerify none SSLProxyCheckPeerCN off SSLProxyCheckPeerName off SSLProxyCheckPeerExpire off ProxyPass /alyvix/alyvixserver01/ https://alyvixserver01.example.com/ ProxyPassReverse /alyvix/alyvixserver01/ https://alyvixserver01.example.com/
Now to use this ProxyPass on your NetEye Apache server in the above plugin, you can use the -P option in this mode, obviously substituting the placeholder with the real data:
/neteye/shared/monitoring/plugins/check_alyvix3_testcases.pl -H <alyvix-server-ip-hostname> -N <alyvix-server-hostname> -P /alyvix/alyvixserver01 -v
So everyone accessing the Alyvix logs will do so over the NetEye Server instead of needing to access Alyvix Server directly over the network.
Enjoy these new modes to use Alyvix along with NetEye in a more secure mode.