Description
Hi Maintainers,
I am currently using Drools v10.2.0 in a Spring Boot microservices architecture and wanted native support for OpenTelemetry instrumentation to improve observability of rule execution.
While OpenTelemetry integration exists for common components (HTTP, JDBC, Kafka, etc.), we could not find any official or community-supported instrumentation for Drools rule execution lifecycle (e.g., KieSession.execute(), rule firing, agenda events).
Since rule evaluation is a critical part of our business logic, the lack of tracing support makes it difficult to:
- Measure rule execution latency
- Identify which rules fired during a request
- Correlate rule behavior with distributed traces
- Debug production issues related to rule evaluation
I would be happy to contribute my implementation if it aligns with the project direction.
Implementation ideas
With respect to Implementing the Feature, I have some steps and Ideas.
- We can have a Single Module with all the Logic to Open-Telemetry Connections.
- After that we can specific modules for integration of Open-Telemetry with Kogito, etc.
- Then we can multiple modules to add support for Quarkus and Spring Boot Libraries as well as add Support for DMN Framework.
Description
Hi Maintainers,
I am currently using Drools v10.2.0 in a Spring Boot microservices architecture and wanted native support for OpenTelemetry instrumentation to improve observability of rule execution.
While OpenTelemetry integration exists for common components (HTTP, JDBC, Kafka, etc.), we could not find any official or community-supported instrumentation for Drools rule execution lifecycle (e.g., KieSession.execute(), rule firing, agenda events).
Since rule evaluation is a critical part of our business logic, the lack of tracing support makes it difficult to:
I would be happy to contribute my implementation if it aligns with the project direction.
Implementation ideas
With respect to Implementing the Feature, I have some steps and Ideas.