Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Add support for output_metric_tags #2160
Add a new
type: Check api_version: core/v2 metadata: namespace: default name: check_sensu_io spec: command: "check_http -u https://sensu.io/ -H sensu.io -N", runtime_assets: - check_http_v0.1 publish: true interval: 10 subscriptions: - docker output_metric_format: nagios_perfdata output_metric_handlers: - influxdb output_metric_tags: entity: entity.name namespace: entity.namespace app: entity.metadata.labels.application_id
Bonus points if we could support access to array objects (e.g.
No support is provided for collecting tags during metric output extraction.
See description above.
Currently, when using metric output extraction with the trusty Nagios
The challenge with this is that when sent to InfluxDB, these appear as very generically named measurements (i.e. "time" and "size"), with no context about which system or service reported the metrics (because there are no tags). Compared with the graphite-style measurement name you would get with Sensu 1.x (e.g.
In further discussion on this issue, it is worth noting that this really only impacts metrics collected in formats that don't natively support tags (e.g. Nagios PerfData and Graphite plaintext). Metrics collected in formats that support tags will have their tags extracted or "passed through".
The good/bad news about that is most of the Sensu Community Plugins have standardized around Graphite plaintext format for metrics collection.