Difference between revisions of "XCP Archive/XCP diagnostic messages"
From Xen
Dave.scott (talk | contribs) (Created page with "In future we would like to have a diagnostic console which can help understand the state of an individual host (not pool). We would like to see: # instantaneous load information…") |
Dave.scott (talk | contribs) |
||
Line 11: | Line 11: | ||
# a live stream of messages, filtered with some expression |
# a live stream of messages, filtered with some expression |
||
# a live stream of logs, filtered with some expression |
# a live stream of logs, filtered with some expression |
||
+ | |||
+ | = Example messages = |
||
+ | |||
+ | The message format is not fixed, it can still be adjusted. Everything here is just an example. |
||
== Load information example == |
== Load information example == |
||
+ | |||
+ | == Alarm state example == |
||
+ | |||
+ | == Message queue example == |
||
+ | |||
+ | == Live stream of messages / logs example == |
Revision as of 14:35, 1 May 2013
In future we would like to have a diagnostic console which can help understand the state of an individual host (not pool). We would like to see:
- instantaneous load information, including
- disk and network throughput (bytes per sec)
- memory usage
- CPU usage
- number of messages per second across various internal control interfaces
- message latency distribution per internal service
- the states of "alarms", where an "alarm" is set when one or more of the load metrics crosses some threshold for some period of time. Perhaps we could 3 states and use red/amber/green (people love dashboards with traffic lights)
- the contents of message queues containing JSON control messages
- a live stream of messages, filtered with some expression
- a live stream of logs, filtered with some expression
Contents
Example messages
The message format is not fixed, it can still be adjusted. Everything here is just an example.