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

Allow instance owners to schedule planned downtime #22

Closed
tn5421 opened this issue Oct 1, 2023 · 2 comments · Fixed by #57
Closed

Allow instance owners to schedule planned downtime #22

tn5421 opened this issue Oct 1, 2023 · 2 comments · Fixed by #57
Labels
💡 idea Needs investigation/research ✅ enhancement New feature or request
Milestone

Comments

@tn5421
Copy link

tn5421 commented Oct 1, 2023

As it stands, this project is very good for detecting unplanned service outages, but there is currently not a way to distinguish between planned and unplanned outages.

@bahmanm bahmanm added 💡 idea Needs investigation/research ✅ enhancement New feature or request labels Oct 1, 2023
@bahmanm bahmanm added this to the v2.0.0 milestone Oct 1, 2023
@bahmanm
Copy link
Owner

bahmanm commented Oct 1, 2023

Thanks 🙏 This is quite a valid requirement. I'll definitely get back to this once v1.0.0 is out.

@bahmanm
Copy link
Owner

bahmanm commented Oct 11, 2023

Two pieces of feedback from the community so far:

  1. There should be a way to declare the downtime w/o requiring a Google account.
    This can be possibly achieved by asking the interested admins to expose their schedule at a predefined URL which can be scraped by lemmy-meter. For example: http://INSTANCE/.well-known/host-metadata.json

  2. Some sites have recurring planned downtime.
    This can be achieved by using the cron syntax to declare such periods.
    💡 In the case of a recurring interval competing w/ a non-recurring one, the latter wins.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💡 idea Needs investigation/research ✅ enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants