Stablish a correlation I between auditors
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 300
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 184
Description
Follow-up idea: since vMCP uses both auditors (HTTP one logs the incoming call, this one logs the workflow internals), it'd be nice to have a correlation ID to tie them together.
Right now you can correlate by user + timestamp + tool name, but an explicit ID would make forensics easier when the same user fires off multiple requests. Maybe propagate X-Request-ID from the HTTP layer in a follow-up?
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 by tracing the vMCP HTTP auditor and the auditor that logs workflow internals, then examine how X-Request-ID could be propagated from the HTTP layer. Done means both audit records for one request share an explicit correlation ID, including when the same user makes multiple requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100