Skip to content
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.

Sign up for GitHub

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

Small edits to audit-log page #1865

Merged
merged 1 commit into from
Mar 17, 2020
Merged

Small edits to audit-log page #1865

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions app/enterprise/1.3-x/admin-api/audit-log.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ X-Kong-Admin-Request-ID: ZuUfPfnxNn7D2OTU6Xi4zCnQkavzMUNM
}
```

The above interaction with the Admin API would generate a correlating entry in
The above interaction with the Admin API generates a correlating entry in
the audit log table. Querying the audit log via Admin API returns the details of the interaction above:

```
Expand Down Expand Up @@ -192,11 +192,11 @@ The following request paths generate an audit log entry in the database:

### Audit Log Retention

Request audit records ree kept in the database for a duration defined by the
Request audit records are kept in the database for a duration defined by the
`audit_log_record_ttl` [Kong configuration property](https://docs.konghq.com/enterprise/1.3-x/property-reference/#audit_log_record_ttl).
Records in the database older than `audit_log_record_ttl` seconds are automatically
purged. In Cassandra databases, record deletion is handled automatically via the
Cassandra TTL mechanism. In Postgres databases, records are purged via stored
Cassandra TTL mechanism. In Postgres databases, records are purged via the stored
procedure that is executed on insert into the record database. Thus, request
audit records may exist in the database longer than the configured TTL, if no new
records are inserted to the audit table following the expiration timestamp.
Expand Down Expand Up @@ -323,7 +323,7 @@ Database audit records are kept in the database for a duration defined by the
`audit_log_record_ttl` [Kong configuration property](https://docs.konghq.com/enterprise/1.3-x/property-reference/#audit_log_record_ttl).
Records in the database older than `audit_log_record_ttl` seconds are automatically
purged. In Cassandra databases, record deletion is handled automatically via the
Cassandra TTL mechanism. In Postgres databases, records are purged via stored
Cassandra TTL mechanism. In Postgres databases, records are purged via the stored
procedure that is executed on insert into the record database. Thus, database
audit records may exist in the database longer than the configured TTL, if no new
records are inserted to the audit table following the expiration timestamp.
Expand Down