Skip to content

Latest commit

 

History

History
54 lines (39 loc) · 1.93 KB

README.md

File metadata and controls

54 lines (39 loc) · 1.93 KB

LDstatus

Gitter

Gitter Seen as this integrates with Gitter it makes sense that it has it's own Gitter chat. I've been using it as a place to test the behaviour of this project, whilst it's being developed. But your welcome to come and chat!

Config

config.json

You need to create a config.json file in the root directory, this is where you will place your api tokens/keys.

I.E. config.json should be

{
  "UPTIMEROBOT_TOKEN" : "<TOKEN_YOU_GENERATE_FOR_UPTIMEROBOT>",

  "GITTER_PAT_TOKEN" : "<YOUR_GITTER_BOTS_PERSONAL_ACCESS_TOKEN>",
}

Up time robot does not provide you with a token, so I suggest using too generate your own. I generated a 16byte token via this link.

uptime robot

Alert contact

To create a web hook from the uptime robot dashboard you need to go to the settings page, and add an alert contact. An alert contact of type webhook is needed.

The url to notify needs to be to url to wherever your hosting your handler with a ? on the end. I'm using Google Cloud Functions, But Amazon AWS Lambda or another "Serverless" provider should work with a little tweaking.

The POST data should be

{
  "provider":"uptimerobot",
  "token":"<TOKEN_YOU_GENERATE_FOR_UPTIMEROBOT>",
  "room":"<GIITER_ROOM/NAME>",
  "statuspageurl":"status.test.zakwest.tech"
}

statspageurl is an optional param.

Enabling the webhook for a monitorURL

To enable the web hook for a specific monitor, go it it's edit page and tick the box next to the name of your web hook.

Deployment

This will vary depending on whether your using Functions or Lambda.

I am using >gcloud beta functions deploy webhook --stage-bucket <ldstatus_staging_bucket> --trigger-http for Google Cloud Functions.