The time window is actually a fixed set of points, and when the master is
down no points are collected. The monitor often continues to run in the
background when the master is down, so it will remember the points from the
last session. Eventually the time will catch up and the monitor will
display one hour. You can always restart the monitor process to clear that
history. You can file a ticket if that's a big issue for you, but I think
the general plan is to move to a more standardized monitoring platform
eventually rather than continuing to build out this monitor.


On Sat, Mar 22, 2014 at 7:25 PM, Kepner, Jeremy - 0553 - MITLL <
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB