monzero - A monitoring stack using PostgreSQL as the backend. http://git.zero-knowledge.org/gibheer/monzero/atom?h=0.1 2019-01-24T08:25:00Z 2019-01-24T08:25:00Z Gibheer gibheer+git@zero-knowledge.org 2019-01-24T08:25:00Z urn:sha1:e8e67f091a7588a68f858a1e7284fbd876377cf0 This way it is possible to jump between a node and its checks. 2019-01-24T08:18:46Z Gibheer gibheer+git@zero-knowledge.org 2019-01-24T08:18:46Z urn:sha1:a9634bbcaa2377e07a47b9ff1f05dfda39336a9d Somewhen in the last couple years, something called a referer policy was introduced. This avoided the correct relocation after any action was sent. Now with the fix, the redirect properly works. 2019-01-11T22:02:58Z Gibheer gibheer+git@zero-knowledge.org 2019-01-11T22:02:58Z urn:sha1:6a5c0b92bd12f4fb06780b67f5f8019de3c827f0 This adds the first basic listing of notifications to the check details. No idea how many of them should be listed here, but having the list at all for a start should be okay. 2019-01-11T18:54:06Z Gibheer gibheer+git@zero-knowledge.org 2019-01-11T18:54:06Z urn:sha1:aed518ea7670efb52a3d7fed3a35f298409c4003 There is just no information that could possibily be shown there, that isn't already shown somewhere else. 2019-01-11T12:04:35Z Gibheer gibheer+git@zero-knowledge.org 2019-01-11T12:04:35Z urn:sha1:168c425fb6954646c8a859296f7c85173e539c92 The checks_notify table was missing and needs to be added. As this is still alpha software, there is no need for a migration step yet. 2019-01-11T12:03:07Z Gibheer gibheer+git@zero-knowledge.org 2019-01-11T12:03:07Z urn:sha1:203ca756e14853d42663a334fb8bfd9f9aba2999 When a check is acknowledged, no more further notifications should be sent. But for the notified system, it should be made clean, that it is taken care of and no further actions need to be done, therefore send an okay, even when the check isn't okay. 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-10T08:50:18Z Gibheer gibheer+git@zero-knowledge.org 2019-01-10T08:50:18Z urn:sha1:f804446ad3e2e653ffd6ef00a662d91ab79bc0dd The adding of the order by clause happend in the wrong position and therefore made the resultset unuseable. 2019-01-10T06:10:02Z Gibheer gibheer+git@zero-knowledge.org 2019-01-10T06:10:02Z urn:sha1:73c735308242ab9d47227b6b64bf0fff393f756c The result list should be ordered for the state when unhandled entries should be returned. Else it is getting weird to figure out, which issue is the most important to fix. 2019-01-10T04:50:02Z Gibheer gibheer+git@zero-knowledge.org 2019-01-10T04:50:02Z urn:sha1:ea658177eea72175ab23d08f3064b4f346133c46 With some monitors, the view may be too wide to make out, which line belongs to what. For that purpose, add a background color when the mouse is hovering over a line.