yegor256 / sixnines Goto Github PK

Website Availability Monitor: add your website to our dashboard and get 24x7 monitoring of its availability (and a badge!)

Home Page: https://www.sixnines.io

License: MIT License

Ruby 78.60% XSLT 8.83% Shell 0.27% HTML 0.04% Procfile 0.07% Sass 3.37% Haml 8.82%

ruby availability monitoring hosted

sixnines's Introduction

SixNines is a hosted service to validate and prove availability of your web service and sites.

Read this blog post for more details: SixNines.io, Your Website Availability Monitor.

The badge is available as:

https://www.sixnines.io/b/5fa8?style=flat&format=png

Here, the style parameter can be either round or flat. The format parameter can be either svg (106x20) or png (424x80).

This is how you put it in your README (in Markdown):

[![Availability at SixNines](https://www.sixnines.io/b/5fa8)](https://www.sixnines.io/h/5fa8)

The badge you see above works exactly like that.

DynamoDB Schema

The sn-endpoints table contains all registered end-points:

fields:
  login/H: GitHub login of the owner
  uri/R: URI of the endpoint, e.g. "http://www.google.com/?q=hello"
  id: Unique ID of the endpoint
  active: "yes" if it's alive, "no" otherwise
  created: Epoch time number of when it was added
  hostname: Host name of the URI, e.g. "google.com"
  pings: Total amount of ping's we've done so far
  failures: Total amount of failed attempts
  state: Either "up" or "down"
  updated: Epoch time of the most recent update of this record
  flipped: Epoch time of recent state change
  expires: Epoch time when it has to be pinged again
  log: Detailed log of the most recent failure
  favicon: URI of the favicon
sn-endpoints/unique: (index)
  id/H
sn-endpoints/hostnames: (index)
  active/H
  hostname/R
sn-endpoints/flips: (index)
  active/H
  flipped/R
sn-endpoints/expires: (index)
  active/H
  expires/R

The sn-pings table contains all recent pings:

fields:
  uri/H: URI of the endpoint we pinged
  time/R: Epoch time of ping
  local: IP address where we were pinging from
  remote: IP address of the endpoint we reached
  msec: How many milliseconds it took
  code: HTTP response code (2xx means success)
  delete_on: TTL attribute for DynamoDB (when to delete this item)

How to contribute?

First, install Java 8+, Maven 3.2+, Ruby 2.3+, Rubygems, and Bundler. Then:

$ bundle update
$ bundle exec rake --quiet

The build has to be clean. If it's not, submit an issue.

Then, make your changes, make sure the build is still clean, and submit a pull request.

In order to run a single test:

$ bundle exec rake run

Then, in another terminal:

$ bundle exec ruby test/test_base.rb -n test_lists_flips

Then, if you want to test the UI, open http://localhost:9292 in your browser, and login, if necessary, by adding ?glogin=tester to the URL.

sixnines's People

Contributors

Stargazers

Watchers

Forkers

ozhiganov pdaw pdacostaporto green2499 elohimsupremes mountaindude agrrh rad1k4l aleee133

sixnines's Issues

flips order is broken in front page

show duration of the last time after flip

multiple source points

Let's add a few more servers, where we can ping endpoints from. When connection fails, we should try to do it from another server, two times. Only if they both fail, we report a failure.

Let's show our current rate of pinging endpoints, to make sure we're alive. Let's just increment some global counter and show that counter on the front page. Let's update it via JavaScript, every second.

ID's must be unique

escape html entities in the log

numbers are off when there are no failures

show only failure logs

coupons

RSS with ups and downs

Let's generate RSS with flips

stripe

show age of endpoint

cache favicons

human readable dates and times

show all times and dates in human readable format

twitter:image

Let's add twitter:image to the history page.

show favicon in History page

show flip date in history

favicon is always default

terms of use

handle empty search query

on index page searchin an empty keyword results exception

show average and mean time

numbers rounding is not accurate

tweet about ups and downs

caching

We make too many DynamoDB requests. Let's introduce a simple in-memory caching layer for most intensive requests.

100% must never show up

show most recent failure HTTP details

availability is not calculated correctly

email subscribe to endpoints

A user should be able to subscribe to any endpoint and receive emails when the status changes. By default endpoint owner must be subscribed.

cookie encryption

email all server-side bugs

Let's email them to [email protected]

get avatar from GitHub for a user

endpoint.to_h: undefined method `[]' for nil:NilClass

undefined method `[]' for nil:NilClass
        ["/app/objects/endpoint.rb:66:in `to_h'"

show URI

w3c compliance

See https://validator.w3.org/nu/?doc=http%3A%2F%2Fwww.sixnines.io%2F

And this https://validator.w3.org/nu/?doc=http%3A%2F%2Fwww.sixnines.io%2Fh%2Fe203

AMP pages

Let's add AMP pages for all history pages.

skeleton

Basic Auth directly from URIs

Let's make it possible to specify login/password right in the URI for Basic Auth:

http://s3auth:[email protected]/

ping every minute

cookie.rb:29-31: We are not encrypting cooking anyhow...

The puzzle 1-e122d8f8 in objects/cookie.rb (lines 29-31) has to be resolved: We are not encrypting cooking anyhow at the moment and this is not secure at all. Let's introduce some encryption mechanism with a secret key.

The puzzle was created by Yegor Bugayenko on 07-Apr-17.

Estimate: 30 minutes, role: IMP.

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD.