chillum / jsonmon Goto Github PK

Since v1.0, Access-Control-Allow-Origin header in server responses is *. This has benefits:

• We can make complex Web portals that use jsonmon to integrate
• We're able to test the UI in development

We may want to make this configurable as not everyone wants this. Maybe we should even set the new default to no such header (and have some environment variable to specify it's value if we really need this), but not really sure about it now.

We need this header to enable efficient gzipping on the Web server

I'm not sure if that's connected to Go runtime or my code, but a long time ago this behaved as intended.

The actual bug is that when HTTPS certificate becomes expired, jsonmon does not report it as error until the app is restarted.

Opened a golang-nuts thread hoping for more ideas.

installing from a zip file is not convenient, we should provide Linux packages

This seems like pretty much exactly what I need: highly configurable, super-lightweight alerting system written in Go.

Do you know how much effort it would take to get this thing working on Windows?

I really have a situation like this: my custom notification plugin takes a lot of time to work. It relies on a MSFT REST service, so that's the case.

So, what's happening while it's sending.

1. jsonmon invokes the notification plugin
2. it hangs for a while
3. it seems like at this point my check is waiting for notification plugin to exit to sleep and to re-check

I don't think, this behaviour is appropriate. That is: notification plugins should be async and if it has to wait, it should do it in the background.

for now it has a blank body, that can be misunderstood by recepients

it would be very nice if we include a body like {name} is back to normal. It has been down for {time}.

It would be very convenient to have the basic Web auth in jsonmon.

It would be nice, if shell command accepted return for the return code

Severe problem, need to investigate

Race conditions, where several triggers flicker in one second, are possible.

We should consider moving to ETag.

API should return the reason, why the check failed. This may help when the initial reason is not more the case. Example (not sure about exact syntax yet):

[
  {
    "name": "Test",
    "web": "http://localhost",
    "failed": true,
    "why": "Get 127.0.0.1 failed"
  },
]

We probably should introduce a limit on reason's length (also applies to match).

It would be nice to have checks like:

- web: https://localhost
  ssl: 3d

That is: to be notified when the SSL certificate expires in 3 days.

They would be nice as well. Might be used for GitLab health check not to expose the token.

It would be nice to allow shell, web and return as lists if requested (keeping the old syntax as well)

Someday we will drop web and shell in one block. That is:

- name:   Yandex
  shell:  ping localhost
  web:    http://localhost

I'm not sure, if there are real users of this undocumented feature, but this will give very strange notifications.