From dccc5e9864bb8e5923d633848860d39e4d92e46c Mon Sep 17 00:00:00 2001 From: Mantas <11616378+mistermantas@users.noreply.github.com> Date: Thu, 5 Jul 2018 14:45:24 +0300 Subject: v2 Dev Preview 1 --- exampleSite/config.yml | 181 +++++++++++++++++++++ .../issues/unavailable-guilds-connection-issues.md | 24 +++ exampleSite/content/issues/us-east-conn-issues.md | 18 ++ exampleSite/content/stats.html | 4 + 4 files changed, 227 insertions(+) create mode 100644 exampleSite/config.yml create mode 100644 exampleSite/content/issues/unavailable-guilds-connection-issues.md create mode 100644 exampleSite/content/issues/us-east-conn-issues.md create mode 100644 exampleSite/content/stats.html (limited to 'exampleSite') diff --git a/exampleSite/config.yml b/exampleSite/config.yml new file mode 100644 index 0000000..f731012 --- /dev/null +++ b/exampleSite/config.yml @@ -0,0 +1,181 @@ +############################################################ +# +------------------------------------------------------+ # +# | Notes | # +# +------------------------------------------------------+ # +############################################################ + +# Welcome to the cState configuration file! +# +# Hugo is used for building the status page, +# so this file can be used to change how +# your status page should behave or look. +# +# If you want to use special characters, +# such as accented letters, you MUST save +# the file as UTF-8, not ANSI. +# +# If cState does not load, ensure that: +# - No tabs are present; +# YAML only allows spaces +# - Indents are correct +# YAML hierarchy is based entirely on indentation +# - You have "escaped" all apostrophes +# in your text: If you want to write "don't", +# for example, write "don''t" instead! +# Note the doubled apostrophe. +# - Text with symbols is enclosed in single +# or double quotation marks. +# +# If you have problems, create an issue on GitHub: +# https://github.com/mistermantas/cstate/issues + +############################################################ +# +------------------------------------------------------+ # +# | Basic metadata | # +# +------------------------------------------------------+ # +############################################################ + +# What is your status page called? +# Shows up in the browser bar and meta tags +title: Example Chat App Status + +# What language is this page in? +# Only alters the html[lang] attribute +languageCode: en-US + +# What is the hostname or path to the root? +# Where is the site hosted? +# +# Slash enables relative links. +# +# Default: / +# Example: https://status.example.com/ +baseURL: / + +############################################################ +# +------------------------------------------------------+ # +# | Preferences | # +# +------------------------------------------------------+ # +############################################################ + +# 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 + +params: + # These are your systems. Change them to + # change the amount of components. + systems: + #- + # name: Client Area + # codename: panel + #- + # name: Minecraft + # codename: mc + #- + # name: Web Hosting + # codename: web + - Gateway + - API + - Media Proxy + + # What header design should we use? + # Default: true + # BOOLEAN; `true`, `false` + useLargeHeaderDesign: false + + # Should we show the logo or the title + # of the status page? + useLogo: false + + # Where is the logo located, if one is + # present at all? + # + # Recommended: png or jpg for best + # browser support! + # logo: /logo.png + + # This is the description that is shown + # in the footer and meta tags. + description: We continuously monitor the status of our services and if there are any interruptions, a note will be posted here. + + # Cplors throughout cState + # + # Defaults: + # + # brand: #181818 + # ok: 228B22 + # warning: DC143C + # down: FF8C00 + # notice: 708090 + brand: 181818 + ok: 228B22 + disrupted: FF8C00 + down: DC143C + notice: 708090 + border: dfdfdf + faded: ccc + + # If the status page shows that + # there are disruptions or outages + # happening, should it keep the + # brand header color or drop it + # and use the status indication + # colors that were just defined? + # + # Default: true + # BOOLEAN; `true`, `false` + alwaysKeepBrandColor: true + +############################################################ +# +------------------------------------------------------+ # +# | Developer | # +# +------------------------------------------------------+ # +############################################################ + + # Custom CSS file + # If you want to add any + # custom styling, you may + # link to one file with all + # your modifications here. + # + # This has *intentionally* + # been left uncommented, + # as it is not an advanced + # feature for developers. + # + # customCSS: /custom.css + + # Custom JavaScript file + # If you want to add any + # custom scripting, you may + # link to one file with all + # your modifications here. + # + # This has *intentionally* + # been left uncommented, + # as it is not an advanced + # feature for developers. + # + # customJS: /custom.js + +############################################################ +# +------------------------------------------------------+ # +# | For developers | # +# +------------------------------------------------------+ # +############################################################ + +# These options affect the core of cState. +# Please do not change them if you do not +# know what you are doing. +theme: cstate + +# If you are developing locally and want +# to contribute to the cState Git repo, +# please uncomment this option but do not +# forget to re-comment it when +# themesDir: ../.. diff --git a/exampleSite/content/issues/unavailable-guilds-connection-issues.md b/exampleSite/content/issues/unavailable-guilds-connection-issues.md new file mode 100644 index 0000000..eba61b2 --- /dev/null +++ b/exampleSite/content/issues/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 +# 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 new file mode 100644 index 0000000..5431bef --- /dev/null +++ b/exampleSite/content/issues/us-east-conn-issues.md @@ -0,0 +1,18 @@ +--- +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" >}} diff --git a/exampleSite/content/stats.html b/exampleSite/content/stats.html new file mode 100644 index 0000000..d4dd1aa --- /dev/null +++ b/exampleSite/content/stats.html @@ -0,0 +1,4 @@ +--- +title: Uptime +type: uptime +--- -- cgit v1.2.3-70-g09d2