@deitch the auth is the token. It is a jwt token, that was signed by a private key that rancher-server. The thing doing the authenticating (websocket-proxy) has the public key.
The data looks like this:
[
{
"id": "1i12",
"resourceType": "container",
"memLimit": 1044586496,
"timestamp": "2016-01-27T19:41:34.001446366Z",
"cpu": {
"usage": {
"total": 31581057,
"per_cpu_usage": [
31581057
],
"user": 10000000,
"system": 20000000
},
"load_average": 0
},
"diskio": {},
"memory": {
"usage": 524288,
"working_set": 245760,
"container_data": {
"pgfault": 3163,
"pgmajfault": 0
},
"hierarchical_data": {
"pgfault": 3163,
"pgmajfault": 0
}
},
"network": {
"name": "eth0",
"rx_bytes": 648,
"rx_packets": 8,
"rx_errors": 0,
"rx_dropped": 0,
"tx_bytes": 648,
"tx_packets": 8,
"tx_errors": 0,
"tx_dropped": 0,
"interfaces": [
{
"name": "eth0",
"rx_bytes": 648,
"rx_packets": 8,
"rx_errors": 0,
"rx_dropped": 0,
"tx_bytes": 648,
"tx_packets": 8,
"tx_errors": 0,
"tx_dropped": 0
}
]
},
"filesystem": [
{
"device": "/dev/sda1",
"capacity": 19507089408,
"usage": 12288,
"available": 0,
"reads_completed": 0,
"reads_merged": 0,
"sectors_read": 0,
"read_time": 0,
"writes_completed": 0,
"writes_merged": 0,
"sectors_written": 0,
"write_time": 0,
"io_in_progress": 0,
"io_time": 0,
"weighted_io_time": 0
}
],
"task_stats": {
"nr_sleeping": 0,
"nr_running": 0,
"nr_stopped": 0,
"nr_uninterruptible": 0,
"nr_io_wait": 0
}
}
}
I actually just pulled that from an actual websocket message sent across to the browser via chrome developer tools. I dont believe we have an official schema for this data.