fleet/server
Zachary Wasserman 971eca9b2b Push distributed query errors over results websocket (#878)
As of recently, osquery will report when a distributed query fails. We now
expose errors over the results websocket. When a query errored on the host, the
`error` key in the result will be non-null. Note that osquery currently doesn't
provide any details so the error string will always be "failed". I anticipate
that we will fix this and the string is included for future-proofing.

Successful result:

```
{
  "type": "result",
  "data": {
    "distributed_query_execution_id": 15,
    "host": {
    ... omitted ...
    },
    "rows": [
      {
        "hour": "1"
      }
    ],
    "error": null
  }
}
```
Failed result:

```
{
  "type": "result",
  "data": {
    "distributed_query_execution_id": 14,
    "host": {
    ... omitted ...
    },
    "rows": [
    ],
    "error": "failed"
  }
}
```
2017-01-10 19:34:32 -08:00
..
config Use redis for distributed query results when not in dev mode (#653) 2016-12-15 16:13:23 -08:00
contexts Quick contexts additions (#739) 2017-01-09 08:10:02 -07:00
datastore Extra comma in SQL string (#876) 2017-01-10 16:25:26 -07:00
errors add the error message to DatabaseError (#846) 2017-01-10 11:01:47 -05:00
kolide Push distributed query errors over results websocket (#878) 2017-01-10 19:34:32 -08:00
mail Add invite email template and use the new invite mailer pattern (#711) 2016-12-28 11:55:03 -05:00
mock add mock package and use in invite tests (#603) 2017-01-10 16:49:14 -05:00
pubsub Fix failing Redis query results test (#864) 2017-01-10 11:56:38 -08:00
service Push distributed query errors over results websocket (#878) 2017-01-10 19:34:32 -08:00
test Host summary endpoint (#742) 2017-01-04 14:16:17 -07:00
version Organizing go code (#241) 2016-09-26 11:48:55 -07:00
websocket Quick contexts additions (#739) 2017-01-09 08:10:02 -07:00