Closed bl1nk closed 8 years ago
Could you post the agent part of your command line? Is anything logged (to stdout) from jmxtrans-agent in the minutes after you have touched the configuration?
Also, if you could post what jmxtrans-agent logs at startup it would help.
Hi, to add to @kerlandsson comments, could you please activate:
@kerlandsson note: it may make sense to add a debug line to dump the new configuration with a TRACE
log message at https://github.com/jmxtrans/jmxtrans-agent/blob/95915e1b639f25539e1cc4ec898e1b2868f997d3/src/main/java/org/jmxtrans/agent/JmxTransExporter.java#L74-L74
The method JmxTransExporterConfiguration.toString()
dumps everything.
what do you think?
@cyrille-leclerc Makes sense. I went ahead and added it: 47f8efbbf4489459c4547519f70265b1850cfbad
@bl1nk we have deployed a new snapshot with @kerlandsson's improvement.
Could you test with it?
I've deployed a service with your new jmxtrans agent and with logging and diagnosis enabled. I removed a query from my jmxtrans config and it stopped reporting metrics for that query. After adding the query to my config jmxtrans started reporting metrics again, logs confirm both of this.
I would close this... for now. It didn't work with another query before, but I can't reproduce it. Thanks for your help!
I'm happy it is resolved! It might have been that you used a too old version - the configuration reload functionality is quite new.
We have been using 1.2.0 before, I just updated to 1.2.3
hey there,
This is the config file we use:
We use this script as a cronjob to update the config:
Problem is that the config file does not get reloaded or is not adding new queries to be reported to our influxdb. Re-deploying the service makes reporting work. The config file definitely gets updated by the cronjob.
What could be the problem here?