Open ricardozanini opened 5 months ago
We decided to modify the scope for this issue so that the operator only creates a service monitor for workflows deployed as k8s deployments. A separate issue has been created to track the work for workflows deployed as Knative services: https://github.com/apache/incubator-kie-kogito-serverless-operator/issues/550
Description
The operator can track in the cluster if Prometheus Operator is installed. If this condition is true and the
SonataFlowPlatform
is marked with.spec.monitoring: true
, then each workflow instance can have aServiceMonitor
object bound to it.Implementation ideas
Each
SonataFlow
already exposes aService
. Hence, in this issue, it's expected that eachServiceMonitor
instance binds to it.Verify with
kogito-runtimes
the endpoints to scrap for metrics (should be/metrics
).Prereqs
Prometheus
CR is already deployed and configured in the cluster. The operator won't provision a Prometheus server.