Skip to content
This repository has been archived by the owner on Oct 6, 2023. It is now read-only.

InfluxDB problems after upgrade to 3.0.7-1 #112

Open
mavynet opened this issue Jul 12, 2017 · 1 comment
Open

InfluxDB problems after upgrade to 3.0.7-1 #112

mavynet opened this issue Jul 12, 2017 · 1 comment

Comments

@mavynet
Copy link

mavynet commented Jul 12, 2017

Hello,

We have some problems with the broker after update to the final version:

  1. if we change the setting for the broker debug messages from yes to no or vice versa, the configuration for the influxdb output is lost (fields empty)
  2. only data for the hosts monitored by poller central are sent to influx, the hosts from satellites are not updated
  3. some readings are sent to influx with spaces that generate errors: {"error":"unable to parse 'status,index_id=18838,host=CentreonLocalChecks,service=vmware connections time="1499856989",value="0" 1499856989': invalid field format

Is there some configuration setting that we missed or something changed with the new version?

Thanks

@jben94
Copy link

jben94 commented Nov 16, 2017

Hi @mavynet,

I do not know if your problem is fixed.

But I think the problem is your variable "service" and "time", it is too much.

Sample query:
cpu_load_short,host=server02,region=us-west value=0.55 1422568543702900257

So for you:

status,index_id=18838,host=CentreonLocalChecks,service=vmware connections time="1499856989",value="0" 1499856989

I find it unfortunate to put the "value" field in "string" form. It is less obvious to make calculations later.
But the value of service should be a string because it will have spacing problem

status,index_id=18838,host=CentreonLocalChecks,service="vmware connections" value="0" 1499856989

Regards.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants