使用Promethues堆栈监视可流动部署
目的是使用Prometheus/grafana
install kube-prometheus-stack使用Helm图表来监视在Kubernetes上部署的可流动项目：
helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
helm repo update
helm install prometheus prometheus-community/kube-prometheus-stack
我们能够开始监视Kubernetes群集内的其他资源
成功部署了它， 作为吊舱运行，我想将可流动的POD指标放到Prometheus上，然后登上Dasboard。
关于如何实现可流动应用程序作为豆荚内的吊舱的任何建议
The goal is to monitor the flowable project deployed on Kubernetes using Prometheus/Grafana
Install kube-prometheus-stack using helm charts:
helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
helm repo update
helm install prometheus prometheus-community/kube-prometheus-stack
Its successfully deployed and we are able to start monitoring the other resources inside our Kubernetes cluster using Prometheus/Grafana
Next, Flowable is running as a pod, which I want to get the flowable pod metrics onto Prometheus and come up the dasboard.
Any suggestions on how to achieve the monitoring for a flowable application running as a pod inside kubernetes
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
添加
micrometer-registry-prometheus依赖关系后，流动性（作为春季启动应用程序）使用千分尺，可提供Prometheus格式的指标。然后，端点为执行器/Prometheus。创建自己的Prometheus指标实际上并不困难。您可以创建一个bean实现
flowableEventListener和metricbinder，然后收听FlowableEngineEngineEventTypeprocess_completed增加微米 CODER> CONDER counter>时间一个过程完成。在Bindto（）方法中注册
MeterRegistry的计数器，应该在Prometheus端点上可用。不需要专用的出口舱。Flowable (as a Spring Boot application) uses Micrometer that will provide metrics in prometheus format as soon as you add the
micrometer-registry-prometheusdependency. Endpoint is thenactuator/prometheus.Creating your own prometheus metric is actually not that difficult. You can create a bean implementing
FlowableEventListenerandMetricBinderand then listen to the FlowableEngineEventTypePROCESS_COMPLETEDto increase a micrometerCounterevery time a process gets completed.Register your counter to the
MeterRegistryin the bindTo() method and the metric should be available over the prometheus endpoint. No need for a dedicated exporter pod.