operations

Prometheus labels every data point — the most well-known example of a label is (probably) instance. Take a look at this query result (query: up{job="prometheus"}): up{instance="127.0.0.1:9090",job="prometheus"} 1 So what does this tell me? I queried for the “up” metric and filtered it for “prometheus” — yay. The “1” says, my service is alive. So far so gut. Readability Since we are in the process of running a few Prometheus servers (in federation), each of those metrics will report back with instance="127....

In my last blog entry, I demo’d how to get started with Vagrant and the ShellProvisioner. To further illustrate how amazingly simple it is to get started on some Ruby, I’ll convert the shell script from my last blog post to a little recipe for chef. Same objective, we install a PEAR package — but it could be anything really. Follow me. Shell This is the shell script from before:...

In 2010, operations became an even more central part of my life. As I write this blog post (in early January, 2011), we have been running on Amazon AWS — and EC2 in particular — for over a year. Previously we had used a service called RightScale but in Q3 of 2010, we moved on/away from RightScale and started using chef and a service called Scalarium. Because Opscode’s chef became such a big part of my work life, I gave a talk about chef, and chef-solo in particular, at last December’s PHP Usergroup meeting in Berlin....

A couple months ago, I wrote an article titled Operation CouchDB. I noticed that a lot of people still visit my blog for this particular post, so this is an update to the situation. And no, you may not copy and paste this or any other of my blog posts unless you ask me. ;-) Caching revisited A while back I wrote about how caching is trivial with CouchDB — well sort of....