use raw host name + add time precision option

[BarthV]

This PR is based on old & outdated PR #21.

2 things :

• Change Body "name" => key.gsub!('-','') to "name" => key
  • AFAIK there's no technical limit that prevent us to use - in metric name.
• add time_precision in influx url option.
  • Default time precision is still s but we can now specify any precision that is supported by Influx rest API. (see : influxdb.go#L629 )
  • see also : https://influxdb.com/docs/v0.9/concepts/glossary.html#timestamp
  • time_precision option can now be specify inside the check's JSON output :

a check with a modified metrics-load script that use ms epoch timestamps

{
  "checks": {
    "metric-load": {
      "interval": 10,
      "type": "metric",
      "command": "metrics-load-ms.rb",
      "time_precision": "ms",
      "subscribers": [
        "all"
      ],
      "handlers": [
        "influx"
      ]
    }
  }
}

Result :

POST /db/sensu.metrics/series?time_precision=ms&u=*****&p=***** HTTP/1.1
Content-Type: application/x-www-form-urlencoded
Connection: close
Host: dev.metrics.local:8086
User-Agent: EventMachine HttpClient
Content-Length: 90

[{"name":"test.load_avg.one","columns":["time","value"],"points":[[1443099053000.0,2.0]]}]

With the real community plugin (that output with epoch in seconds) :

POST /db/sensu.metrics/series?time_precision=s&u=*****&p=***** HTTP/1.1
Content-Type: application/x-www-form-urlencoded
Connection: close
Host: dev.metrics.local:8086
User-Agent: EventMachine HttpClient
Content-Length: 87

[{"name":"test.load_avg.one","columns":["time","value"],"points":[[1443097834.0,0.0]]}]

[alfredopalhares]

Good research, thank you!