monzero - A monitoring stack using PostgreSQL as the backend. http://git.zero-knowledge.org/gibheer/monzero/atom?h=master 2024-09-05T17:38:25Z 2024-09-05T17:38:25Z Gibheer gibheer+git@zero-knowledge.org 2024-09-05T17:38:25Z urn:sha1:6ea4d2c82de80efc87708e5e182034b7c6c2019e lib/pq is out of maintenance for some time now, so switch to the newer more active library. Looks like it finally stabilized after a long time. 2023-09-05T13:24:11Z Gibheer gibheer+git@zero-knowledge.org 2023-09-05T13:24:11Z urn:sha1:efa2f5b307be6db42b781be4f9d86306114c0cb8 With monzero supporting slog to get debug output from check commands, moncheck now supports that too by changing the level to debug. 2023-09-05T13:07:38Z Gibheer gibheer+git@zero-knowledge.org 2023-09-05T13:07:38Z urn:sha1:26a4ca6ab56d23054f606bc378ba355cebce485a With this moncheck itself is also changed to use slog. The early config parsing is still using log as we do not have any idea what else to use. But from then slog is used at all points. With the additional config options a man page was also added to explain the new config options. 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.