Added functionality to receive JSON check results

[box293]

This addresses issue #7.

Here is the JSON structure.

Host

{ "checkresults": [ { "checkresult": { "type": "host", "checktype": "1" }, "hostname": "YOUR_HOSTNAME", "state": "0", "output": "OK" } ] }

Service

{ "checkresults": [ { "checkresult": { "type": "service", "checktype": "1" }, "hostname": "YOUR_HOSTNAME", "servicename" : "YOUR_SERVICE", "state": "0", "output": "OK" } ] }

Submit results with &JSONDATA=

Also allows &pretty=true.

Here are some examples with output.

1 Host

curl -f -d 'token=XXXXX&cmd=submitcheck&JSONDATA={ "checkresults": [ { "checkresult": { "type": "host", "checktype": "1" }, "hostname": "YOUR_HOSTNAME", "state": "0", "output": "OK" } ] }' http://127.0.0.1/nrdp/
{ "result" : {  "status" : "0", "message" : "OK", "output" : "1 checks processed." } }

1 Host 2 Services with pretty

curl -f -d 'token=XXXXX&cmd=submitcheck&JSONDATA={ "checkresults": [ { "checkresult": { "type": "host", "checktype": "1" }, "hostname": "YOUR_HOSTNAME", "state": "0", "output": "OK" }, { "checkresult": { "type": "service", "checktype": "1" }, "hostname": "YOUR_HOSTNAME", "servicename" : "YOUR_SERVICE", "state": "0", "output": "OK" }, { "checkresult": { "type": "service", "checktype": "1" }, "hostname": "YOUR_HOSTNAME", "servicename" : "YOUR_SERVICE_TWO", "state": "2", "output": "CRITICAL" } ] }&pretty=true' http://127.0.0.1/nrdp/
{
  "result" : {
    "status" : "0",
    "message" : "OK",
    "output" : "3 checks processed."
  }
}

Incorrectly formatted JSON:

curl -f -d 'token=XXXXX&cmd=submitcheck&JSONDATA={ "checkresults": [ { "checkresult": { "type": "host", "checktype": "1" }, "hostname": "YOUR_HOSTNAME", "state": "0", "output": "OK" ] }' http://127.0.0.1/nrdp/2
{ "result" : { "status" : "-1", "message" : "BAD JSON" } }

If this is pull request is accepted I'll then proceed to update the send_nrdp clients to support JSON.

[jomann09]

From looking at this, it seems like it'll work. I will have to test it (and I am sure Bryan will too) and then we can pull this in for 1.5.0 - once this gets added, and whatever changes we make get applied, we really should be ready for a 1.5.0 release.

[box293]

I think perhaps we should strip out the change comments / acknowledgements and add them to a central CHANGES.txt file.

Also might be worth setting the clients and server on the same version. For example I think send_nrpd.sh is 0.6, might make more sense if it is 1.5.

[hedenface]

Thanks @box293 !