When running a cluster of Mitel PABX’s it is likely that you will have them interconnecting in one way or another. If you send calls over your WAN connection then these graphs are for you.
There are two graphs added:
Bandwidth – Shows the current set bandwidth limit and usage figures for a Zone Access Point
Calls – Shows the number of calls both accepted or rejected by Bandwidth Management
Linode provides a convenient XML data feed that provides information about your CPU usage and Network Usage. The graph for the CPU Usage seems a little useless, but I have included it here as the XML feed provides the data.
You will need your linode account number to use the graphs, you can find this number by looking at the graphs provided to you in your Linode account management interface. The title of the graph will be “http://www.linode.com/ – yourhostname (linode12345) – CPU – …….”. You will need the text from inside the ( ) for your username ie linode12345.
I thought I would write a quick post on this error, it is very simple to fix. If you receive the following error when importing a Cacti Template:
Error: XML: Hash version does not exist
This simply means the template was generated on a version of Cacti newer than the one you are importing to. Don’t despair, there are simple upgrade instructions on the cacti website.
Just make sure you make a full backup of your database and Cacti webfiles before attempting the upgrade (As a cautionary tale, if you installed cacti from a package you should first check to see if an updated package is available. Package installs can sometimes put the different files required in different places)
I firstly want to acknowledge the work of Mark Round and Linux iostat monitoring with Cacti. The following work was inspired and based on the ideas found in Mark’s post.
My main objective when I started looking into disk monitoring was to get some similar stats into Cacti for Linux that can be found with the Windows PerfMon utility. I found Mark’s post and didn’t quite like the way it used cron to collect its statistics, and wanted something that I could easily add to snmpd.conf without needing to change much more. I was also keen on obtaining the mount point data for each partition as looking at “cciss/c0d0p3” doesn’t mean as much to management (and sometimes to me) and hopefully “/home” does.
When I realised that the free version of VMWare ESXi only kept an hours worth of logging information I went looking for a solution to keep more statistical data. This is what I have come up with so far.
