Adding further data collection to pt-k8s-debug-collector
General
Escalation
General
Escalation
Description
Environment
None
Activity
Show:

Aaditya Dubey January 27, 2025 at 10:42 AM
Hi @Pablo Svampa
Thank you for the report and feedback.
Details
Details
Assignee

Reporter

Priority
Components
Fix versions
Needs QA
Yes
Smart Checklist
Open Smart Checklist
Smart Checklist

Open Smart Checklist
Created January 24, 2025 at 7:51 PM
Updated January 27, 2025 at 10:55 AM
Hello team,
The support team struggled a lot with PostgreSQL Operator issues related to the backup and restore process.
We made a sync-up with the engineering team, and we asked what logs would be relevant for them if we need to escalate the problem.
Additionally to the existing data collection we need to collect
Database logs (everything under $PGDATA/logs. Similar to what we would get by performing:
kubectl exec -i cluster1-instance1-xxxx-0 -c database -- bash -c 'tar cz /pgdata/*/log' > cluster1-instance1-xxxx-0.tar
Output of patronictl list. Similar to what we would get by performing:
kubectl exec cluster1-instance1-
xxxx
-0 -c database -i -- bash -c 'patronictl list' > patronictl_list.logpgbackrest container logs
kubectl logs cluster1-instance1-xxxx-0 -c pgbackrest > cluster1-instance1-xxxx-0_pgbackrest_container.log
pgbackrest execution logs
kubectl exec -i cluster1-instance1-xxxx-0 -c pgbackrest -- bash -c 'tar cz /pgdata/pgbackrest/log' > cluster1-instance1-xxxx-0_pgbackrest_execution_logs.tar
pgbackrest info output
kubectl exec cluster1-repo-host-0 -it -c pgbackrest -- bash -c 'pgbackrest info' > pgbackrest_info.out
If you need any additional info, please let us know.
Best regards,