Document integrity check audit log events
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
Product: Tarantool Enterprise Edition
Since: 3.8.0
Root document: https://www.tarantool.io/en/doc/latest/platform/security/audit_log
NO_WRAP
New audit log events and the corresponding event group introduced:
- Name:
integrity_check_ok
Event: an integrity check has been completed successfully
Event group:integrity_check
Severity:VERBOSE
Example:Integrity check for file /tmp/file.txt succeeded - Name:
integrity_check_fail
Event: an integrity check has failed (for a file or for a data buffer)
Event group:integrity_check
Severity:ALARM
Examples:Integrity check for file /tmp/file.txt failed: hash mismatch, expected: x, got: yIntegrity check for file /tmp/file.txt failed: couldn't open the file
NO_WRAP
Requested by @mkostoevr in https://github.com/tarantool/tarantool-ee/commit/8a39066742261b67254a11f7c5ed474cfc37c145.
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
Open the audit log root document linked in the issue and locate its audit event and event-group reference. Document the integrity_check group and both integrity_check_ok and integrity_check_fail events, including their descriptions, severities, and examples; done means the new entries accurately reflect the requested details.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100