open-policy-agent / open-policy-agent/java-opa-sdk
Add prepare/compile-path timers
Open
Nobody has claimed this yet.
evaluator
metrics
- Dominant language
- Java
- Stars
- 16
- Forks
- 24
- Avg merge
- 8h 17m
- Merged PRs (30d)
- 15
Description
Engine.java only times the eval side (rego_query_eval, rego_parse_pojo_input, rego_marshal_pojo_results, rego_marshal_raw_results). Users can't attribute startup cost (bundle load, plan parse, prepare).
- Add timers around bundle load, plan parse, and prepare.
- Match Go names where they appear in decision logs so OPA's tooling can read them — e.g.,
rego_query_compile,rego_load_bundles(see https://github.com/open-policy-agent/opa/blob/main/v1/metrics/metrics.go). - Cover with integration tests that assert the timers appear in the metrics map.
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 in Engine.java, where the existing eval timers are defined, and trace bundle loading, plan parsing, and preparation. Compare timer names with the referenced Go metrics names, then add integration coverage that asserts the new timers appear in the metrics map. Done means startup costs are represented with names OPA tooling can read.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100