-
Notifications
You must be signed in to change notification settings - Fork 23
K8SPXC-1405 Added a note about the retention policy with PITR #219
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.
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
Conversation
reworked the doc to improve readability
modified: docs/backups-pitr.md
docs/backups-pitr.md
Outdated
* `pxc_binlog_collector_failure_total` - The total number of failed binlog collection cycles. Indicates issues in the binlog collection process, such as connectivity problems or errors during processing | ||
* `pxc_binlog_collector_gap_detected_total` - Tracks the total number of gaps detected in the binlog sequence during collection. Highlights potential issues with missing or skipped binlogs, which could impact replication or recovery. | ||
* `pxc_binlog_collector_last_processing_timestamp` - Records the timestamp of the last successful binlog processing operation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Records the timestamp of the last successful binlog collection operation. During collection operation there can be no binlogs to upload.
docs/backups-pitr.md
Outdated
|
||
## Monitoring binary logs | ||
|
||
The point-in-time recovery Pod collects statistics metrics for binlogs. They provide insights into the success and failure rates of binlog operations, timeliness of processing and uploads and potential gaps or inconsistencies in binlog data. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The point-in-time recovery Pod collects statistics metrics for binlogs -> pod is not collecting info and does not aggregate it, so after pod restart counters will be restarted and will grow until next restart - for example this one pxc_binlog_collector_success_total .
bae8aae
to
e3b1e19
Compare
e3b1e19
to
68a26fd
Compare
68a26fd
to
828f67a
Compare
reworked the doc to improve readability
Added K8SPXC-1405 - Info about Prometheus metrics