we’re running a multi-zone Icinga environment that monitors environments of multiple customers. It’s currently writing into a single influxdb with v1.8. In addition we use Grafana to create performance data reports from that influxdb.
In a later step we have to let external users create their own reports in Grafana which requires direct access to the influxdb. Unfortunately that single db also contains data from other companies. So we either need a security layer in influx or to split the data.
Is it possible to configure Influxdbwriter (or Influxdb2writer) to filter the data before writing? E.g. write all data to influxdb A, but just write data for company B to a different influxdb B?
I assume this isn’t possible now - but if I were to create a PR that implemented macro expansion in the InfluxDB configuration attributes, are there any obvious concerns with this?
We would benefit from this greatly, as we monitor around ~120 customers (mostly in their own zone) - we have a unique organization in Grafana for each customer, but without InfluxDB enterprise, there is no way to prevent one customer viewing another customers data.
This also causes performance issues with InfluxDB as we have high levels of cardinality (e.g SNMP interface perfdata tagged with the interface name, customer ID, etc.