Skip to content

Commit 2a7afc6

Browse files
Update event security logs documentation regarding logging charm operations (#1253)
Signed-off-by: Marcelo Henrique Neppel <marcelo.neppel@canonical.com>
1 parent 6117f30 commit 2a7afc6

File tree

2 files changed

+7
-0
lines changed

2 files changed

+7
-0
lines changed

docs/.custom_wordlist.txt

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -85,6 +85,7 @@ Nextcloud
8585
otf
8686
Parca
8787
Parca's
88+
patroni
8889
Patroni
8990
patronictl
9091
pgAudit

docs/explanation/security/index.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -100,6 +100,12 @@ The following information is configured to be logged:
100100

101101
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/configurations#logging_log_connections).
102102

103+
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 directories below and also forwarded to COS:
104+
105+
* /var/snap/charmed-postgresql/common/var/log/patroni
106+
* /var/snap/charmed-postgresql/common/var/log/pgbackrest
107+
* /var/snap/charmed-postgresql/common/var/log/postgresql
108+
103109
No secrets are logged.
104110

105111
## Additional resources

0 commit comments

Comments
 (0)