Observability
Observability
Section titled “Observability”sigMAX components should expose operational state by design.
Observability is split into three signals: logs, metrics, and traces. They do not have the same availability in sigMAX Core and sigMAX Enterprise.
Logs explain component and runtime behavior: startup, route execution, validation failures, denied capabilities, runtime errors, and operational events.
In sigMAX Core, logs are not collected by a native Docker logging stack. Local inspection is done directly from the running containers, for example with podman logs.
In sigMAX Enterprise, a Loki collector centralizes logs. Grafana with Loki is then used to search, filter, correlate, and observe those logs across deployed components.
Metrics
Section titled “Metrics”Metrics expose measurable runtime signals such as counters, latency, health indicators, execution duration, error counts, and resource-oriented runtime indicators.
Metrics are not a native Core runtime feature. sigMAX Core remains inspectable locally, but it does not include a built-in metrics pipeline.
sigMAX Enterprise incorporates metrics natively in the runtime. Those metrics are centralized and stored with Thanos, then displayed and explored through Grafana.
Traces
Section titled “Traces”Traces correlate a request path across runtime steps and components. They are useful for understanding distributed calls, latency, and cross-component execution flow.
Tracing is limited to sigMAX Enterprise. The Enterprise observability stack uses Zipkin for trace collection and exploration through the Zipkin interface.
Edition Summary
Section titled “Edition Summary”| Signal | Availability |
|---|---|
| Logs | Local consultation with podman logs. |
| Metrics | Not incorporated natively in the runtime. |
| Traces | Not included. |
| Signal | Availability |
|---|---|
| Logs | Centralized collection with Loki, observed through Grafana Loki. |
| Metrics | Native runtime metrics, centralized and stored with Thanos, displayed in Grafana. |
| Traces | Zipkin-based collection and visualization through the Zipkin interface. |