!coeAONBrWyDJnYMbMi:nixos.org

NixOS System Operations

551 Members
About system administration for running NixOS systems in production. Declaratively manage your operations. | Room recommendations: #networking:nixos.org147 Servers

Load older messages


SenderMessageTime
8 Dec 2024
@hexa:lossy.networkhexayeah, k900 implied it wasn't yesterday fwiw22:42:28
@hexa:lossy.networkhexawhich would make queries much more easy to write in the face of how badly the feedback of the ruler is22:43:06
@hexa:lossy.networkhexaat least I'm now getting fast feedback22:46:27
@hexa:lossy.networkhexa
building '/nix/store/3f7ww8pjj8v32w45vcflz6l7lvc767vp-rules.yaml.drv'...
ERRO[0000] unable parse rules file                       error="could not parse expression for alert 'PostgresqlCollationMismatch' in group 'postgresql': parse error at line 5, col 1: syntax error: unexpected $end, expecting )" file=/nix/store/b90hjjsvamndv0z2a9vqfz91w66lbc43-rules.yaml
lokitool: error: prepare operation unsuccessful, unable to parse rules files: file read error, try --help
error: builder for '/nix/store/3f7ww8pjj8v32w45vcflz6l7lvc767vp-rules.yaml.drv' failed with exit code 1;
       last 2 log lines:
       > ERRO[0000] unable parse rules file                       error="could not parse expression for alert 'PostgresqlCollationMismatch' in group 'postgresql': parse error at line 5, col 1: syntax error: unexpected $end, expecting )" file=/nix/store/b90hjjsvamndv0z2a9vqfz91w66lbc43-rules.yaml
       > lokitool: error: prepare operation unsuccessful, unable to parse rules files: file read error, try --help
       For full logs, run 'nix log /nix/store/3f7ww8pjj8v32w45vcflz6l7lvc767vp-rules.yaml.drv'.
22:46:30
@hexa:lossy.networkhexafinally22:50:39
@hexa:lossy.networkhexaimage.png
Download image.png
22:50:39
@adam:robins.wtf@adam:robins.wtf Nice 23:57:10
@adam:robins.wtf@adam:robins.wtf I definitely need that collation mismatch alert ;) 23:57:41
9 Dec 2024
@hexa:lossy.networkhexapay up! 😄 00:00:13
@adam:robins.wtf@adam:robins.wtfi gotta set up loki first00:00:28
@hexa:lossy.networkhexaman, I hate how shitty log based alerting is00:00:31
@hexa:lossy.networkhexait could be so simple afer all00:00:39
@hexa:lossy.networkhexa * it could be so simple after all00:00:42
@hexa:lossy.networkhexae.g. logwatch00:00:53
@adam:robins.wtf@adam:robins.wtfwhat's the whole, working, rule look like?00:03:01
@hexa:lossy.networkhexa
      count_over_time({unit="postgresql.service"}
          |~ "database \"[^\"]+\" has a collation version mismatch"
          | regexp "database \"(?<database>[^\"]+)\""
        [5m])
00:03:47
@magic_rb:matrix.redalder.orgmagic_rb
In reply to @hexa:lossy.network
sent an image.
Alerts through matrix? Bold move
00:04:14
@hexa:lossy.networkhexafalls back to pushover when synapse or the bot are not up00:04:52
@hexa:lossy.networkhexathat is why alertmanager support routing 🤷00:05:11
@hexa:lossy.networkhexa * that is why alertmanager supports routing 🤷00:05:25
@magic_rb:matrix.redalder.orgmagic_rbAh cool00:05:28
@magic_rb:matrix.redalder.orgmagic_rbHey, i also do matrix notifs, for ssh login and smart stats00:05:44
@magic_rb:matrix.redalder.orgmagic_rbSo not one to judge00:05:58
@hexa:lossy.networkhexa🙂 00:06:03
@adam:robins.wtf@adam:robins.wtfscreenshot_2024-12-08-192345.png
Download screenshot_2024-12-08-192345.png
00:24:11
@adam:robins.wtf@adam:robins.wtfhelpful? i guess. but limiting to ten sections at a time isn't the best use of space00:24:51
@hexa:lossy.networkhexawell00:24:58
@hexa:lossy.networkhexaI have strong opinions about that question00:25:03
@adam:robins.wtf@adam:robins.wtfheh00:25:11
@hexa:lossy.networkhexa

one page has

[ruler: <ruler_config>}
00:25:21

Show newer messages


Back to Room ListRoom Version: 10