The Mem entity on Sun seems to have acquired this neat ability to store all the readings during a QOS server outage and report them to the server when it returns. The drawback: it's all reported at the same timestamp :( This causes "interesting" output on the reporting side.
Logged In: YES
user_id=105929
Looks like this is intentional behavior.. the qos agent specifically queues reports due to server-down. This should get rolled over to a feature request to put a datestamp in the entity protocol so the data can be logged properly instead of bunching up.
Logged In: YES
user_id=105929
Drop the priority on this since it's design behavior, as nasty as it is... the alternatives aren't too pretty either :(
Logged In: YES
user_id=105929
Drop the priority on this since it's design behavior, as nasty as it is... the alternatives aren't too pretty either :(