open-policy-agent / open-policy-agent/java-opa-sdk
SLF4J sink for status reports
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 16
- Forks
- 24
- Avg merge
- 8h 17m
- Merged PRs (30d)
- 15
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with StatusPlugin and compare the existing decision-log SLF4J sink described in issue #7. Trace how status reports are currently sent to the console or service uploader, then add the independent logger path and tests for the named logger, expected payload, configurable level, and structured logging support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 57/100