|DEBUG||poop contains corn|
|TRACE||poop currently moving into colon|
|WARN||sh*t is approaching the fan|
|ERROR||sh*t has hit the fan|
|SEVERE||sh*t is spraying into the fan|
|CRITICAL||sh*t is spraying all over the room|
|ALERT||sh*t is piling up|
|FATAL||the room is flooding with sh*t|
|EMERGENCY||the fan has stopped spinning|
There is a tangible confusion around as to what Zeitgeist is and what it isn’t; what it can do and what it can’t do. This is partly our own fault because we could have communicated this whole thing better, for instance we have some very outdated wiki pages lying around that you should probably stay away from until we updated them. In this post I aim to give a semi technical run down of the core Zeitgeist functionality and how we expose it for you to work with. This should hopefully clear out some confusion.
At my day job we deal with a lot of incoming data for our product, which requires us to be able to calculate histograms and other statistics on the data-stream as fast as possible.
Assume we have a stream of events coming in one at a time, and we need to count the frequency of the different types of events in the stream.
I have lots of positive things to say about the OpenStack community. They managed to create a great mixture of professional yet agile and FLOSSy. Amazing CI/CD and devstack is just an awesome way to kickstart development on OpenStack.