[dev.icinga.com #10480] Add InfluxDbWriter feature #3562
This issue has been migrated from Redmine: https://dev.icinga.com/issues/10480
Created by mfriedrich on 2015-10-28 18:55:17 +00:00
InfluxDB 0.9.x could still use the GraphiteWriter feature although they changed the tree notation from Graphite into a tag based system similar to OpenTSDB. By default the Graphite tree is stored "flat" and does not benefit from the InfluxDB tags and indexes. So there's not really a point in using the Graphite input with InfluxDB at this point.
2016-05-03 12:12:51 +00:00 by spjmurray 79c1e88
The text was updated successfully, but these errors were encountered:
Updated by spjmurray on 2016-04-12 14:44:56 +00:00
As discussed on IRC I'm happy to pick this up and maintain it. Here's what I imagine the configuration to look like:
The important bits:
InfluxDB also advises not to have more that one piece of data in a tag. Say if we had an MTU check applied to an interface we'd potentially generate mtueth0 as the service name from the check command mtu and the key we applied the check to eth0. In this case the mtu part is redundant as it's already available as $service.check_command$ and all we really care about is this data point is tagged to the interface eth0. This could be possibly surfaced by attaching the key to the service object.
Another idea is to make tags programmable:
In this example rather than encoding the template as a fixed string, it can be encoded as a hash. The measurement field is required, tags is optional. Any unresolved macros are omitted from the final set of tags to be sent to InfluxDB.
All I can think of right about now. Feel free to highlight any technical snafus I may be making.
Updated by mfriedrich on 2016-04-19 15:24:52 +00:00
You're way too fast for us catching up with a review. Much appreciated though :)
I've seen your blog post, leaving as a reference here: http://www.datacentred.co.uk/blog/integrating-icinga2-with-influxdb-and-grafana/
I'll take it for a review though it might take a while. Since it is a new feature it should target 2.5.0 then.
Updated by spjmurray on 2016-04-19 16:24:53 +00:00
shroud has already kicked my ass into shape so most of the major points should have been fixed! Bloody hell, the marketing droids don't hang about... well at least you get a bigger picture of what this is about.
Updated by mfriedrich on 2016-05-03 12:35:40 +00:00
You are actually using the http bits from libremote and fixed a bug over there, nice :)
The rest looks like you know your development foo, also helped by shroud :)
I've partially updated the documentation for addons/features and amended those changes into your patch.
I have no objections against the patch though I'm lacking a test setup for now. Once the snapshot packages are built, please invite others to test them before they are hitting the release 2.5.0 then.
Updated by mfriedrich on 2016-05-05 07:03:16 +00:00
Snapshot packages are built on each git commit for el7 (vagrant/docker trsts) and via cron for all other distributions once a day. You don't have to wait for the bugfix release 2.4.8, that release will just backport certsin fixes from the master development branch which currently targets 2.5.0 :)
TL;DR - start now.