Skip to main content

OpenStack monitoring: Zabbix Ceilometer proxy installation

Recently a Ceilometer proxy for Zabbix was released by OneSource. This proxy will pull all the instance information from OpenStack and populate it in Zabbix

The source code can be downloaded from here:

The basic prerequisites for the server where the proxy is running is Python and Pika library. Also there should be network connectivity from the proxy machine to your OpenStack installation.

In the test installation, I tried it on a standalone Ubuntu machine. Python can be installed using apt-get and was pretty much straight forward. The document suggests installation of Pika using PIP package manager. Since the machine is sitting behind a proxy, we had some trouble using PIP. As a workaround, the Pika can be directly downloaded and installed from the source repository here

Simply download all files in the repo and execute the script to install pika

Now coming back to the Ceilometer proxy installation. For this you have to uncomment this line in your keystone.conf file.

 notification_driver = keystone.openstack.common.notifier.rpc_notifier
 Next step is to update the proxy.conf file with your OpenStack installation connection parameters.This is also pretty much straight forward for people familiar with OpenStack. I had some confusion on the rabbitmq account to be used, the 'guest' account worked fine for me. Other than that it is just your ceilometer api IP address and keystone authentication details. In the zabbix_configs section, you need to provide your zabbix host IP and admin credentials for web login

Once the proxy.conf file is updated, you can simply run the script to start the monitoring. A new entry for the proxy will be created Administration->DM .

Note: One shortcoming we have noticed is that the instances created using heat orchestrator are not being picked up by the proxy.  Also the cleanup of machines from Zabbix once they are deleted from openstack is not happening.



Post a Comment

Popular posts from this blog

Windows server 2012: where is my start button??

If you have been using Windows Server OS for a while, the one thing that will strike you most when you login to a Windows server 2012 is that there is no start button!!.. What??..How am I going to manage it?? Microsoft feels that you really dont need a start button, since you can do almost everything from your server  manager or even remotely from your desktop. After all the initial configurations are done, you could also do away with the GUI and go back to server core option.(In server 2012, there is an option to add and remove GUI). So does that mean, you need to learn to live without a start button. Actually no, the start button is very much there .Lets start looking for it. Option 1: There is "charms" bar on the side of your deskop, where you will find a "start" option. You can use the "Windows +C" shortcut to pop out the charms bar Option 2: There is a hidden "start area"in  the bottom left corner of your desktop

Use Diskpart to make drives online

Issue: In disk management, disk is shown as missing or Offline in Windows Resolution: The disks can be made online by using diskpart utility - Open a command prompt->type diskpart -Inorder to list the disks in the system type: list disk -Note down the number of the disk that you want to make online -Select that disk to operate upon, For eg:, if the disk number is 1, type: Select disk 1 -Now that particular disk will be selected as teh active disk. If you type "list disk" command once more, you can see a * symbol on the left side of the selected disk -Inorder to make the selected disk online type : online disk - If the disk is made online, you will get a message that the operation is completed successfully

Kubernetes best practices in Azure: AKS name space isolation and AAD integration

Once you have decided to run your workloads in AKS service in Azure, there are certain best practices to be followed during design and implementation. In this blog we will discuss two of these recommended practices and the practical aspects of their implementation- Azure AD integration and name space isolation While AAD helps to authenticate users to your AKS cluster using the existing users and groups in your Azure AD, name space isolation provides logical isolation of resources used by them. It is useful in multi tenant scenarios where the same cluster is being used by different teams/departments to run their workloads. It is also useful in running say a dev, test and QA environment for organization in the same cluster. Combining AAD integration with name spaces allow users to login to their namespace using their Azure AD credentials AAD integration with AKS : The following Microsoft document will get you started  with AAD integration of AKS cluster.: https://docs.microsof