netlify / netlify-statuskit Goto Github PK

View Code? Open in Web Editor NEW

240.0 24.0 41.0 45.29 MB

Netlify StatusKit is a template to deploy your own Status pages on Netlify.

Home Page: https://www.netlify.com/status-pages/

License: MIT License

JavaScript 36.07% HTML 38.20% CSS 25.73%

netlify hugo jamstack statuspage status-dashboard incident

netlify-statuskit's Introduction

Introduction

Netlify StatusKit is a template to deploy your own Status pages on Netlify.

Netlify StatusKit is released under the MIT License. Please make sure you understand its implications and guarantees.

Project Status

This project is no longer being maintained by netlify staff. This is a community led project and if you are looking to support this project, please get in touch via an issue.

Netlify's Statement

[Netlify] doesn't currently have the staff to process such contributions.

Initial configuration

Click in the Deploy to Netlify button above to create your own site directly and push this repository to your own account. Before creating the site, Netlify will ask you to fill required environment variables listed here:

STATUSKIT_PAGE_TITLE - Title to show in the browser for your status site.
STATUSKIT_COMPANY_LOGO - URL to your company's logo.
STATUSKIT_SUPPORT_CONTACT_LINK - URL to a support page for your users to talk with you.
STATUSKIT_RESOURCES_LINK - URL to documentation for your users.

Extra configuration

After the site is created, you can modify the code as much as you want and push it to your GitHub repository. Netlify will pick up changes from there.

Reporting systems

You can add systems you want to report about to your Status page. For instance, you might want to tell your users about a status change in your CDN infrastructure but not in your API.

Go to site/config.toml and change the global systems variables. Once that's done, you'll be able to change the status of each one of those systems individually when you open or modify an incident.

Full customization

This template is based in Netlify's Victor-Hugo boilerplate. To work on it you'll need NPM installed. To download dependencies type npm run dependencies, that will check if you have Hugo installed and will download it for you if you don't. It will also run npm install for the first time to download extra dependencies. After that, you can run npm install every time you want to install packages.

Managing incidents

Incidents are plain markdown files inside the site/content/incidents directory.

Creating new incidents

Adding incidents to your status page is as simple as adding a new document to the incidents collection. Create a new incident using npm:

npm run new-incident

You'll be asked a series of questions about the incident, then Hugo will generate a new file pre-filled with your responses.

After explaining the current situation in the incident, you can just push the file to GitHub. Netlify will deploy the indicent announcement for you in a matter of seconds.

Resolving incidents

Everything will be operational again when all incidents are marked with resolved = true in the incident frontMatter:

+++
...
affectedsystems = ["API"]
resolved = true
+++

Tracking activity

When there is an update in your incident you can track activity by inserting a timestamp with the update. For example:

**Update**: We've identified the issue. {{< track "2016-11-22T14:34:00.000Z" >}}

Development

Netlify StatusKit uses NPM to manage dependencies. It also bundles a version of Hugo to work out of the box.

Use npm install to download dependencies.
Use npm start to start the development server.

netlify-statuskit's People

Contributors

Stargazers

Watchers

netlify-statuskit's Issues

Multiple Active Incidents

- Do you want to request a feature or report a bug?
bug
- What is the current behavior?
duplication of ✅ Up and running
- If the current behavior is a bug, please provide the steps to reproduce.
Create multiple unresolved incidents
- What is the expected behavior?
Only the systems that are affected change and there is no duplication.

Should we add learning reviews section?

- Do you want to request a feature or report a bug?

This is a new feature that I'm wondering about.

- What is the current behavior?

After an incident, we organize a learning review and put the outcome in a blog post. We usually update the incident with the link to this blog post.

- What is the expected behavior?

I'm wondering if it'd be more useful to add a learning reviews section to write those outcomes here.

Add incident duration

- Do you want to request a feature or report a bug?

This is a new feature.

- What is the current behavior?

There is no way to know how long an incident was open for.

- If the current behavior is a bug, please provide the steps to reproduce.

- What is the expected behavior?

People should be able to display the incident duration. There are two alternatives:

Add a new parameter to the frontMatter, for instance duration.
Replace the boolean resolved with a date resolvedAt and compare it with the opening date. Use the resulting duration to display that information with each incident.

Add external metrics and graphs

- Do you want to request a feature or report a bug?

This is a new feature.

- What is the current behavior?

There are no metrics or a way to create pretty graphs from external metrics 😿

- If the current behavior is a bug, please provide the steps to reproduce.

- What is the expected behavior?

People should be able to give a set of metrics endpoints and configuration and we should put them in the landing page and a dedicated /metrics/ page.

Update dependencies, fix vulnerabilities

npm install shows a lot of outdated/vulnerable packages:

351 vulnerabilities found [7166 packages audited]
    Severity: 281 low | 40 moderate | 29 high | 1 critical

Incident Content missing in archetype incident.md

I tried to open new incident however i did successfully able to create new incident but i got stuck in incident content i tried finding out in archetype file but it don't have any content variable to define. Then i tried checking views files and found the the variable used in incident html template for description is {{- .Content -}} however i don't know why it didn't worked.

Deploy failed

4:45:09 PM: Build ready to start
4:45:11 PM: build-image version: 9e0f207a27642d0115b1ca97cd5e8cebbe492f63
4:45:11 PM: build-image tag: v3.3.2
4:45:11 PM: buildbot version: 75cd99f62ada9e21edea53208e8baf0eab85a045
4:45:11 PM: Fetching cached dependencies
4:45:11 PM: Failed to fetch cache, continuing with build
4:45:11 PM: Starting to prepare the repo for build
4:45:12 PM: No cached dependencies found. Cloning fresh repo
4:45:12 PM: git clone https://github.com/netlify/netlify-statuskit
4:45:15 PM: Preparing Git Reference refs/heads/master
4:45:15 PM: Found netlify.toml. Overriding site configuration
4:45:15 PM: Starting build script
4:45:15 PM: Installing dependencies
4:45:17 PM: v10.15.3 is already installed.
4:45:18 PM: Now using node v10.15.3 (npm v6.4.1)
4:45:18 PM: Attempting ruby version 2.6.2, read from environment
4:45:19 PM: Using ruby version 2.6.2
4:45:20 PM: Using PHP version 5.6
4:45:20 PM: Started restoring cached node modules
4:45:20 PM: Finished restoring cached node modules
4:45:20 PM: Started restoring cached yarn cache
4:45:20 PM: Finished restoring cached yarn cache
4:45:20 PM: Installing yarn at version 1.13.0
4:45:20 PM: Installing Yarn!
4:45:20 PM: > Downloading tarball...
4:45:20 PM: [1/2]: https://yarnpkg.com/downloads/1.13.0/yarn-v1.1
4:45:20 PM: 3.0.tar.gz --> /tmp/yarn.tar.gz.BMbcDhm7gs
4:45:20 PM:   % Total    % Received % Xferd  Average Speed   Tim
4:45:20 PM: e    Time     Time  Current
4:45:20 PM:                                  Dload  Upload   Total   Spent    Left  Speed
4:45:20 PM: 
  0     0    0
4:45:20 PM:    0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
4:45:20 PM: 
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:
4:45:20 PM: --     0
4:45:20 PM: 
100    93  100    93    0     0    329      0 --:--:-- --:--:-- --:--:--   328
4:45:21 PM: 
100   609    0   609    0     0    894      0 --:--:-- --:--:--
4:45:21 PM:  --:--:--   894
4:45:21 PM: 
100 1142k  100 1142k    0     0  1051k      0  0:00:01
4:45:21 PM:  0:00:01 --:--:-- 1051k
4:45:21 PM: [2/2]: https://yarnpkg.com/downloads/1.
4:45:21 PM: 13.0/yarn-v1.13.0.tar.gz.asc --> /tmp/yarn.tar.gz.BMbcDhm7gs.asc
4:45:21 PM: 
100    97  100    97    0     0   2123      0 --:--:-- --:--:-- --:--:--
4:45:21 PM: 2123
4:45:21 PM: 
  0     0    0     0    0     0      0      0 --:--:-
4:45:21 PM: - --:--:-- --:--:--     0
100   613    0   613    0     0   3709      0
4:45:21 PM:  --:--:-- --:--:-- --:--:--  598k
4:45:21 PM: 
100   832  100   832    0     0   4026      0 --:--:-- -
4:45:21 PM: -:--:-- --:--:--  4026
4:45:21 PM: > Verifying integrity...
4:45:21 PM: gpg: Signature made Tue 18 Dec 2018 04:04:55 PM UTC using RSA key ID B6FF4DE3
4:45:21 PM: gpg: Good signature from "Yarn Packaging <[email protected]>"
4:45:21 PM: gpg: Note: This key has expired!
4:45:21 PM: Primary key fingerprint: 72EC F46A 56B4 AD39 C907  BBB7 1646 B01B 86E5 0310
4:45:21 PM:      Subkey fingerprint: E219 30C4 D0A4 AA46 1858  1F7A E074 D16E B6FF 4DE3
4:45:21 PM: > GPG signature looks good
4:45:21 PM: > Extracting to ~/.yarn...
4:45:21 PM: > Adding to $PATH...
4:45:21 PM: > We've added the following to your /opt/buildhome/.profile
4:45:21 PM: > If this isn't the profile of your current shell then please add the following to your correct profile:
4:45:21 PM: export PATH="$HOME/.yarn/bin:$HOME/.config/yarn/global/node_modules/.bin:$PATH"
4:45:21 PM: 
4:45:22 PM: > Successfully installed Yarn 1.13.0! Please open another terminal where the `yarn` command will now be available.
4:45:22 PM: Installing NPM modules using Yarn version 1.13.0
4:45:23 PM: yarn install v1.13.0
4:45:23 PM: warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
4:45:23 PM: [1/4] Resolving packages...
4:45:24 PM: [2/4] Fetching packages...
4:45:36 PM: info [email protected]: The platform "linux" is incompatible with this module.
4:45:36 PM: info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
4:45:36 PM: [3/4] Linking dependencies...
4:45:36 PM: warning " > [email protected]" has unmet peer dependency "babel-core@^6.0.0".
4:45:40 PM: [4/4] Building fresh packages...
4:45:40 PM: success Saved lockfile.
4:45:40 PM: Done in 17.40s.
4:45:40 PM: NPM modules installed using Yarn
4:45:41 PM: Started restoring cached go cache
4:45:41 PM: Finished restoring cached go cache
4:45:41 PM: unset GOOS;
4:45:41 PM: unset GOARCH;
4:45:41 PM: export GOROOT='/opt/buildhome/.gimme/versions/go1.12.linux.amd64';
4:45:41 PM: export PATH="/opt/buildhome/.gimme/versions/go1.12.linux.amd64/bin:${PATH}";
4:45:41 PM: go version >&2;
4:45:41 PM: export GIMME_ENV='/opt/buildhome/.gimme/env/go1.12.linux.amd64.env';
4:45:41 PM: go version go1.12 linux/amd64
4:45:41 PM: Installing missing commands
4:45:41 PM: Verify run directory
4:45:41 PM: Executing user command: npm run build
4:45:41 PM: > [email protected] build /opt/build/repo
4:45:41 PM: > gulp build
4:45:42 PM: [09:45:42]
4:45:42 PM: Requiring external module babel-register
4:45:42 PM: gulp[1306]: ../src/node_contextify.cc:626:static void node::contextify::ContextifyScript::New(const v8::FunctionCallbackInfo<v8::Value>&): Assertion `args[1]->IsString()' failed.
4:45:42 PM:  1: 0x8dc510 node::Abort() [gulp]
4:45:42 PM:  2: 0x8dc5e5  [gulp]
4:45:42 PM:  3: 0x91081e node::contextify::ContextifyScript::New(v8::FunctionCallbackInfo<v8::Value> const&) [gulp]
4:45:42 PM:  4: 0xb6166b  [gulp]
4:45:42 PM:  5: 0xb63602 v8::internal::Builtin_HandleApiCall(int, v8::internal::Object**, v8::internal::Isolate*) [gulp]
4:45:42 PM:  6: 0x364db845be1d
4:45:42 PM: Aborted (core dumped)
4:45:42 PM: npm
4:45:42 PM:  ERR! code ELIFECYCLE
4:45:44 PM: failed during stage 'building site': Build script returned non-zero exit code: 134
4:45:42 PM: npm
4:45:45 PM: Shutting down logging, 33 messages pending

Favicon not changing to -ok status

Hello everyone,

I am currently experiencing the following bug:

I updated the favicons in the static folder and linked them in the config. Afterwards, I created a new incident (degraded performance) and the favicon changed to -warning. I resolved the issue but the favicon doesn't change to the -ok one. (Every incident has resolved set to true)

I would guess the issue has to lay somewhere in here:

{{ $active := where $incidents "Params.resolved" "!=" true }}

{{ if $major }}
      <link rel="icon" href="{{ absURL $favicons }}favicon-danger.ico">
    {{ else if $active }}
      <link rel="icon" href="{{ absURL $favicons }}favicon-warning.ico">
    {{ else }}
      <link rel="icon" href="{{ absURL $favicons }}favicon.ico">

If I output $active it says Pages(1). To further investigate I deleted every incident.md and it changed to Pages(0) and the favicon changed as well. When I readd the .md's the favicon changes to warning again.

Here's the live example: https://status.graphcms.com/

What could be the problem here? Any suggestions?

UptimeRobot integration

- Do you want to request a feature or report a bug?
Feature
- What is the current behavior?
Have to manually update status page when server goes down, DDoS attack etc...
- If the current behavior is a bug, please provide the steps to reproduce.
N/a
- What is the expected behavior?
Would like to see some integration with UptimeRobot (using their API) to automatically create incidents/update the statuspage and leave us to fill in the blanks (investigating etc...)
- Please mention your node.js, and operating system version.
N/a

Fail wail deploying

8:07:19 PM: Build ready to start
8:07:21 PM: Fetching cached dependencies
8:07:22 PM: Starting to download cache of 136.3MB
8:07:22 PM: Finished downloading cache in 789.099448ms
8:07:22 PM: Starting to extract cache
8:07:27 PM: Finished extracting cache in 4.456520615s
8:07:27 PM: Finished fetching cache in 5.372445741s
8:07:27 PM: Starting to prepare the repo for build
8:07:27 PM: Preparing Git Reference refs/heads/master
8:07:28 PM: Found netlify.toml. Overriding site configuration
8:07:28 PM: Running build command: npm run build
8:07:28 PM: Installing dependencies
8:07:31 PM: v6.12.2 is already installed.
8:07:32 PM: Now using node v6.12.2 (npm v3.10.10)
8:07:32 PM: Using version v6.12.2 of node
8:07:33 PM: Using /opt/buildhome/.rvm/gems/ruby-2.1.2
8:07:33 PM: mv: cannot move ‘/opt/build/cache/.yarn_cache’ to ‘/opt/build/.yarn_cache’
8:07:33 PM: : Permission denied
8:07:33 PM: Installing NPM modules using Yarn version 0.18.1
8:07:34 PM: yarn install v0.18.1
8:07:34 PM: error An unexpected error occurred: "EACCES: permission denied, mkdir '/opt/build/.yarn_cache'".
8:07:34 PM: info If you think this is a bug, please open a bug report with the information provided in "/opt/build/repo/yarn-error.log".
8:07:34 PM: info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
8:07:34 PM: Error during Yarn install
8:07:34 PM: Build complete: exit code: 1
8:07:34 PM: Error running command: Build script returned non-zero exit code: 1
8:07:34 PM: Failing build: Failed to build site
8:07:34 PM: failed during stage 'building site': Build script returned non-zero exit code: 1
8:07:34 PM: Finished processing build request in 13.605933973

I am trying to create a 404 page i have it right but its failing!

Deploying failing

10:05:59 PM: Build ready to start
10:06:02 PM: build-image version: 9e0f207a27642d0115b1ca97cd5e8cebbe492f63
10:06:02 PM: build-image tag: v3.3.2
10:06:02 PM: buildbot version: 75cd99f62ada9e21edea53208e8baf0eab85a045
10:06:03 PM: Fetching cached dependencies
10:06:03 PM: Failed to fetch cache, continuing with build
10:06:03 PM: Starting to prepare the repo for build
10:06:04 PM: No cached dependencies found. Cloning fresh repo
10:06:04 PM: git clone https://github.com/netlify/netlify-statuskit
10:06:07 PM: Preparing Git Reference refs/heads/master
10:06:07 PM: Found netlify.toml. Overriding site configuration
10:06:07 PM: Starting build script
10:06:07 PM: Installing dependencies
10:06:09 PM: v10.15.3 is already installed.
10:06:10 PM: Now using node v10.15.3 (npm v6.4.1)
10:06:10 PM: Attempting ruby version 2.6.2, read from environment
10:06:11 PM: Using ruby version 2.6.2
10:06:11 PM: Using PHP version 5.6
10:06:11 PM: Started restoring cached node modules
10:06:11 PM: Finished restoring cached node modules
10:06:11 PM: Started restoring cached yarn cache
10:06:11 PM: Finished restoring cached yarn cache
10:06:11 PM: Installing yarn at version 1.13.0
10:06:11 PM: Installing Yarn!
10:06:11 PM: > Downloading tarball...
10:06:11 PM: [1/2]: https://yarnpkg.com
10:06:11 PM: /downloads/1.13.0/yarn-v1.13.0.tar.gz --> /tmp/yarn.tar.gz.LWPuiNtVbX
10:06:11 PM: % Total % Received
10:06:11 PM: % Xferd Average Speed Time Time Time Current
10:06:11 PM: Dload Upload Total
10:06:11 PM: Spent Left Speed
10:06:11 PM:
0 0 0 0
10:06:11 PM: 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
10:06:12 PM:
100 93 100 93 0 0 374 0
10:06:12 PM: --:--:-- --:--:-- --:--:-- 375
10:06:12 PM:
100 609 0 609 0 0 995 0 --:--:-- --:--:-- --:
10:06:12 PM: --:-- 995
10:06:12 PM:
0 0 0 0 0 0 0 0 --
10:06:12 PM: :--:-- --:--:-- --:--:-- 0
10:06:13 PM:
100 1142k 100 1142k 0 0
10:06:13 PM: 1116k 0 0:00:01 0:00:01 --:--:-- 6108k
10:06:13 PM: [2/2]: https://yar
10:06:13 PM: npkg.com/downloads/1.13.0/yarn-v1.13.0.tar.gz.asc --> /tmp/yarn.tar.gz.LWPuiNtVbX.a
10:06:13 PM: sc
10:06:13 PM:
100 97 100 97 0 0
10:06:13 PM: 2223 0 --:--:-- --:--:-- --:--:-- 2223
10:06:13 PM:
100 613 0 613 0 0 4608 0 --:--:-- --:--:-- -
10:06:13 PM: -:--:-- 4608
10:06:13 PM:
100 832 100 832 0 0 4919 0 --:--:-
10:06:13 PM: - --:--:-- --:--:-- 4919
10:06:13 PM: > Verifying integrity...
10:06:13 PM: gpg: Signature made Tue 18 Dec 2018 04:04:55 PM UTC using RSA key ID B6FF4DE3
10:06:13 PM: gpg: Good signature from "Yarn Packaging [email protected]"
10:06:13 PM: gpg: Note: This key has expired!
10:06:13 PM: Primary key fingerprint:
10:06:13 PM: 72EC F46A 56B4 AD39 C907 BBB7 1646 B01B 86E5 0310
10:06:13 PM: Subkey fingerprint: E219 30C4 D0A4 AA46 1858 1F7A E074 D16E B6FF 4DE3
10:06:13 PM: > GPG signature looks good
10:06:13 PM: > Extracting to ~/.yarn...
10:06:13 PM: > Adding to $PATH...
10:06:13 PM: > We've added the following to your /opt/buildhome/.profile
10:06:13 PM: > If this isn't the profile of your current shell then please add the following to your correct profile:
10:06:13 PM: export PATH="$HOME/.yarn/bin:$HOME/.config/yarn/global/node_modules/.bin:$PATH"
10:06:13 PM:
10:06:13 PM: > Successfully installed Yarn 1.13.0! Please open another terminal where the yarn command will now be available.
10:06:14 PM: Installing NPM modules using Yarn version 1.13.0
10:06:15 PM: yarn install v1.13.0
10:06:15 PM: warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
10:06:15 PM: [1/4] Resolving packages...
10:06:16 PM: [2/4] Fetching packages...
10:06:27 PM: info [email protected]: The platform "linux" is incompatible with this module.
10:06:27 PM: info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
10:06:27 PM: [3/4] Linking dependencies...
10:06:27 PM: warning " > [email protected]" has unmet peer dependency "babel-core@^6.0.0".
10:06:31 PM: [4/4] Building fresh packages...
10:06:31 PM: success Saved lockfile.
10:06:31 PM: Done in 16.62s.
10:06:31 PM: NPM modules installed using Yarn
10:06:32 PM: Started restoring cached go cache
10:06:32 PM: Finished restoring cached go cache
10:06:32 PM: unset GOOS;
10:06:32 PM: unset GOARCH;
10:06:32 PM: export GOROOT='/opt/buildhome/.gimme/versions/go1.12.linux.amd64';
10:06:32 PM: export PATH="/opt/buildhome/.gimme/versions/go1.12.linux.amd64/bin:${PATH}";
10:06:32 PM: go version >&2;
10:06:32 PM: export GIMME_ENV='/opt/buildhome/.gimme/env/go1.12.linux.amd64.env';
10:06:32 PM: go version go1.12 linux/amd64
10:06:32 PM: Installing missing commands
10:06:32 PM: Verify run directory
10:06:32 PM: Executing user command: npm run build
10:06:32 PM: > [email protected] build /opt/build/repo
10:06:32 PM: > gulp build
10:06:32 PM: [16:36:32]
10:06:32 PM: Requiring external module babel-register
10:06:33 PM: gulp[1305]: ../src/node_contextify.cc:626:static void node::contextify::ContextifyScript::New(const v8::FunctionCallbackInfov8::Value&): Assertion args[1]->IsString()' failed. 10:06:33 PM: 1: 0x8dc510 node::Abort() [gulp] 10:06:33 PM: 2: 0x8dc5e5 [gulp] 10:06:33 PM: 3: 0x91081e node::contextify::ContextifyScript::New(v8::FunctionCallbackInfo<v8::Value> const&) [gulp] 10:06:33 PM: 4: 0xb6166b [gulp] 10:06:33 PM: 5: 0xb63602 v8::internal::Builtin_HandleApiCall(int, v8::internal::Object**, v8::internal::Isolate*) [gulp] 10:06:33 PM: 6: 0x615e94dbe1d 10:06:33 PM: Aborted (core dumped) 10:06:33 PM: npm 10:06:33 PM: ERR! code ELIFECYCLE 10:06:33 PM: npm 10:06:33 PM: ERR! 10:06:33 PM: errno 10:06:33 PM: 134 10:06:33 PM: npm 10:06:33 PM: ERR! [email protected] build: gulp build`
10:06:33 PM: npm ERR! Exit status 134
10:06:33 PM: npm
10:06:33 PM: ERR!
10:06:33 PM: npm
10:06:33 PM: ERR! Failed at the [email protected] build script.
10:06:33 PM: npm ERR!
10:06:33 PM: This is probably not a problem with npm. There is likely additional logging output above.
10:06:33 PM: npm
10:06:33 PM: ERR!
10:06:33 PM: A complete log of this run can be found in:
10:06:33 PM: npm
10:06:33 PM: ERR! /opt/buildhome/.npm/_logs/2019-05-18T16_36_33_261Z-debug.log
10:06:33 PM: Skipping functions preparation step: no functions directory set
10:06:33 PM: Caching artifacts
10:06:33 PM: Started saving node modules
10:06:33 PM: Finished saving node modules
10:06:33 PM: Started saving yarn cache
10:06:33 PM: Finished saving yarn cache
10:06:33 PM: Started saving pip cache
10:06:33 PM: Finished saving pip cache
10:06:33 PM: Started saving emacs cask dependencies
10:06:33 PM: Finished saving emacs cask dependencies
10:06:33 PM: Started saving maven dependencies
10:06:33 PM: Finished saving maven dependencies
10:06:33 PM: Started saving boot dependencies
10:06:33 PM: Finished saving boot dependencies
10:06:33 PM: Started saving go dependencies
10:06:33 PM: Finished saving go dependencies
10:06:35 PM: Error running command: Build script returned non-zero exit code: 134
10:06:35 PM: Failing build: Failed to build site
10:06:35 PM: failed during stage 'building site': Build script returned non-zero exit code: 134
10:06:35 PM: Finished processing build request in 32.59086766s
10:06:36 PM: Shutting down logging, 0 messages pending

Display the affected systems in the incident cards

- Do you want to request a feature or report a bug?

This is bug.

- What is the current behavior?

There is no way which systems were affected by a past incident.

- If the current behavior is a bug, please provide the steps to reproduce.

There is no information in the incident card.

- What is the expected behavior?

We should display the affected systems with the incident.

RSS

- Do you want to request a feature or report a bug?
feature
- What is the current behavior?
missing

Is RSS still a thing? I think so... Wouldn't it be pretty cool to get an rss feed for the status pages. I would be even cooler to subscribe to only the system that you are interested in.

What are your thoughts?

Create gulp task for creating new incidents

- Do you want to request a feature or report a bug?
feature

- What is the current behavior?
Current instructions direct users to create new incidents by running:

cd site
hugo new incidents/oh-no-something-went-wrong.md

This runs the user's global version of Hugo, which loses the advantage of having the Hugo binary bundled directly in the repo. Also, changing into the site directory for this command, then having to change back out to build the site seems like an unnecessary hassle.

- What is the desired behavior?
A specialized gulp task could leverage the bundled binaries and run directly from the repo root. If someone want to get really fancy, this could include the interactive prompts suggested in #16 as well.

CANT VIEW MY OWN STATUS PAGE

OH MY GOD SOMEONE HELP MY STATUS PAGE I DONT HAVE PERMISSON TO VIEW IT IM USING THE RIGHT EMAIL ITS JUST GONE PLEASE SOMEONE HELP

[security] Enforce Branch Protections

This is an issue generated by (for-internal-use-only)github-tools

Description

This repository has exceeded the development grace period, and the repo owner must decide if branch protections should be enforced.
If this repository houses code used in production in any capacity, branch protections must be enforced. Read (for-internal-use-only)here for more details

What do I need to do?

You can control whether or not branch protections are enforced by exclusively creating either of the labels:
'enforce-branch-protections: true' or 'enforce-branch-protections: false'
If there is no branch protection control label, this issue will be recreated.
Once you have created either label, you can close this issue.
If you have issues or questions, please reach out to #internal-security-n-compliance on slack.

Scheduled maintenance

It would be nice if there was a way to show scheduled maintenance before it takes place, perhaps per-system or just a notice at the top above the systems.

Responsive design not working on iPhone 6S

- Do you want to request a feature or report a bug?
Bug

- What is the current behavior?
Responsive design not working on iPhone 6S, shows tiny desktop layout

- If the current behavior is a bug, please provide the steps to reproduce.
Open iOS Safari browser on iPhone 6S
Type in ‘netlifystatus.com’ (or any other Status Kit powered status pages)

- What is the expected behavior?
Responsive design that resized to accommodate the screen resolution as displayed on Android devices

- Please mention your node.js, and operating system version.
iOS 11.2.5 (latest)

Integrate Deploy Preview to be able to check that PRs don't break everything

- Do you want to request a feature or report a bug?

This is a feature.

- What is the current behavior?

There is no way to know if new changes break the template.

- What is the expected behavior?

We should have Netlify building deploy previews of this repository and notifying pull requests so we can verify that new changes don't break the template.

template too big

- Do you want to request a feature or report a bug?
bug
- What is the current behavior?

- If the current behavior is a bug, please provide the steps to reproduce.
attempt to click "Use Template" button on the repo.
- What is the expected behavior?
a new repo is initialized from the template
- Please mention your node.js, and operating system version.
n/a

Issue creating indent not taking action

Hello again i finnly figure out how to make an issue but when i need to i dont know what folder to put it in what path should you put it in

Cant create new indent with npm

How do you create a issue i tried everything

Add interactive command to create new incident.

- Do you want to request a feature or report a bug?

This is a new feature.

- What is the current behavior?

You need to use hugo directly to create a new incident and then modify the frontMatter.

- What is the expected behavior?

I'd like to type something like npm run new and then be prompted with a series of questions, something like this:

prompt> npm run new
output > What the cause of the incident? 
input   > Connection issues in the load balancer
output > What's the severity of the incident? (degraded-performance, minor-outage, major-outage...)
input   >  minor-outage
output > What are the affected systems? (API, CDN, Origin servers...)
input   > CDN, Origin servers
output > Edit site/content/incidents/connection-issues-in-the-load-balancer.md ? (y/n)
input   > n
prompt>

The last question is not required, but having a prompt like this would make the process slightly faster and more convenient, specially to fill severity and affected systems.

Please make RSS feed discoverable

Hello,

I wanted to subscribe to netlifies status page but there did not appear to be any way to do so. I keep track of the status of most products I use via Atom or RSS feeds. Netlify has a feed at http://netlifystatus.com/index.xml but I didn't realize it until I was about to make a feature request because the alerting system we use can't find it (I found it by searching this issue tracker and finding what would have been a duplicate issue for RSS support that was marked as invalid). Please add a link in the header so that tools can find the page:

<link href="/index.xml" rel="feed" type="application/rss+xml" title="Netlify Status" />

For more information on doing this with Hugo, see this page: https://gohugo.io/templates/rss/

Project errors with node@lts

When trying to create a new incident via npm run new-incident it fails trying load everything. I've run npm install and worked out as many issues as I could but have had no luck. I just deployed this to netlify and it all worked well. I wanted to create an incident just to test things out, but no luck.

Here is my full output log

npm run new-incident                                    ✘ 1 master ✱

> [email protected] new-incident /Users/anthony/Documents/Projects/Canteen/Server/Status
> gulp new-incident

[11:42:23] Failed to load external module @babel/register
[11:42:23] Requiring external module babel-register
assert.js:351
    throw err;
    ^

AssertionError [ERR_ASSERTION]: Task function must be specified
    at Gulp.set [as _setTask] (/Users/anthony/Documents/Projects/Canteen/Server/Status/node_modules/undertaker/lib/set-task.js:10:3)
    at Gulp.task (/Users/anthony/Documents/Projects/Canteen/Server/Status/node_modules/undertaker/lib/task.js:13:8)
    at Object.<anonymous> (/Users/anthony/Documents/Projects/Canteen/Server/Status/gulpfile.babel.js:26:6)
    at Module._compile (internal/modules/cjs/loader.js:707:30)
    at loader (/Users/anthony/Documents/Projects/Canteen/Server/Status/node_modules/babel-register/lib/node.js:144:5)
    at Object.require.extensions.(anonymous function) [as .js] (/Users/anthony/Documents/Projects/Canteen/Server/Status/node_modules/babel-register/lib/node.js:154:7)
    at Module.load (internal/modules/cjs/loader.js:605:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:544:12)
    at Function.Module._load (internal/modules/cjs/loader.js:536:3)
    at Module.require (internal/modules/cjs/loader.js:643:17)
    at require (internal/modules/cjs/helpers.js:22:18)
    at execute (/Users/anthony/Documents/Projects/Canteen/Server/Status/node_modules/gulp/node_modules/gulp-cli/lib/versioned/^4.0.0/index.js:36:18)
    at Liftoff.handleArguments (/Users/anthony/Documents/Projects/Canteen/Server/Status/node_modules/gulp/node_modules/gulp-cli/index.js:175:63)
    at Liftoff.execute (/Users/anthony/Documents/Projects/Canteen/Server/Status/node_modules/liftoff/index.js:203:12)
    at module.exports (/Users/anthony/Documents/Projects/Canteen/Server/Status/node_modules/flagged-respawn/index.js:51:3)
    at Liftoff.<anonymous> (/Users/anthony/Documents/Projects/Canteen/Server/Status/node_modules/liftoff/index.js:195:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] new-incident: `gulp new-incident`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] new-incident script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/anthony/.npm/_logs/2018-11-08T19_42_25_422Z-debug.log

I'm not a Node developer so this is a bit over my head. My version info is stated below too.

macOS 10.14
Node v11.1.0
npm v6.4.1

Add notifications

- Do you want to request a feature or report a bug?

This is a new feature.

- What is the current behavior?

There is no way to notify people.

- If the current behavior is a bug, please provide the steps to reproduce.

- What is the expected behavior?

People should be able to subscribe to changes in the status page.
We can use services like chimpmail and twilio that provider JS api's for this. We can also use some Lambda functions for more elaborated notifications if we need to.

Minimum services I'd like to integrate with:

Twitter
Email
SMS

Hugo fails to build after new incident is created

- Do you want to request a feature or report a bug?
Bug

- What is the current behavior?
nil error on Incident template

- If the current behavior is a bug, please provide the steps to reproduce.

clone repo
npm install
cd site
hugo new incidents/fail.md
update to resovled
npm start
fail

- What is the expected behavior?
it builds

- Please mention your node.js, and operating system version.

This is a hugo issue I made
https://discourse.gohugo.io/t/netlify-status-kit-upgrade-issue/8175

Integrate with third parties APIs

- Do you want to request a feature or report a bug?

This is a new feature.

- What is the current behavior?

There is no way to add information about third party systems, like GitHub.

- If the current behavior is a bug, please provide the steps to reproduce.

- What is the expected behavior?

People should be able to add third party systems to their status pages to let users know that an outage in a third party service might be causing service disruptions.

Deploy successful but no code push to Github

- Do you want to request a feature or report a bug?
bug
- What is the current behavior?
Deploy by using the button:
Deploy successful but no code push to Github.
Log on deploy:

1:57:25 PM: Error pushing to remote repository at [email protected]:lz100/netlify-statuskit

- If the current behavior is a bug, please provide the steps to reproduce.
Just click the deploy button to make a new website
- What is the expected behavior?
Code
- Please mention your node.js, and operating system version.
N.A.

The problem is caused by Github workflows. Third-party apps are not allowed to push workflows to github. Current template has a /.github folder with a workflow, so it will fail to push to Github. I am having the same issue with my own template where it also has a workflow and I cannot use netlify deploy button. Is there any way to solve this?

Missing title and date in new incident

- Do you want to request a feature or report a bug?
🐛

- What is the current behavior?

hugo -s site new -k incidents incidents/oh-no-something-went-wrong.md
hugo new incidents/test.md

Does not add title and date front matter like the incidents.md file states.

hugo new test.md

does create the front matter.

I can't find a bug in the hugo issue tracker.

That results in the following image

- If the current behavior is a bug, please provide the steps to reproduce.

Create site and create a new incident.
Look at the new file
Realize no title and date are present

- What is the expected behavior?
The date and title should be generated from the command or the command needs to be updated to tell users how to have those items generated.

- Please mention your node.js, and operating system version.

$ hugo version
Hugo Static Site Generator v0.24.1 darwin/amd64 BuildDate: 2017-06-29T09:40:24-06:00

$ node -v
v6.11.0

netlify / netlify-statuskit Goto Github PK

netlify-statuskit's Introduction

Introduction

Project Status

Netlify's Statement

Initial configuration

Extra configuration

Reporting systems

Full customization

Managing incidents

Creating new incidents

Resolving incidents

Tracking activity

Development

netlify-statuskit's People

Contributors

Stargazers

Watchers

Forkers

netlify-statuskit's Issues

Description

What do I need to do?

Recommend Projects

Recommend Topics

Recommend Org