Comments

• 

  almost 6 years ago by lrupp | Reply

  While I'm happy to read that someone wants to start even thinking about a status page, I like to add two comments from my history, as the one who implemented status.opensuse.org:

  • even a somehow generated static page needs to get distributed to multiple locations (and you might want to make sure that your "source of truth" is also high available). Setting up the DB servers on status{1,2}.opensuse.org in a master - master setup was seen as easier task from my side than having an additional GIT (or whatever) source that needs to be available. Just ask yourself: how many times was status.o.o not available? - And would the "static page" generation have helped to avoid this?

  • about "monitoring alerts not going to the status page": as written in their documentation, Cachet has a nice API that can be used for that.

×
Edit Comment 3186
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

* Use asterisks
* for lists

This is an [example link](http://example.com/)

This is an ![example image](http://paste.opensuse.org/view/raw/68957446)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
While I'm happy to read that someone wants to start even thinking about a status page, I like to add two comments from my history, as the one who implemented status.opensuse.org: * even a somehow generated static page needs to get distributed to multiple locations (and you might want to make sure that your "source of truth" is also high available). Setting up the DB servers on status{1,2}.opensuse.org in a master - master setup was seen as easier task from my side than having an additional GIT (or whatever) source that needs to be available. Just ask yourself: how many times was status.o.o not available? - And would the "static page" generation have helped to avoid this? * about "monitoring alerts not going to the status page": as written in their documentation, Cachet has a [nice API](https://docs.cachethq.io/docs/advanced-api-usage) that can be used for that.
 
×
Reply to lrupp
While I'm happy to read that someone wants to start even thinking about a status page, I like to add two comments from my history, as the one who implemented status.opensuse.org:
• even a somehow generated static page needs to get distributed to multiple locations (and you might want to make sure that your "source of truth" is also high available). Setting up the DB servers on status{1,2}.opensuse.org in a master - master setup was seen as easier task from my side than having an additional GIT (or whatever) source that needs to be available. Just ask yourself: how many times was status.o.o not available? - And would the "static page" generation have helped to avoid this?

• about "monitoring alerts not going to the status page": as written in their documentation, Cachet has a nice API that can be used for that.
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

* Use asterisks
* for lists

This is an [example link](http://example.com/)

This is an ![example image](http://paste.opensuse.org/view/raw/68957446)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview