Logging & Monitoring
Rierino microservices include configurable logging and monitoring capabilities.
Last updated
Installation
Rierino microservices include configurable logging and monitoring capabilities.
Last updated
API gateway and microservice layers include Logback logging capabilities out of box. Alternative logging libraries can also be used, by replacing logback dependency in build.gradle files (or ConfigMap entries), if preferred.
The default deployment includes DEBUG level logging to Console with the following pattern:
The log level can be defined when deploying new services either through the Deployment UI or helm chart parameters.
The logging pattern and the destination (such as rotating files or SIEM platforms) can easily be configured by editing the logback.xml file (or ConfigMap entry) for the required microservices.
In order to display root cause of errors, which are received in "payload.cause" field from runners, gateway logging level should be set to TRACE. Otherwise, the root cause is hidden to avoid information exposure and only a more generic "message" field is available instead.
Rierino uses OpenTelemetry to facilitate monitoring of availability and performance across all platform components. The default deployment has this feature disabled, but it can be enabled by setting the useOTLP helm chart parameters of required services for kubernetes deployments.
OTLP feeds can be consumed by any monitoring platform after this activation and the Rierino Ansible playbooks include an example for deploying SigNoz as well.
Apart from this approach which provides detailed level traceability, it is also possible to use standard kubernetes node and ingress monitoring capabilities as well.
