Files
cgm-remote-monitor/database_configuration.json
T
Ben West 9dcab2f8f7 minimal changes to get /pebble to do something as-is
With @brandonarbiter et al. :-)

* Also, this includes a change which allows mongo keys to be specified in the azure website.

curl -isv localhost:1337/pebble | json

* Adding handle: conn: 0x2108b90
* Adding handle: send: 0
* Adding handle: recv: 0
* Curl_addHandleToPipeline: length: 1
* - Conn 0 (0x2108b90) send_pipe: 1, recv_pipe: 0
* About to connect() to localhost port 1337 (#0)
*   Trying 127.0.0.1...
* Connected to localhost (127.0.0.1) port 1337 (#0)
> GET /pebble HTTP/1.1
> User-Agent: curl/7.32.0
> Host: localhost:1337
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Sun, 04 May 2014 19:57:44 GMT
< Connection: keep-alive
< Transfer-Encoding: chunked
<
{ [data not shown]
* Connection #0 to host localhost left intact
{
  "status": [
    {
      "now": 1399233463088
    }
  ],
  "bgs": [
    {
      "y": "156",
      "x": 1399231359000,
      "d": "05/04/2014 12:22:39 PM"
    },
    {
      "y": "154",
      "x": 1399231659000,
      "d": "05/04/2014 12:27:39 PM"
    },
    {
      "y": "152",
      "x": 1399231959000,
      "d": "05/04/2014 12:32:39 PM"
    },
    {
      "y": "151",
      "x": 1399232259000,
      "d": "05/04/2014 12:37:39 PM"
    },
    {
      "y": "150",
      "x": 1399232559000,
      "d": "05/04/2014 12:42:39 PM"
    }
  ]
}
2014-05-04 12:57:16 -07:00

5 lines
44 B
JSON

{
"url": null,
"collection": null
}