[Ovirt-devel] [R&D] Breaking the Browser

[David Lutterkort]

On Fri, 2008-07-04 at 22:33 -0400, mark wagner wrote:
> > What graph _absolutely has to be_ realtime? In all of the cases I
> > could come up with
> > not a one wouldn't be serviced by near-realtime graphs. Do you expect
> > users to have
> > ovirt graph screens up on a bank of plasma displays watching node
> > stats in realtime?
> 
> So if your job is to monitor the 25 hosts in your pool and take immediate and
> effective action to mitigate any performance or catastrophic issues in said
> pool within one minute and 26 secs (3 nines, assuming this is the only issue
> that day) of the event, how are you going to monitor your pool ?
> 
> If we don't provide the ability to notify immediately when a host goes down,
> you are rapidly eating into time specified to resolve a problem.

This is completely unrealistic - notification of any sort of important
event would not come through a web browser, they would be sent from a
monitoring system to a pager or similar.

Graphs in the browser might help understand what is happening and why
load is the way it is, but it would never be used as the primary
notification.

David