-
Notifications
You must be signed in to change notification settings - Fork 91
Labels
comp-jans-cedarlingTouching folder /jans-cedarlingTouching folder /jans-cedarlingenhancementkind-featureIssue or PR is a new feature requestIssue or PR is a new feature request
Milestone
Description
Is your feature request related to a problem? Please describe.
To get single entry from memory logger we need to know ID of entry.
Currently, it is not possible without getting all logs.
Actually we need the way to get decision log exactly.
Describe the solution you'd like
We need to create request_id
per one authorize
request, propagate it to each log entry. And return it in the AuthorizeResult
structure.
Also, we need to improve sparkv
, add index with additional ID for entity and add tag
for entity.
It will allow go get entities per request and filter per tag.
Describe alternatives you've considered
to result structure add ID of log entry that show decision-log
Additional context
- generate request ID per single execution authorize call. And pass it to every log entry.
- currently request_id generate per log entry (because only one log entry use it)
- add to each log entry id and request_id (if was missed)
- add to sparkv possibility to get log entries per request_id and request_id + some tag (in result will be id of log entry or list of ids)
- add to result structure request_id
- and eventually use updated api of memory logger that allows you to extract logs selectively using request_id or request_id + some tag
Metadata
Metadata
Assignees
Labels
comp-jans-cedarlingTouching folder /jans-cedarlingTouching folder /jans-cedarlingenhancementkind-featureIssue or PR is a new feature requestIssue or PR is a new feature request