monitoror / monitoror Goto Github PK

see : https://github.com/digineo/go-ping/blob/master/codecov.yml
see: https://circleci.com/blog/go-v1.11-modules-and-circleci/
see: https://circleci.com/docs/2.0/code-coverage/#codecov

Randomized anti-DoS is only useful for some tile types:

• Jenkins

Add Makefile for tarting build / tests / package front

Return long cache if the call return timeout

Wrap Store for Put the value in the store with different timeout.
Using JSONErrorHandler with custom Error type and get the value if it's a timeout.

https://gist.github.com/jsdidierlaurent/e3dd5c939263c80d2202ba4eceabfd53

To improve split between which data is sent to server and which one is used in front only, I think using a custom key for group sub titles can be great.

It allows to do something like that in front state:

export interface TileState {
  type: TileType,
  label?: string,
  subTiles?: TileState[],
}

• Create common struc in model/response.go
• Create "enum" for Status

• If version exist in tags, skip release binaries steps
• use VERSION file in build for setting binaries version
• use monitoror --version to set release / tag version
• create CHANGELOG file to setup CHANGELOG
• use https://github.com/tcnksm/ghr to release version / tag

see : https://circleci.com/blog/publishing-to-github-releases-via-circleci/

https://github.com/microsoft/azure-devops-go-api

Change default logger for something like this :

[2018-01-16 10:35:24.38231] [MiddlewareServer/server.go:147] [INFO ] – Starting....
[2018-01-16 10:35:24.38252] [MiddlewareServer/server.go:148] [ERROR] – some error

Instead of JSON

See : labstack/echo#1017

To avoid spamming your own services, add cache middleware with 8s TTL (with gcache ?)
Don't forget headers

Output from: http://localhost:8080/api/v1/info

{
  "build-info": {
    "version": "0.0.2-beta-31-g37cb071",
    "git-commit": "37cb071",
    "build-time": "2019-05-22T22:26:13+00:00"
  },
  "configuration": {
    "Port": 8080,
    "Env": "development",
    "UpstreamCache": {
      "Expire": 10000,
      "CleanupInterval": 1000
    },
    "DownstreamCache": {
      "Expire": 120000,
      "CleanupInterval": 10000
    },
    "Monitorable": {
      "Ping": {
        "Count": 2,
        "Timeout": 1000,
        "Interval": 100
      },
      "Port": {
        "Timeout": 1000
      },
      "Gitlab": {
        "Token": ""
      },
      "Github": {
        "Token": ""
      },
      "TravisCI": {
        "Token": "",
        "Timeout": 2000,
        "Url": "https://api.travis-ci.org/"
      }
    }
  }
}

Some keys are kebab-case, some are PascalCase, I will prefer camelCase everywhere, is that possible?

Http repository can query the same URL with différent parameters (ex : different json key in the same file)

Caching file of the same url should be great

For fixing cache issue in configuration file, we need to replace the full url to path without host:port/api/v1.
Ex :
url: http://localhost:8080/api/v1/http/any?url=test.com
will be :
path: /http/any?url=test.com

For doing this, we need to add apiPath notion in front end.
By default apiPath = front hostname:port + /api/v1 but it's overridable in url params

After this, we can change the actual monitoror path :
http://localhost:8000/?config=http://localhost:8080/api/v1/config?path=./test/faker-config.json
by this :
http://localhost:8000/?apiPath=http://localhost:8080/api/v1&configPath=./test/faker-config.json
Or (in production)
http://localhost:8080/?configUrl=http://github.com/...

See: https://github.com/xanzy/go-gitlab

• monitoror version : expose full build info
• monitoror --version : expose version
• monitoror --help
• monitoror validate config.json
• monitoror --verbose
• monitoror init

123456789 => 123 456 789
15346ms => 15,3s ?

Change structure for something like this :
/cmd
├── main.go
/server
├── api/
├── route/
...
├── server.go
/front
...

https://www.codementor.io/packt/how-to-set-up-a-project-in-echo-mpo39w5zu

We need a dynamic / generated tiles in config.

• Jenkins multibranch pipeline
• MR build status in Gitlab
• List all checkers for pingdom

We need to add this in hydrate config process

⚠️ must works with groups

Hi guys!

The demo on your website doesn't seem to work.

In the same way, I can't get Monitoror to run on my machine (Debian 64 bits) with the provided executable and default configuration. I get the same error as on your site using ?configPath mode. At the end I'm asked to check my configuration because it can't be loaded.

Did I miss a step?

Use Viper for config setting and provide config to all Model and set config in echo.context

• In develop : expose front on port 3000 with npm and webpack
• In builded version : use webpack for building front and inject it inside go binaries and expose it in root directory

⚠️ backend must be start without webpack file (for develop)

• https://github.com/go-webpack/webpack
• https://github.com/go-bindata/go-bindata
• https://github.com/Caiyeon/goldfish
• https://github.com/GeertJohan/go.rice
• https://github.com/dfcook/vue-webpack4-template

GET : /api/v1/config/validate
With 2 possible parameters:

• url: url of hosted config (like on github/gitlab/web server, watever)
• file: file name of configuration file hosted in config directory on host (require --client-config-directory parameter)

See: https://eagain.net/articles/go-dynamic-json/

• Split build/ tests into buid-front / back and test-font/back
• Adding news steps for deploying coverage for front
• Adding language tags for coverage : https://docs.codecov.io/docs/merging-reports

Actualy the Error Handler is from https://github.com/eurie-inc/echo-sample

Change it for Monitowall usage

See : https://github.com/Alex-D/MonitoWall/blob/develop/server/modules/counter.youtrack.js

https://github.com/ckopjiuoh/go-youtrack-api-client

https://github.com/bndr/gojenkins

In the future we will have "dynamic" tile (like list merge request or pipeline multi branch)
In the clinet-config we need a block for this type of config.

This route will transform this bloc in "classical" tile config (0-x tile by line)

POST : /api/v1/config/hydrate

Maybe something like this ?

Tag: x.x.x
Master: x.x.x-master-{hash}
Develop: x.x.x-develop-{hash}
PR: x.x.x-nightly-{hash}

Create a service for faking Gitlab/Jenkins ...

Use project param for asking response.
Ex : gitlab projet name : test.success.12365 for

{
   "Status": "SUCCESS",
   "Label": "test",
   "Duration": 12365
}

https://github.com/russellcardullo/go-pingdom

To keep server things on server side, sending API URLs via the config file seems to be a great way to avoid hardcoded URLs in front. Also, params can be added to the URL as the front does not need them (so we can drop them from config sent to front).

Note: do not forget group items and hydrated ones.

{
  columns: 4,
  tiles: [
    {
      type: 'ping',
      url: 'http://domain.tld:port/api/.../ping?param1&param2'
    }
  ]
}

see : https://github.com/Alex-D/MonitoWall/blob/develop/server/modules/server.http.js

It's a more user friendly name :)