From 4a968698e45ece04b25f41783298b9b397a191a1 Mon Sep 17 00:00:00 2001 From: Mantas <11616378+mistermantas@users.noreply.github.com> Date: Thu, 24 Jan 2019 19:23:35 +0200 Subject: cState is now stable on v3.0 - 2019-01-24 (info: #41) --- exampleSite/README.txt | 3 + exampleSite/config.yml | 99 +++++++++++++--------- .../issues/2018-01-17-sending-dms-impacted.md | 15 ++++ ...8-04-13-unavailable-guilds-connection-issues.md | 24 ++++++ .../issues/2018-05-25-us-east-conn-issues.md | 19 +++++ .../issues/2018-06-13-maintenance-window.md | 13 +++ .../issues/unavailable-guilds-connection-issues.md | 24 ------ exampleSite/content/issues/us-east-conn-issues.md | 18 ---- 8 files changed, 134 insertions(+), 81 deletions(-) create mode 100644 exampleSite/README.txt create mode 100644 exampleSite/content/issues/2018-01-17-sending-dms-impacted.md create mode 100644 exampleSite/content/issues/2018-04-13-unavailable-guilds-connection-issues.md create mode 100644 exampleSite/content/issues/2018-05-25-us-east-conn-issues.md create mode 100644 exampleSite/content/issues/2018-06-13-maintenance-window.md delete mode 100644 exampleSite/content/issues/unavailable-guilds-connection-issues.md delete mode 100644 exampleSite/content/issues/us-east-conn-issues.md (limited to 'exampleSite') diff --git a/exampleSite/README.txt b/exampleSite/README.txt new file mode 100644 index 0000000..4664609 --- /dev/null +++ b/exampleSite/README.txt @@ -0,0 +1,3 @@ +This is the default cState status page website directory/folder. + +https://github.com/cstate/example diff --git a/exampleSite/config.yml b/exampleSite/config.yml index a9558ca..85c5e26 100644 --- a/exampleSite/config.yml +++ b/exampleSite/config.yml @@ -6,9 +6,8 @@ # Welcome to the cState configuration file! # -# This is the configuration file for v2.0! # If you are using an earlier version, or one -# in the future, such as v3, you may see errors +# in the future, such as v8.0 you may see errors # pop up when deploying a cState website. # # Now, onto the fun part. @@ -44,24 +43,54 @@ # What is your status page called? # Shows up in the browser bar and meta tags -title: Eggsample App Status +title: Eggsample Status -# What language is this site using? -# Only alters the html[lang] attribute +# Should posts, which have a publish date +# from the future, be built? Useful for +# sharing upcoming maintenance, etc. +# +# We recommend to keep this at `true`. +# BOOLEAN; `true`, `false` +buildFuture: true + +# What language do you want to use for the +# html[lang] definition? # +# Does not change language of site +# itself. +# +# Default: `en` # ISO 639-1 defines abbreviations. +# # See: https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes # Also: https://www.w3schools.com/tags/ref_language_codes.asp languageCode: en +# What translation file should cState use? +# You can also define whether missing +# translations should get placeholders. +# +# For defaultContentLanguage— +# Default: `en` +# +# For enableMissingTranslationPlaceholders— +# do not set it to true for languages other +# than English! When tested with Lithuanian, +# it would add unnecesary placeholders to +# values that were intentionally empty. +defaultContentLanguage: en + # What is the hostname or path to the root? # Where is the site hosted? # -# Slash enables relative links. +# 💥 cState & Hugo don’t support / in +# production use. It will break RSS +# feeds and breaks permalinks since +# version 3. If you are just testing, +# localhost should automatically work. # -# Default: / # Example: https://status.example.com/ -baseURL: / +baseURL: https://status.example.com ############################################################ # +------------------------------------------------------+ # @@ -76,15 +105,24 @@ params: # For help, see the wiki: # https://github.com/cstate/cstate/wiki/Customization systems: - - - name: Gateway - - - name: API + - name: Gateway + - name: API description: The guts of the application. - - - name: Media Proxy + - name: Media Proxy description: This is the service responsible for serving images, audio, and video. It is reliant on our CDN. + # What date format to use? + # + # Hugo formatting docs: + # https://gohugo.io/functions/format/#hugo-date-and-time-templating-reference + # + # Technical: GOLANG/HUGO .Date.Format & dateFormat + # + # dateFormat Default: "January 2, 2006 at 3:04 PM" + # shortDateFormat Default: "15:04 — Jan 2" + dateFormat: January 2, 2006 at 3:04 PM + shortDateFormat: 15:04 — Jan 2 + # What header design should we use? # # Default: true @@ -109,7 +147,7 @@ params: logo: /logo.png # This is the description that is shown - # in the footer and meta tags. + # on the footer and meta tags. # # Default: We continuously monitor the status of our services and if there are any interruptions, a note will be posted here. description: We continuously monitor the status of our services and if there are any interruptions, a note will be posted here. @@ -146,12 +184,12 @@ params: # # brand: #181818 # ok: 228B22 - # warning: DC143C - # down: FF8C00 + # warning: EE7600 + # down: DC143C # notice: 708090 brand: 181818 ok: 228B22 - disrupted: FF8C00 + disrupted: EE7600 down: DC143C notice: 708090 @@ -181,29 +219,12 @@ params: # Default: UA-00000000-1 googleAnalytics: UA-00000000-1 -############################################################ -# +------------------------------------------------------+ # -# | For developers | # -# +------------------------------------------------------+ # -############################################################ - -# Should posts, which have a publish date -# from the future, be built? Useful for -# sharing upcoming maintenance, etc. -# -# We recommend to keep this at `true`. -# BOOLEAN; `true`, `false` -buildFuture: true - # These options affect the core of cState. # Please do not change them if you do not # know what you are doing. theme: cstate -# This option tells cState what version -# your config file is using. -# -# Never ever remove this, nor change it, -# if you have not updated to any other -# version. -version: 2 +preserveTaxonomyNames: true + +taxonomies: + affected: affected diff --git a/exampleSite/content/issues/2018-01-17-sending-dms-impacted.md b/exampleSite/content/issues/2018-01-17-sending-dms-impacted.md new file mode 100644 index 0000000..0af6136 --- /dev/null +++ b/exampleSite/content/issues/2018-01-17-sending-dms-impacted.md @@ -0,0 +1,15 @@ +--- +title: Issues Sending DMs +date: 2018-01-17 16:24:00 +resolved: true +resolvedWhen: 2018-01-17 16:58:00 +# Possible severity levels: down, disrupted, notice +severity: disrupted +affected: + - API +section: issue +--- + +*Update* - This incident has been resolved. + +*Investigating* - We're aware of an issue affecting sending DMs and viewing online friends. We're online and working on a resolution. diff --git a/exampleSite/content/issues/2018-04-13-unavailable-guilds-connection-issues.md b/exampleSite/content/issues/2018-04-13-unavailable-guilds-connection-issues.md new file mode 100644 index 0000000..a5213d1 --- /dev/null +++ b/exampleSite/content/issues/2018-04-13-unavailable-guilds-connection-issues.md @@ -0,0 +1,24 @@ +--- +title: Unavailable Guilds & Connection Issues +date: 2018-04-13 15:54:00 +resolved: true +resolvedWhen: 2018-04-13 17:30:00 +# Possible severity levels: down, disrupted, notice +severity: down +affected: + - API +section: issue +--- + +*Post-mortem* + +At approximately 14:01, a Redis instance acting as the primary for a highly-available cluster used by our API services was migrated automatically by Google’s Cloud Platform. This migration caused the node to incorrectly drop offline, forcing the cluster to rebalance and trigger known issues with the way our API instances handle Redis failover. After resolving this partial outage, unnoticed issues on other services caused a cascading failure through Example Chat App’s real time system. These issues caused enough critical impact that Example Chat App’s engineering team was forced to fully restart the service, reconnecting millions of clients over a period of 20 minutes. + + +--- + +*Update* - A fix has been implemented and we are monitoring the results. Looks like this has been fixed. {{< track "2018-04-13 17:30:00" >}} + +*Monitoring* - After hitting the ole reboot button Example Chat App is now recovering. We're going to continue to monitor as everyone reconnects. {{< track "2018-04-13 16:50:00" >}} + +*Investigating* - We're aware of users experiencing unavailable guilds and issues when attempting to connect. We're currently investigating. {{< track "2018-04-13 15:54:00" >}} diff --git a/exampleSite/content/issues/2018-05-25-us-east-conn-issues.md b/exampleSite/content/issues/2018-05-25-us-east-conn-issues.md new file mode 100644 index 0000000..96c228c --- /dev/null +++ b/exampleSite/content/issues/2018-05-25-us-east-conn-issues.md @@ -0,0 +1,19 @@ +--- +title: US East Connection Issues +date: 2018-05-25 04:13:00 +resolved: true +resolvedWhen: 2018-05-25 04:13:59 +# Possible severity levels: down, disrupted, notice +severity: disrupted +affected: + - API + - Media Proxy +section: issue +--- + +*Resolved* - +We believe all users experiencing issues have been able to connect at this time. {{< track "2018-05-25 05:54:00" >}} + +*Monitoring* - We believe the connectivity issues are being caused by an isolated ISP issue. We've had reports that swapping to Google DNS servers (see here; https://developers.google.com/speed/public-dns/docs/using) resolves the problem for users. {{< track "2018-05-25 04:40:00" >}} + +*Investigating* - We're aware of reports that users are experiencing connection issues on the East coast of the United States. We're currently investigating these issues, and apologize for any inconvenience it may be causing you. {{< track "2018-05-25 04:13:00" >}} diff --git a/exampleSite/content/issues/2018-06-13-maintenance-window.md b/exampleSite/content/issues/2018-06-13-maintenance-window.md new file mode 100644 index 0000000..e21ae4d --- /dev/null +++ b/exampleSite/content/issues/2018-06-13-maintenance-window.md @@ -0,0 +1,13 @@ +--- +title: Maintenance Window +date: 2018-06-13 15:54:00 +resolved: false +resolvedWhen: 2018-06-13 17:30:00 +# Possible severity levels: down, disrupted, notice +severity: notice +affected: + - API +section: issue +--- + +*Just began* - We're currently shutting down the network. {{< track "2018-06-13 15:54:00" >}} diff --git a/exampleSite/content/issues/unavailable-guilds-connection-issues.md b/exampleSite/content/issues/unavailable-guilds-connection-issues.md deleted file mode 100644 index 327c017..0000000 --- a/exampleSite/content/issues/unavailable-guilds-connection-issues.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Unavailable Guilds & Connection Issues -date: 2018-04-13 15:54:00 -resolved: true -resolvedWhen: 2018-04-13 17:30:00 -# down, disrupted, notice -severity: down -affected: - - API -section: issue ---- - -*Post-mortem* - -At approximately 14:01, a Redis instance acting as the primary for a highly-available cluster used by our API services was migrated automatically by Google’s Cloud Platform. This migration caused the node to incorrectly drop offline, forcing the cluster to rebalance and trigger known issues with the way our API instances handle Redis failover. After resolving this partial outage, unnoticed issues on other services caused a cascading failure through Example Chat App’s real time system. These issues caused enough critical impact that Example Chat App’s engineering team was forced to fully restart the service, reconnecting millions of clients over a period of 20 minutes. - - ---- - -*Update* - A fix has been implemented and we are monitoring the results. Looks like this has been fixed. {{< track "2018-04-13 17:30:00" >}} - -*Monitoring* - After hitting the ole reboot button Example Chat App is now recovering. We're going to continue to monitor as everyone reconnects. {{< track "2018-04-13 16:50:00" >}} - -*Investigating* - We're aware of users experiencing unavailable guilds and issues when attempting to connect. We're currently investigating. {{< track "2018-04-13 15:54:00" >}} diff --git a/exampleSite/content/issues/us-east-conn-issues.md b/exampleSite/content/issues/us-east-conn-issues.md deleted file mode 100644 index 3f19c0b..0000000 --- a/exampleSite/content/issues/us-east-conn-issues.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: US East Connection Issues -date: 2018-05-25 04:13:00 -resolved: true -resolvedWhen: 2018-05-25 04:40:00 -# down, disrupted, notice -severity: disrupted -affected: - - API -section: issue ---- - -*Resolved* - -We believe all users experiencing issues have been able to connect at this time. {{< track "2018-05-25 05:54:00" >}} - -*Monitoring* - We believe the connectivity issues are being caused by an isolated ISP issue. We've had reports that swapping to Google DNS servers (see here; https://developers.google.com/speed/public-dns/docs/using) resolves the problem for users. {{< track "2018-05-25 04:40:00" >}} - -*Investigating* - We're aware of reports that users are experiencing connection issues on the East coast of the United States. We're currently investigating these issues, and apologize for any inconvenience it may be causing you. {{< track "2018-05-25 04:13:00" >}} -- cgit v1.2.3-70-g09d2