Write metrics to different influxdb databases

[adrianlzt]

I have discovered this project while making a PR to mod_gearman.

I'm trying also to send icinga perfdata to InfluxDB, but I need to send each perfdata to a different database based on a custom template defined in each host.

Any idea if it will be possible to handle this with nagflux?

Thanks!

[Griesbacher]

Hi,
at the moment it not possible to do that, if mod_gearman is not able to do so. You could only collect the data from multiple mod_gearman servers but send them just to one InfluxDB. But we were already talking about something like that and I'll add such feature when I'm back to work, in a some weeks.
I was thinking about something like, multiple named serverconfigs within the nagflux config and if such a name is passed by a perfdata the data will be send to the corresponding InfluxDB. If the field is empty the default InfluxDB will be chosen.
Greetings Philip

[adrianlzt]

And choosing the influxdb databse with a custom variable?
@sni is thinking in expanding mod_gearman to be able to add custom variables: sni/mod_gearman#108 (comment)

[Griesbacher]

Exactly, e.g. you're setting a customvariable like NAGFLUX::TARGET to server1, then nagflux would send the data to the server1, which config/address is stored in a the nagflux config

[sni]

It would be possible if Mod-Gearman had a customizable performance data template so you could just define the data like ex.: ...NAGFLUX:DB=$_HOSTINFLUXDB$ or something like that.

[adrianlzt]

That would be perfect

…

On Fri, Feb 3, 2017, 15:40 Sven Nierlein ***@***.***> wrote: It would be possible if Mod-Gearman had a customizable performance data template so you could just define the data like ex.: ...NAGFLUX:DB=$_HOSTINFLUXDB$ or something like that. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#25 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADFnmKiQP2JTBnXLpDgQpQhuKhWsLHSQks5rYzxLgaJpZM4L1rFv> .

[adrianlzt]

Any update on this?
Thanks

[Griesbacher]

I'll be back at the office in one week and tackle the problem then. It's not forgotten.

[Griesbacher]

The latest release should solve this issue.