Issue related to configuration of influxdb with jmxtrans
See original GitHub issueHi i am getting the below error while setting up influxbd with jmxtrans for monitoring data from kafka
[19 Jun 2017 17:39:53] [jmxtrans-result-7] 256568 WARN (com.googlecode.jmxtrans.jmx.ResultProcessor$1:60) - Could not write results [Result(attributeName=HeapMemoryUsage, className=sun.management.MemoryImpl, objDomain=java.lang, typeName=type=Memory, values={init=1073741824, committed=1073741824, max=1073741824, used=510296072}, epoch=1497874193415, keyAlias=jvmMemory), Result(attributeName=NonHeapMemoryUsage, className=sun.management.MemoryImpl, objDomain=java.lang, typeName=type=Memory, values={init=2555904, committed=53870592, max=-1, used=52743976}, epoch=1497874193415, keyAlias=jvmMemory)] of query Query(objectName=java.lang:type=Memory, keys=[], attr=[HeapMemoryUsage, NonHeapMemoryUsage], typeNames=[], resultAlias=jvmMemory, useObjDomainAsKey=false, allowDottedKeys=false, useAllTypeNames=false, outputWriterInstances=[com.googlecode.jmxtrans.model.output.support.ResultTransformerOutputWriter@4dc41b51]) to output writer com.googlecode.jmxtrans.model.output.support.ResultTransformerOutputWriter@4dc41b51
java.lang.RuntimeException: {"error":"error parsing query: found NOT, expected ; at line 1, char 20"}
at org.influxdb.impl.InfluxDBErrorHandler.handleError(InfluxDBErrorHandler.java:19)
at retrofit.RestAdapter$RestHandler.invoke(RestAdapter.java:242)
at org.influxdb.impl.$Proxy29.query(Unknown Source)
at org.influxdb.impl.InfluxDBImpl.createDatabase(InfluxDBImpl.java:205)
at com.googlecode.jmxtrans.model.output.InfluxDbWriter.doWrite(InfluxDbWriter.java:151)
at com.googlecode.jmxtrans.model.output.support.ResultTransformerOutputWriter.doWrite(ResultTransformerOutputWriter.java:50)
at com.googlecode.jmxtrans.jmx.ResultProcessor$1.run(ResultProcessor.java:58)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
embedded-jmxtrans - Need to export metrics on Influx-Grafana
I don't see influxDB outputwriter in embedded-jmxtrans but i see it in jmxtrans , we are using embedded-jmxtrans for our scala code based ......
Read more >InfluxDB line protocol tutorial - InfluxData Documentation
CLI. Write data to InfluxDB using the InfluxDB command line interface (CLI). Launch the CLI, use the relevant database, and put INSERT ...
Read more >Monitoring Apache Kafka with Grafana / InfluxDB via JMX
Here is how to monitor Kafka with Grafana and InfluxDB. ... blog post and finally another post on this topic I've provided a...
Read more >Monitoring node - No Magic Documentation
Jmxtrans - Collector to retrieve JMX metrics from remote hosts. Install and configure InfluxDB. Install InfluxDB on the monitoring node: Create ...
Read more >Chapter 7 – Monitoring | Mastering Apache Cassandra 3.x
JMXTrans : Introduction to JMXTrans: Retrieved from ... InfluxData: InfluxDB: InfluxDB Line Protocol tutorial: Retrieved from ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
can confirm the issue is resolved in the v265 of jmxtrans.
@4nky-mnky thanks for the report!