OpenConext / OpenConext/OpenConext-engineblock
Logging for SBS interrupt/aggregation
Open
Nobody has claimed this yet.
logging
- Dominant language
- PHP
- Stars
- 17
- Forks
- 25
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
[!NOTE]
Waarom doen we dit? Op Wat moet er precies in? Op welke loglevels?
Add logging for SBS callout. The following events should be logged:
- backend interrupt:
- request is sent (+DEBUG: which attributes are sent)
- result of result (whether or not to interrupt)
- interrupt callout is initiated
- users returns from interrupt
- attribute callout
- request is sent
- response from SBS (+DEBUG: full json response)
- which attributes were added/replaced
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
Start by locating the SBS backend-interrupt and attribute-callout entry points, then inspect existing logging conventions and levels. Done means the listed request, result, initiation, return, response, and attribute-change events are logged, with the specified request attributes and full SBS JSON response at DEBUG level.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100