prometheus监控java程序

可参考链接，需找开发商量jmx端口暴露方式

https://www.jianshu.com/p/8a5e681b18ce 或者 http://www.mamicode.com/info-detail-2323750.html

上图两个链接为不同的jmx暴露方式，实则大同小异，需跟开发商量，以免程序启动不了

下载jmx_exporter的jar包

https://repo1.maven.org/maven2/io/prometheus/jmx/jmx_prometheus_javaagent/0.3.1/jmx_prometheus_javaagent-0.3.1.jar

创建配置文件namenode.yaml(datanode.yaml)放在任意位置，内容为你想要的metrics

参考配置：

---
startDelaySeconds: 0
hostPort: master:1234 #master为本机IP（一般可设置为localhost）；1234为想设置的jmx端口（可设置为未被占用的端口）
#jmxUrl: service:jmx:rmi:///jndi/rmi://127.0.0.1:1234/jmxrmi
ssl: false
lowercaseOutputName: false
lowercaseOutputLabelNames: false

其他参数参考：

Name	Description
startDelaySeconds	start delay before serving requests. Any requests within the delay period will result in an empty metrics set.
hostPort	The host and port to connect to via remote JMX. If neither this nor jmxUrl is specified, will talk to the local JVM.
username	The username to be used in remote JMX password authentication.
password	The password to be used in remote JMX password authentication.
jmxUrl	A full JMX URL to connect to. Should not be specified if hostPort is.
ssl	Whether JMX connection should be done over SSL. To configure certificates you have to set following system properties: `-Djavax.net.ssl.keyStore=/home/user/.keystore` `-Djavax.net.ssl.keyStorePassword=changeit` `-Djavax.net.ssl.trustStore=/home/user/.truststore` `-Djavax.net.ssl.trustStorePassword=changeit`
lowercaseOutputName	Lowercase the output metric name. Applies to default format and `name`. Defaults to false.
lowercaseOutputLabelNames	Lowercase the output metric label names. Applies to default format and `labels`. Defaults to false.
whitelistObjectNames	A list of ObjectNames to query. Defaults to all mBeans.
blacklistObjectNames	A list of ObjectNames to not query. Takes precedence over `whitelistObjectNames`. Defaults to none.
rules	A list of rules to apply in order, processing stops at the first matching rule. Attributes that aren‘t matched aren‘t collected. If not specified, defaults to collecting everything in the default format.
pattern	Regex pattern to match against each bean attribute. The pattern is not anchored. Capture groups can be used in other options. Defaults to matching everything.
attrNameSnakeCase	Converts the attribute name to snake case. This is seen in the names matched by the pattern and the default format. For example, anAttrName to an_attr_name. Defaults to false.
name	The metric name to set. Capture groups from the `pattern` can be used. If not specified, the default format will be used. If it evaluates to empty, processing of this attribute stops with no output.
value	Value for the metric. Static values and capture groups from the `pattern` can be used. If not specified the scraped mBean value will be used.
valueFactor	Optional number that `value` (or the scraped mBean value if `value` is not specified) is multiplied by, mainly used to convert mBean values from milliseconds to seconds.
labels	A map of label name to label value pairs. Capture groups from `pattern` can be used in each. `name` must be set to use this. Empty names and values are ignored. If not specified and the default format is not being used, no labels are set.
help	Help text for the metric. Capture groups from `pattern` can be used. `name` must be set to use this. Defaults to the mBean attribute decription and the full name of the attribute.
type	The type of the metric, can be `GAUGE`, `COUNTER` or `UNTYPED`. `name` must be set to use this. Defaults to `UNTYPED`.

前提：

1.java程序的目录结构展示（因断网环境所以没办法用树状图命令tree来展示，只能截图）

如上图所示，一个服务器有一个java程序，其中子程序包括manager(管理端), server，client，PRM, Utilities，关联关系是agent和server要从manager管理端获取各种参数，server再向agent发包，这样程序就算跑起来了。

这里主要监控server和client

下图为manager和server以及其中一个client的目录结构

各conf目录下都有一个namenode.conf,内容如下

startDelaySeconds: 10
jmxUrl: service:jmx:rmi:///jndi/rmi://127.0.0.1:${JMX_PORT}/${APP_NAME}
ssl: false
lowercaseOutputName: false
lowercaseOutputLabelNames: false

各conf目录下都有一个namenode.yaml,内容如下(此为manager下conf中的)

各个子程序bin目录下都有关于程序的启动脚本，先执行1脚本启动，然后2脚本是让程序开启一个prometheus jmx端口，以便jmx exporter探针找到这个端口，收集到java程序的metrics信息，达到监控的目的

下图是npds-manager.sh脚本中实现开启jmx端口的脚本信息，完整脚本信息在最下面

这样启动java程序后，访问ip加自定义的端口9210就能访问到manager的mertrics信息了,达到监控的目的

然后找开发要他们想要监控的参数，以我为例要的参数如下图：

再以此一个个配置，就能实现监控了

vim npds-manager.sh

#!/bin/bash
then
echo "=================================================================="
echo "ERROR: Please set the JAVA_HOME variable in your environment!"
echo "=================================================================="
exit 20
fi

cd=$(pwd)

if [ ${cd:0-3} != "bin" ]
then
echo "=================================================================="
echo "ERROR: Please execute the script in the bin directory!"
echo "=================================================================="
exit 21
fi

APP_HOME=${cd%/bin}

APP_NAME=NPDS-Manager

APP_MAIN_CLASS=cn.com.greattimes.npds.manager.boot.ManagerBootstrap

JPS_FLAG=ManagerBootstrap

LIBRARY_PATH=$APP_HOME/jni

JAVA_OPTS="-server
-Xmx1G
-Xms1G"

DEBUG=0

RET_CODE=0

FORCE_KILL=0

CHECK_STATUS=1

CHECK_STATUS_TIMEOUT=5

check_env() {
local DIR=${APP_HOME:POS+1}

if [ ! $DIR == $APP_NAME ]
then
echo "=================================================================="
exit 22
fi

if [ ! -d "$APP_HOME/logs" ]
then
mkdir $APP_HOME/logs
fi

if [ $DEBUG -eq 1 ]
then
local DBG_PORT=9310
fi
}

check_prometheus() {
if [ -e "$APP_HOME/conf/namenode.conf" ]
then
local JMX_PORT=15914
fi

if [ -e "$APP_HOME/conf/namenode.yaml" ]
then
local WEB_PORT=9210
fi
}

check() {
PID=0
local TMP=$(jps -v | grep $JPS_FLAG | grep $APP_HOME)
TMP=${TMP%% *}

if [ ${#TMP} -ne 0 ]
then
PID=$TMP
fi

if [ $PID -ne 0 ]
then
RUNNING=1
else
RUNNING=0
fi
}

print() {
if [ $QUIET_MODE -eq 1 ]
then
return
fi

echo "$1" "$2"
}
if [ ! -n "$1" ]
then
return 2
fi

ps -p $1 > /dev/null

if [ $? -eq 0 ]
then
kill -9 $1
fi
}

start() {
check

if [ $RUNNING -eq 1 ]
then
print "=================================================================="
print "WARN: $APP_NAME(PID=$PID) is running."
print "=================================================================="
return 1
fi

info

if [ $CHECK_STATUS -eq 0 ]
then
print -n "..."
print
print "------------------------------------------------------------------"
print "WARN: $APP_NAME is started without checking status."
print
return 1
fi

local n=0

for ((; n<$CHECK_STATUS_TIMEOUT; n++))
do
if [ $n -lt 3 ]
then
sleep 1
print -n "."
else
check

if [ $RUNNING -eq 1 ]
then
print
print "Done!"
print
return 0
else
sleep 1
fi
fi
done

print
print "------------------------------------------------------------------"
print "ERROR: $APP_NAME failed to start for unknown reasons. "
print " Please refer to the log file for details."
print
return 2
stop() {
check

if [ $RUNNING -eq 0 ]
then
print "=================================================================="
print "WARN: $APP_NAME is stopped."
print "=================================================================="
return 1
fi

info
print -n "Stopping $APP_NAME"

if [ $FORCE_KILL -eq 1 ]
then
print -n "..."
print

kill_pid $PID

print "------------------------------------------------------------------"
print "WARN: $APP_NAME was killed by force."
print
return 1

if [ $CHECK_STATUS -eq 0 ]
then
print -n "..."
print
print "------------------------------------------------------------------"
print "WARN: $APP_NAME is stopped without checking status."
print
return 1
fi

local n=0

for ((; n<$CHECK_STATUS_TIMEOUT; n++))
do
if [ $n -lt 3 ]
then
sleep 1
print -n "."
else
check

if [ $RUNNING -eq 0 ]
then
print
print "Done!"
print
return 0
else
sleep 1
fi
fi
done

kill_pid $PID

print
print "------------------------------------------------------------------"
print "WARN: $APP_NAME was killed for stopping timeout."
print
return 1
}

restart() {
check

if [ $RUNNING -eq 1 ]
then
if [ $CHECK_STATUS -eq 0 ]
then
FORCE_KILL=1
fi
stop
fi

start
}

status() {
check

if [ $RUNNING -eq 0 ]
then
print "=================================================================="
print "INFO: $APP_NAME is stopped."
print "=================================================================="
return 0
else
print "=================================================================="
print "INFO: $APP_NAME(PID=$PID) is running."
print "=================================================================="
return 1
fi
}

info() {
if [ $QUIET_MODE -eq 1 ]
then
return
fi

echo "=================================================================="
echo "$APP_NAME Information:"
echo "------------------------------------------------------------------"
echo "JAVA_HOME=$JAVA_HOME"
echo "CLASS_PATH=$CLASS_PATH"
echo
echo `$JAVA_HOME/bin/java -version`
echo "APP_HOME=$APP_HOME"
echo "APP_MAIN_CLASS=$APP_MAIN_CLASS"
echo "=================================================================="
}

check_env

if [ $# -gt 1 ]
then
for v in $@
do
if [ "$v" == "$1" ]
then
continue
fi
case "$v" in
'--quiet')
QUIET_MODE=1
;;
'--nocheck')
CHECK_STATUS=0
;;
'--force')
FORCE_KILL=1
;;
*)
;;
esac
done
fi

case "$1" in
'start')
check_prometheus
start
;;
'stop')
check_prometheus
stop
;;
'restart')
check_prometheus
restart
;;
'status')
status
;;
'info')
info
;;
*)
echo "=================================================================="
echo "Usage: $0 <commands> [options]"
echo "------------------------------------------------------------------"
echo "where commands include:"
echo
echo -e " start [options]"
echo -e " --quiet\twithout console output"
echo -e " --nocheck\twithout checking status"
echo
echo -e " stop [options]"
echo -e " --quiet\twithout console output"
echo -e " --nocheck\twithout checking status"
echo -e " --force\tforce-kill"
echo
echo -e " restart [options]"
echo -e " --quiet\twithout console output"
echo -e " --nocheck\twithout checking status"
echo -e " --force\tstart after force-kill"
echo
echo -e " status \t\tdisplay running status"
echo
echo -e " info \t\tdisplay environment information"
echo "=================================================================="
;;
esac

RET_CODE=`echo $?`

exit $RET_CODE

prometheus监控java程序相关推荐

监控工具—Prometheus—监控Java程序
原文作者:青蛙小白原文地址:Prometheus监控实践:使用Prometheus监控Java应用目录 1.Prometheus JVM Client 2.Prometheus的服务发现 3.Gr ...
Prometheus 监控 Java 应用
Prometheus 监控 Java 应用 Prometheus 监控 Java 应用有两种方式:一种是使用官方提供的jar包,然后嵌入到应用中.这种方式一般都是新项目.我认为也是最合适的一种.不过这 ...
prometheus监控java项目（jvm等）：k8s外、k8s内
前言虽然可以使用jvisualvm之类的工具监控java项目,但是集群环境下,还是捉襟见肘,下面介绍如何用主流的prometheus来监控java项目. java项目配置在pom.xml中添加依赖 ...
使用jvisualvm的jstatd方式远程监控Java程序
使用Java自带的jvisualvm调试Java程序,可以查看CPU.内存.类及线程等信息,还可以进行Dump,无疑是一个利器由于客户端是Windows.服务端是Linux,并且是最小安装的Linu ...
prometheus监控java应用的jvm指标
在k8s环境中我们有很多的java应用,需要监控其性能我们可以通过集成jmx的客户端,然后通过promethues的自动发现来实现监控数据的获取. promethues的部署he相关配置可参考:pro ...
监控工具—Prometheus—监控Redis
原文作者:wyl9527 原文地址:Grafana Prometheus系统监控Redis服务目录 1.下载redis_exporter安装包 2.解压安装 3.systemd管理redis_exp ...
java程序怎么监控错误_Fundebug上线Java程序错误监控啦！
原标题:Fundebug上线Java程序错误监控啦! 摘要: Fundebug竭诚为你的Java程序保驾护航. 理论上讲,BUG是无法避免的,实时监控可以帮助开发者第一时间发现BUG,及时修复BUG, ...
Prometheus监控（kube-prometheus）
Prometheus监控实战(kube-prometheus) 部署kube-prometheus监控套件调试 manifests下用户可以自定义CRD等资源配置增加prometheus监控K8S ...
java 程序架构知识
流程类 Activity 的介绍和使用(一) https://blog.csdn.net/litengit/article/details/51065442 三分钟明白 Activity工作流 -- ...

prometheus监控java程序

前提：

prometheus监控java程序相关推荐

最新文章

热门文章