Monitoring values from prometheus endpoint

Flowable Engine
1

I am building an own flowable image to inject our own JavaDelegate and EventListener.

FROM flowable/flowable-rest

USER root

# Install required system libraries
RUN apk add --no-cache libc6-compat

USER flowable
COPY target/flowable_delegate_and_eventlistener-1.0-SNAPSHOT.jar /app/WEB-INF/lib
COPY logback-spring.xml /app/WEB-INF/classes
COPY mysql-connector-j-8.0.33.jar /app/WEB-INF/lib
COPY micrometer-registry-prometheus-1.12.5.jar /app/WEB-INF/lib
COPY simpleclient-0.16.0.jar /app/WEB-INF/lib
COPY simpleclient_common-0.16.0.jar /app/WEB-INF/lib
COPY simpleclient_hotspot-0.16.0.jar /app/WEB-INF/lib
COPY simpleclient_tracer_common-0.16.0.jar /app/WEB-INF/lib
COPY simpleclient_tracer_otel-0.16.0.jar /app/WEB-INF/lib

i created a docker compose file to start the flowable engine

services:
    flowable-rest:
        build: .
        ports:
            - 8181:8080
            - 5005:5005
        environment:
            - KAFKA_SERVERS=---
            - KAFKA_TOPIC=...
            - KAFKA_GROUP_ID=...
            - MANAGEMENT_PROMETHEUS_METRICS_EXPORT_ENABLED=true
            - MANAGEMENT_ENDPOINTS_WEB_EXPOSURE_INCLUDE=*
            - SPRING_DATASOURCE_URL=jdbc:mysql://...:3306/flowable?characterEncoding=UTF-8
            - SPRING_DATASOURCE_USERNAME=...
            - SPRING_DATASOURCE_PASSWORD=...

I can now reach the endpoint under flowable-rest/actuator/prometheus but there are now interesting flow values like “how many processes are running“, “how many are paused” etc.

I know, that i can get this values f.e. over the /flowable-rest/service/history/historic-process-instances endpoint, but i thought, they are also aggreated over the prometheus endpoint.

Am i missing something on my environment to active this values?

2

Hey @MeAndMyTeam,

For questions like

I would advise you to use the query endpoints. Exposing everything through the metrics is not realistic.

Cheers,
Filip

3

Why are you saying, is it not realistic? In prometheus there are nice metric types like gauge or counter, just for those use cases. With the query of the endpoints i have to stress the service quite more, as if he will give me the parameters in the metrics.