部署ONEAPM JMX远程监控无法找到JMX文件

111106 · 2015-12-21 09:32:19 UTC

nail · 2015-12-22 02:17:25 UTC

这个应该是 tomcat.yaml 配置报错，可以把配置都贴出来我们看一看

111106 · 2015-12-22 02:43:23 UTC

这是tomcat.yaml的配置
instances:

host: localhost
port: 7199

user: monitorRole

password: QED

process_name_regex: .process_name. # Instead of specifying a host, and port. The agent can connect using the attach api.

# This requires the JDK to be installed and the path to tools.jar to be set below.

tools_jar_path: /usr/lib/jvm/java/lib/tools.jar # To be set when process_name_regex is set

name: tomcat_instance
java_bin_path: /usr/lib/jvm/java/bin # Optional, should be set if the agent cannot find your java executable
java_options: “-Xmx200m -Xms50m” # Optional, Java JVM options
trust_store_path: /path/to/trustStore.jks # Optional, should be set if ssl is enabled
trust_store_password: password
tags:
env: stage

newTag: test

List of metrics to be collected by the integration

Read http://www.oneapm.com/docs/ci/services/jmx.html to learn how to customize it

init_config:
conf:
- include:
type: ThreadPool
attribute:
maxThreads:
alias: tomcat.threads.max
metric_type: gauge
currentThreadCount:
alias: tomcat.threads.count
metric_type: gauge
currentThreadsBusy:
alias: tomcat.threads.busy
metric_type: gauge
- include:
type: GlobalRequestProcessor
attribute:
bytesSent:
alias: tomcat.bytes_sent
metric_type: counter
bytesReceived:
alias: tomcat.bytes_rcvd
metric_type: counter
errorCount:
alias: tomcat.error_count
metric_type: counter
requestCount:
alias: tomcat.request_count
metric_type: counter
maxTime:
alias: tomcat.max_time
metric_type: gauge
processingTime:
alias: tomcat.processing_time
metric_type: counter
- include:
j2eeType: Servlet
attribute:
processingTime:
alias: tomcat.servlet.processing_time
metric_type: counter
errorCount:
alias: tomcat.servlet.error_count
metric_type: counter
requestCount:
alias: tomcat.servlet.request_count
metric_type: counter
- include:
type: Cache
accessCount:
alias: tomcat.cache.access_count
metric_type: counter
hitsCounts:
alias: tomcat.cache.hits_count
metric_type: counter
- include:
type: JspMonitor
jspCount:
alias: tomcat.jsp.count
metric_type: counter
jspReloadCount:
alias: tomcat.jsp.reload_count
metric_type: counter

fangh · 2015-12-22 06:36:01 UTC

你的tomcat 的 jmx开启了么，需要jmx开启了才可以监控到数据呢

111106 · 2015-12-22 06:42:40 UTC

开启了，指定的jmx端口也是通的

fangh · 2015-12-22 07:06:55 UTC

你执行一下 sudo service oneapm-ci-agent configcheck 看看yaml有没有错误
执行 sudo service oneapm-ci-agent jmx list_everything

请把上面两个命令的输出贴出来吧

111106 · 2015-12-22 08:14:24 UTC

root@bogon:/etc/oneapm-ci-agent/conf.d# /etc/init.d/oneapm-ci-agent configcheck
jmx.yaml contains errors:
while parsing a block mapping
in “”, line 1, column 1
did not find expected key
in “”, line 12, column 3
tomcat.yaml contains errors:
while parsing a block collection
in “”, line 2, column 3
did not find expected ‘-’ indicator
in “”, line 9, column 3
Fix the invalid yaml files above in order to start the OneAPM CI Agent. A useful external tool for yaml parsing can be found at http://yaml-online-parser.appspot.com/
root@bogon:/etc/oneapm-ci-agent/conf.d# /etc/init.d/oneapm-ci-agent jmx list_everything
2015-12-22 16:13:04,445 | ERROR | ci.collector | jmxfetch(jmxfetch.py:203) | Unable to parse yaml config in /etc/oneapm-ci-agent/conf.d/jmx.yaml
2015-12-22 16:13:04,447 | ERROR | ci.collector | jmxfetch(jmxfetch.py:203) | Unable to parse yaml config in /etc/oneapm-ci-agent/conf.d/tomcat.yaml
Couldn’t find any valid JMX configuration in your conf.d directory: /etc/oneapm-ci-agent/conf.d
Have you enabled any JMX check ?
If you think it’s not normal please get in touch with OneAPM Support
root@bogon:/etc/oneapm-ci-agent/conf.d# cat jmx.yaml
init_config:

instances:

host: localhost
port: 7199

user: monitorRole

password: QED

process_name_regex: .process_name. # Instead of specifying a host, and port. The agent can connect using the attach api.

# This requires the JDK to be installed and the path to tools.jar to be set below.

tools_jar_path: /usr/lib/jvm/java-7-openjdk-amd64/lib/tools.jar # To be set when process_name_regex is set

name: jmx_instance

java_bin_path: /usr/lib/jvm/java/bin # Optional, should be set if the agent cannot find your java executable
java_options: “-Xmx200m -Xms50m” # Optional, Java JVM options
trust_store_path: /path/to/trustStore.jks # Optional, should be set if ssl is enabled
trust_store_password: password
tags:
env: stage

newTag: test

# List of metrics to be collected by the integration
# Read http://www.oneapm.com/docs/ci/services/jmx.html to learn how to customize it
# conf:
   - include:
       domain: my_domain
       bean:
         - my_bean
         - my_second_bean
       attribute:
         attribute1:
           metric_type: counter
           alias: jmx.my_metric_name
         attribute2:
           metric_type: gauge
           alias: jmx.my2ndattribute
   - include:
       domain: 2nd_domain
     exclude:
       bean:
         - excluded_bean
   - include:
       domain_regex: regex_on_domain
     exclude:
       bean_regex:
         - regex_on_excluded_bean

root@bogon:/etc/oneapm-ci-agent/conf.d# cat tomcat.yaml
instances:

host: localhost
port: 7199

user: monitorRole

password: QED

process_name_regex: .process_name. # Instead of specifying a host, and port. The agent can connect using the attach api.

# This requires the JDK to be installed and the path to tools.jar to be set below.

tools_jar_path: /usr/lib/jvm/java/lib/tools.jar # To be set when process_name_regex is set

name: tomcat_instance
java_bin_path: /usr/lib/jvm/java/bin # Optional, should be set if the agent cannot find your java executable
java_options: “-Xmx200m -Xms50m” # Optional, Java JVM options
trust_store_path: /path/to/trustStore.jks # Optional, should be set if ssl is enabled
trust_store_password: password
tags:
env: stage

newTag: test

List of metrics to be collected by the integration

Read http://www.oneapm.com/docs/ci/services/jmx.html to learn how to customize it

init_config:
conf:
- include:
type: ThreadPool
attribute:
maxThreads:
alias: tomcat.threads.max
metric_type: gauge
currentThreadCount:
alias: tomcat.threads.count
metric_type: gauge
currentThreadsBusy:
alias: tomcat.threads.busy
metric_type: gauge
- include:
type: GlobalRequestProcessor
attribute:
bytesSent:
alias: tomcat.bytes_sent
metric_type: counter
bytesReceived:
alias: tomcat.bytes_rcvd
metric_type: counter
errorCount:
alias: tomcat.error_count
metric_type: counter
requestCount:
alias: tomcat.request_count
metric_type: counter
maxTime:
alias: tomcat.max_time
metric_type: gauge
processingTime:
alias: tomcat.processing_time
metric_type: counter
- include:
j2eeType: Servlet
attribute:
processingTime:
alias: tomcat.servlet.processing_time
metric_type: counter
errorCount:
alias: tomcat.servlet.error_count
metric_type: counter
requestCount:
alias: tomcat.servlet.request_count
metric_type: counter
- include:
type: Cache
accessCount:
alias: tomcat.cache.access_count
metric_type: counter
hitsCounts:
alias: tomcat.cache.hits_count
metric_type: counter
- include:
type: JspMonitor
jspCount:
alias: tomcat.jsp.count
metric_type: counter
jspReloadCount:
alias: tomcat.jsp.reload_count
metric_type: counter

nail · 2015-12-22 08:23:49 UTC

你贴出来的第一个命令的返回结果显示，你的 jmx.yaml 和 tomcat.yaml 配置文件的格式有错误。

daowanlilai · 2016-01-04 07:25:53 UTC

配置文件格式错误，不符合 yaml 缩进格式，此外 java 路径也不对，java_bin_path: /usr/lib/jvm/java/bin ，应该是 java_bin_path: /usr/lib/jvm/java/bin/java 修改后成功