-
Notifications
You must be signed in to change notification settings - Fork 740
Pass audit log parts from grpc request check actor to monitoring [simple way] #23519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pass audit log parts from grpc request check actor to monitoring [simple way] #23519
Conversation
|
🟢 |
|
⚪ Test history | Ya make output | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
|
⚪ DetailsTest history | Ya make output | Test bloat
⚪ Test history | Ya make output | Test bloat | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
…ple way] (ydb-platform#23519) (cherry picked from commit c30df31)
…ple way] (ydb-platform#23519) (cherry picked from commit c30df31)
Changelog entry
...
Changelog category
Description for reviewers
This PR allows to pass folder_id/cloud_id/resource_id parameters from the actor that performs authentication step to the monitoring subsystem. Then monitoring uses them in audit logging.
I passed audit log parts to monitoring. In the future it should be done in more common way: the same as for request through grpc API: instead of passing audit log parts separately, the request context should be passed. Then this context should be used (as in grpc subsystem) in audit logging directly. It enables to use one audit context filled in one place in both http and grpc.