monzero - A monitoring stack using PostgreSQL as the backend. http://git.zero-knowledge.org/gibheer/monzero/atom/cmd/moncheck?h=20221215 2021-12-02T16:53:47Z 2021-12-02T16:53:47Z Gibheer gibheer+git@zero-knowledge.org 2021-12-02T16:53:47Z urn:sha1:41d4805d584161ca16b8187194385e47c36422a6 2021-12-02T14:57:00Z Gibheer gibheer+git@zero-knowledge.org 2021-12-02T14:57:00Z urn:sha1:b69cd1ea3e2894ebe5afd189c8719836b7ed7aa6 This switches the internals of the moncheck instance to using the monzero.Checker API. This way we can reuse it completely and also see if it works properly. 2019-08-12T12:49:53Z Gibheer gibheer+git@zero-knowledge.org 2019-08-12T12:49:53Z urn:sha1:e2b479c34fcee4c41009fc9e8fe869831fbd494f With this, it is now possible to support multiple check instances and balance the load. 2019-05-28T11:38:16Z Gibheer gibheer+git@zero-knowledge.org 2019-05-28T11:38:16Z urn:sha1:142f9cf3582e111910723cacbdc4a66267a79c75 Any time the state of the check changes, we need to refresh the column. This will be used in the frontend. This way it is much faster than using the notifications and also doesn't rely on the last of it being still around. 2019-04-10T07:09:15Z Gibheer gibheer+git@zero-knowledge.org 2019-04-10T07:09:15Z urn:sha1:2bfe75c8a702508284ddb75a8db3a1b4911b9635 This should make the frontend much easier to handle than before. It isn't the best solution, but it makes it easier in the frontend for now. 2019-04-09T07:51:52Z Gibheer gibheer+git@zero-knowledge.org 2019-04-09T07:51:52Z urn:sha1:532f55d640ec0ab2cb3f352c8e449e9351522344 It happend all the time, that connections were hanging in idle in transaction state. This was caused by a rollback stuck behind a sleep loop to wait for the next bunch of checks to run. This also replaces a Query() call with QueryRow, as we only expect a single row and this cleans up the code a bit. 2019-01-11T12:02:37Z Gibheer gibheer+git@zero-knowledge.org 2019-01-11T12:02:37Z urn:sha1:7ed255d5911f22ac278c1e7a34b11ce273029c6e This can help with determining which exact check connection broke the check. 2019-01-07T14:50:55Z Gibheer gibheer+git@zero-knowledge.org 2019-01-07T14:50:55Z urn:sha1:3b222e06ed63050cb99020d9d74ca0f1e52959d2 The default worker count was set to 25, which might be too much depending on the amount of cores available. Now make the default 25 and let people decide on how many they want to use. 2018-12-12T13:05:46Z Gibheer gibheer+git@zero-knowledge.org 2018-12-12T13:05:46Z urn:sha1:affbe8c4206437b265e322aafaa74d39f0278d57 2018-12-11T19:21:14Z Gibheer gibheer+git@zero-knowledge.org 2018-12-11T19:21:14Z urn:sha1:af843d76e1aff287af3d07dd5890f814991e662a It would be nice to support multiple notification mechanisms with a way to disable all or part of them. So for now, this is bound to the check but may change again in the future. Apart from that, all notifications get written to the notification table, so that the notifiers can do their job and ACK their own notifications.