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.

Sign up for GitHub

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

Jump to bottom

Improved K8up operator monitoring #11

Closed
tobru opened this issue May 9, 2019 · 1 comment
Closed

Improved K8up operator monitoring #11

tobru opened this issue May 9, 2019 · 1 comment
Assignees
@Kidswiss

Comments

@tobru
Copy link
Contributor

tobru commented May 9, 2019

Add a lot more of monitoring information to the operator to close the gap.

Operator:

  • global view over all registered backups (how many schedules for example)
  • reports failed successful runs (as in backoff limit was reached/crashed/etc.)
  • could also report how many jobs are queued up due to a blocking prune run
  • with that info it could be possible to find out if a backup job is late

Wrestic:

  • more granular per job info
  • how many file errors, changes, etc (as already implemented)
  • start/end time

refs APPU-1058
@Kidswiss Kidswiss self-assigned this May 29, 2019
@Kidswiss
Copy link
Contributor

Was merged with #60.

Closing the issue.

cimnine pushed a commit that referenced this issue Aug 5, 2021
@Kidswiss
Merge pull request #11 from vshn/catch_signal
c027f61 
Pass signals to the restic process
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Kidswiss Kidswiss

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tobru @Kidswiss