Parallel to #7 (decision-log SLF4J sink). Today StatusPlugin only writes to console (operational logger) or POSTs to a service. Users who route their observability through SLF4J/Logback want status reports as structured log records on a dedicated logger so they flow through the same pipeline as everything else.
- Add an SLF4J sink for status reports (configurable, independent of the service uploader): one log record per report on a dedicated logger name (e.g.
io.github.open_policy_agent.opa.status).
- Marker / structured-args support for Logback's JSON encoder.
- Configurable level (default
INFO).
- Tests: assert reports appear on the named logger with the expected payload.
Parallel to #7 (decision-log SLF4J sink). Today
StatusPluginonly writes to console (operational logger) or POSTs to a service. Users who route their observability through SLF4J/Logback want status reports as structured log records on a dedicated logger so they flow through the same pipeline as everything else.io.github.open_policy_agent.opa.status).INFO).