Metrics Overview(4.1)
- Jenni Wallin
In  there are 2 different metric types.
MIMs, to see available MIMs, use the MIM-browser in the workflow, for more information see Administration and Management(4.0).
PrometheusUDRs, used by the Prometheus Agent.
Interactions of Different Metrics
The tables below shows the different methods for collecting metrics.
Metric | Originates from | Special Settings required | Supports Filter Configuration | Exposed Metrics from | Port to Prometheus Examples with standard port | Tool To Display the Metric |
|---|---|---|---|---|---|---|
MIM in Batch | Workflows | No | Yes | EC | http://<node>:9090/metrics | Prometheus or Grafana |
PrometheusUDR | Workflows | Yes, in the workflows. | Yes | EC | http://<node>:9090/metrics | Prometheus or Grafana |
Metrics colllected from workflows
Metric | Interface to Prometheus | Originates from | Special Settings required | Supports Filter Configuration | Exposed Metrics from | Port to Prometheus Examples with standard port | Tool To display the Metric |
|---|---|---|---|---|---|---|---|
MIM in Realtime | Servlet | Workflows | No | Yes | EC | http://<node>:9090/metrics | Prometheus |
JMX Beans | Servlet | Java code | No | Yes | EC | http://<node>:9090/metrics | Prometheus |
JMX Beans | JMX Exporter | Java code | Yes in | No | Platform | http://<node>:9190/metrics | Prometheus |
Metrics collected from all MX beans
Deciding When To Use MIMs or PrometheusUDRs
See the example here: Prometheus Forwarding Agent Example
MIMs have no extra labels which the PrometheusUDRs can have.
MIMs cannot control timed collection of metrics which is possible with PrometheusUDRs.