Submit traces from Policies
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 71
- Forks
- 111
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 110
Description
Problem
When a Guardrail blocks a request, the user should be able to see the traces of what happened. It should include the input for the Guardrail and the reasons for the block, which guardrail.
Proposed Solution
Any policy can publish traces. This should be possible from Policy Engine. Each Policy can maintain a system config to determine whether to publish data or not.
Alternatives
No response
Version
No response
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are identified in the issue. Start by locating the Policy Engine and how policies and system configuration are represented. Clarify the trace format, the guardrail input and block reasons to expose, and the configuration behavior before implementation; done means policies can publish these traces when enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100