-
Notifications
You must be signed in to change notification settings - Fork 43
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
[Config] Update 'Audit log' to using a new config #3983
Conversation
e853fc1
to
a696542
Compare
51c1d26
to
559bf9c
Compare
eaf6ff3
to
1904098
Compare
ac90435
to
9e07fff
Compare
b50c05a
to
2ab386d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work! LGTM
doc/code_snippets/snippets/config/instances.enabled/audit_log/myapp.lua
Outdated
Show resolved
Hide resolved
|
||
Specify a pipe for the audit log destination. | ||
You can set the ``pipe`` type using the :ref:`audit_log.to <configuration_reference_audit_to>` option. | ||
If log is a program, its pid is stored in the ``audit_log.logger_pid`` variable. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is audit_log.logger_pid
means audit_log
module (obtained by require('audit_log')
) and its field logger_pid
?
Now it looks very similar to audit_log.to
and others, which are configuration options in this context. Maybe it worth to clarify it here to avoid a confusion.
If the ``audit_log`` string starts with '|', | ||
the string is interpreted as a Unix `pipeline <https://en.wikipedia.org/wiki/Pipeline_%28Unix%29>`_. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A pipeline connected to process'es stdin, I guess?
So, if there is no pipe at start, where the logs will be send?
(These my questions as a reader, I don't remember how it works.)
doc/enterprise/audit_log.rst
Outdated
However, it is not recommended to use the entire memory, as this may cause performance degradation | ||
and even loss of some logs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's an unclear recommendation, because there are no configurable memory limit for the audit log.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No objections from my side. I left several questions to discuss if you like.
97456da
to
83f0975
Compare
* Add `audit_log` config section * Rewrite `Audit log module` page
83f0975
to
849bb3d
Compare
Updated and restructured Audit module page
Added audit_log reference section:
Documented new audit log fields - uuid, severity
Added a new Severity level subsection to Custom events section (with examples)
Fixed typo in the
tt search
descriptionFixes #3667
Fixes https://github.com/tarantool/enterprise_doc/issues/258
Fixes https://github.com/tarantool/enterprise_doc/issues/257
Fixes https://github.com/tarantool/enterprise_doc/issues/221 - also related to 2.11, don't forget to update this in 2.11 branch
Fixes https://github.com/tarantool/enterprise_doc/issues/248