[Hawkular-dev] Another perspective on Availability

mike thompson mithomps at redhat.com
Tue Apr 7 13:40:55 EDT 2015


I found this view of availability interesting from open source monitoring project: CachetHQ(https://cachethq.io/ <https://cachethq.io/>)

Perhaps we might want to incorporate these ideas of component status versus incident status.

Component Status

https://docs.cachethq.io/v1.0/docs/component-statuses <https://docs.cachethq.io/v1.0/docs/component-statuses>

Status	Name	Description
1

Operational

The component is working.

2

Performance Issues

The component is experiencing some slowness.

3

Partial Outage

The component may not be working for everybody. This could be a geographical issue for example.

4

Major Outage

The component is not working for anybody.

Incident Status

https://docs.cachethq.io/v1.0/docs/incident-statuses <https://docs.cachethq.io/v1.0/docs/incident-statuses>


Status	Name	Description
0

Scheduled

This status is used for a scheduled status.

1

Investigating

You have reports of a problem and you're currently looking into them.

2

Identified

You've found the issue and you're working on a fix.

3

Watching

You've since deployed a fix and you're currently watching the situation.

4

Fixed

The fix has worked, you're happy to close the incident.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20150407/d69e455b/attachment-0001.html 


More information about the hawkular-dev mailing list