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.

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

Fixes in backup.adoc #201

Merged
merged 1 commit into from
Dec 11, 2020
Merged
Changes from all commits
Commits
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
4 changes: 2 additions & 2 deletions docs/modules/ROOT/pages/backup.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -21,9 +21,9 @@ TIP: You can always check the state and configuration of your backup by using `k

== Checking the Status of Backup Jobs

Every time a job starts, it creates a separate pod in your namespace. You can see them using `kubectl pods`. You can then use the usual `kubectl logs <POD NAME>` command to troubleshoot a failed backup job.
Every time a job starts, it creates a separate pod in your namespace. You can see them using `kubectl get pods`. You can then use the usual `kubectl logs <POD NAME>` command to troubleshoot a failed backup job.

Additionally the operator exposes a `:8080/metrics` endpoint for prometheus scraping. This will give you additional metrics that can be used to find failed jobs. See the [Prometheus examples](https://github.com/vshn/k8up/blob/v0.1.10/manifest/examples/prometheus) in our Github repository.
Additionally the operator exposes a `:8080/metrics` endpoint for prometheus scraping. This will give you additional metrics that can be used to find failed jobs. See the https://github.com/vshn/k8up/blob/v0.1.10/manifest/examples/prometheus[Prometheus examples in our Github repository].

== Application-Aware Backups

Expand Down