Application Presence
I’ve been thinking a lot about distributed applications lately, in particular, those that make use of distributed data stores and XMPP.
What began as an experiment with application log monitoring and retention using log4j and XMPP has grown into an idea for presence at the application or service level.
What if your internet service or application used XMPP to report changes in “mood” or more specifically changes in service level? What if every application had an embedded SLA monitoring and reporting component?
Let’s say that you run an internet-scale service such as del.icio.us or flickr and every node communicated it’s service level to a federated XMPP service. Your ops team could subscribe to specific or aggregated service levels and receive notification of SLA thresholds and at the same time have real-time presence or “pulse”.
You could define service level or “mood” for the application at specific granular levels and use simple filtering of log messages to set/project the application’s “mood”.
Storage service level: 100% (no outage in the last 10 mins.)
User service level: 99.9% (5 dropped in the last 10 mins.)
–
Over all service level: 99.99% (within advertised SLA range)
