i-ky / effluence Goto Github PK

InfluxDB 2.0 is currently in alpha beta generally available. This issue is created mainly to track user interest in it. Please leave a 🚀 reaction if you want/need it.

• Replace continuous query for trend calculation with a task like described here or here
• Fix broken links to InfluxDB documentation
• Check that Grafana integration still works

Hello,

while testing the precompiled module for CentOS with both Zabbix 4.0 and 4.2 I get this error from the log:

# tail /var/log/zabbix/zabbix_server.log 
  3136:20190627:110148.052 Jabber notifications:      YES
  3136:20190627:110148.052 Ez Texting notifications:  YES
  3136:20190627:110148.052 ODBC:                      YES
  3136:20190627:110148.052 SSH2 support:              YES
  3136:20190627:110148.052 IPv6 support:              YES
  3136:20190627:110148.052 TLS support:               YES
  3136:20190627:110148.052 ******************************
  3136:20190627:110148.052 using configuration file: /etc/zabbix/zabbix_server.conf
  3136:20190627:110148.052 cannot load module "effluence.so": /var/lib/zabbix/modules/effluence.so: invalid ELF header
  3136:20190627:110148.052 loading modules failed, exiting...

Thank you in advance,
Eric

Will it support Zabbix 6.0 and 7.0?

I installed it on Zabbix 6.4.4.
Zabbix service is running, but the data has not appeared in the InfluxDB database.

Hello everyone,

I have a issue when zabbix try to load this module.
The OS is Centos 7.4

log :

 25902:20181018:110619.302 using configuration file: /etc/zabbix/zabbix_server.conf
 25902:20181018:110619.302 cannot load module "effluence.so": /usr/lib/zabbix/modules/effluence.so: undefined symbol: yaml_parser_set_input_file
 25902:20181018:110619.302 loading modules failed, exiting...

This is my configuration file :

[dbl, uint]: # for both Numeric (float) and Numeric (unsigned)
  url: http://10.2.20.39:8086
  db: numeric
  user: zabbix

I have installed these packages :

• libyaml-0.1.4-11.el7_0.x86_64
• libcurl-7.29.0-42.el7.x86_64

Has anyone ever had this problem?
Thank you for your work

Monitoring InfluxDB instance will never be the goal of this module (there should be another module for that), but adding some self-monitoring would be nice. Total and per data type number of values sent to InfluxDB, time spent doing HTTP requests, etc. This would help user to judge if the chosen Zabbix-module-InfluxDB configuration provides optimal performance.

However, there are technical difficulties. Performance metrics can be obtained by history syncer processes doing actual work, but need to be provided somehow to poller processes to report them back to Zabbix. This will require some tedious inter-process communication and I'm not going to spend time on that unless there is some serious demand.

This can be used as a starting point.

This will greatly simplify the installation process.

Quoting InfluxDB documentation:

We recommend using the least precise precision possible as this can result in significant improvements in compression.

Investigate if precision has any real effect and, if it actually does, make it configurable.

I don't expect this to get worked on but I'll throw it up here anyways.

Add an optional configuration file attribute to configure (per data type) retention policy to use, pass rp variable to /write queries.

Based on #13.

If InfluxDB is not available or slow to respond...

module is getting backed up trying to write data to influx and not timing out or failing in any way

This will...

cause some silent backlog in zabbix and suddenly no data at all is being inserted into zabbix

As a solution:

• Warn users about potential issue and insist on the importance of monitoring InfluxDB availability/performance.
• Test and document influxdb-relay as a workaround.
• Introduce timeout: configuration option, drop data if it is not possible to insert it into InfluxDB in a timely fashion, assume no/infinite timeout if it's not configured (current behaviour).

At the moment README.md is a long read. I think it may be a good idea to offload large parts of it into Wiki section. This will separate documentation from the code and will make writing documentation easier.