Local Graphite installation on CentOS 5.5 howto

Feature request Our client called:- “I want something to monitor my application!”- “Ok, let’s use JMX, we have plenty of stats exposed there already.”- “Fine, but I want something fancy!”- “Ok, let’s install Graphite, take a look at screenshots!”- “Exc…

Feature request

Our client called:
– “I want something to monitor my application!”
– “Ok, let’s use JMX, we have plenty of stats exposed there already.”
– “Fine, but I want something fancy!”
– “Ok, let’s install Graphite, take a look at screenshots!”
– “Excellent! Use our testing CentOS machine for this.”
– “Ok, erm… wait, nooooo! We have no root access there, there is no internet access and we can’t install anything!!!”
– “(hangup click)”

Setup

There I was, standing alone, looking for help…

My scenario: * no internet access * only user account, no root account * gcc and make installed * some libraries missing * no development packages for installed libraries

    My goals:

  • install libraries to $HOME
  • install Graphite and stuff to $HOME/graphite

Solution

It took me a few days, but I’ve managed to install Graphite locally. Here is a gist for a sake of documentation and for others that may need it.

<a href="https://gist.github.com/SpOOnman/5957589">https://gist.github.com/SpOOnman/5957589</a>
You May Also Like

Context menu or Action buttons ?

Recently I was drawn into one of those UI "religious" disputes that has no easy answers and usually both sides are right. One of our web developers was trying out new web tech (with pretty rich widget library) and started to question himself about some basic usability decisions. The low level problem in this case is usually brought to "which widget should I use ?". I'm not fond of bringing the usability problems to questions: Should I use Tabs over Menu ? Or should I use Context menu instead of buttons panel ? But sometimes if time is crucial factor and other usability levels are by default not addressed at all - better developer that asks those basic questions than developer that do not question himself at all.