Skip to content

Commit c699e1f

Browse files
Update event security logs documentation regarding logging charm operations (#1141)
Signed-off-by: Marcelo Henrique Neppel <marcelo.neppel@canonical.com>
1 parent 936a3c5 commit c699e1f

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

docs/explanation/security/index.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -104,6 +104,8 @@ The following information is configured to be logged:
104104

105105
Other events, like connections and disconnections, are logged depending on the value of the charm configuration options related to them. For more information, check the configuration options with the `logging` prefix in the [configuration reference](https://charmhub.io/postgresql-k8s/configurations#logging_log_connections).
106106

107+
Also, all operations performed by the charm as a result of user actions — such as enabling or disabling plugins, managing TLS, creating or restoring backups, and configuring replication between clusters (asynchronous or logical) — are executed through the underlying workload components (PostgreSQL, Patroni, or pgBackRest). Consequently, these operations are recorded in the respective workload log files, which are accessible in the `/var/log/postgresql` directory and also forwarded to COS.
108+
107109
No secrets are logged.
108110

109111
## Additional Resources

0 commit comments

Comments
 (0)