simono41/chaos-jetzt-nixfiles
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
chaos-jetzt-nixfiles/secrets/all/monitoring.htpasswd

44 lines
4.2 KiB
Text
Raw Permalink Normal View History

services/monitoring: Setup The goal is to create a monitoring setup where each server monitors itself when it comes failing systemd services, disk or RAM filling up, …. In addition each prometheus will monitor remote prometheus and alertmanager instances for signs of failure (e.g. being unreachable, errors in notification delivery, dropping alerts). A lot of metrics (especially histograms from prometheus or alertmanager) are being dropped before ingestion to disk save on space and memory. Depending on how many servers we may or may not have in the future this could probably use some kind of overhaul since we rightnow have n^2 monitoring peer relationships (not even speaking of possible duplicated alerts).
2022-12-31 22:40:07 +01:00
{
Add adb and admin htpasswd user Also updated instructions for editing the .htpasswd
2023-01-03 16:07:00 +01:00
"data": "ENC[AES256_GCM,data:Xqc8Q0HEslyyCBFIYQOTVqNQJ/9PZ+tGivu2f6duobwz/qnGwT1lPUoC0/IISH4Q/7JhEacYZysCdOFO4PlGV3b8DKUel4WC+SwqRWglHSRpSN8RCcMgNDBSf9wKFSqQOBM8VAMKcnCCCCM1Zmc+sLJrLshAqvj3u/ABEIcqqrET,iv:1TuOgxbekoT+t/x0/w7gWOB02r/G8cX5Aa+OcJda/6g=,tag:hH1C1vGBzybGbdLeyRiB3w==,type:str]",
services/monitoring: Setup The goal is to create a monitoring setup where each server monitors itself when it comes failing systemd services, disk or RAM filling up, …. In addition each prometheus will monitor remote prometheus and alertmanager instances for signs of failure (e.g. being unreachable, errors in notification delivery, dropping alerts). A lot of metrics (especially histograms from prometheus or alertmanager) are being dropped before ingestion to disk save on space and memory. Depending on how many servers we may or may not have in the future this could probably use some kind of overhaul since we rightnow have n^2 monitoring peer relationships (not even speaking of possible duplicated alerts).
2022-12-31 22:40:07 +01:00
"sops": {
"kms": null,
"gcp_kms": null,
"azure_kv": null,
"hc_vault": null,
"age": [
{
"recipient": "age14ysl953378r2vvy7ft3gwce9xp83pr6wypf5lgx2yjwx2lxra5qs6j8eqe",
hosts/hamilton: init
2023-08-12 11:02:30 +02:00
"enc": "-----BEGIN AGE ENCRYPTED FILE-----\nYWdlLWVuY3J5cHRpb24ub3JnL3YxCi0+IFgyNTUxOSBmR21TejMwVXltZXlUdEFK\nZkF3V3gxSDBaS3d2UFNza2hmU29Jeks4TURVClV1bnZPTWZJT3A0cURyUzFMNVR1\nQjRTWUlPZ2t3TUMzbWxTZlZHU2lJajQKLS0tIDQ3VXp5cWpjWkdRZmwyR2FmUFNl\nMGMzaFY5VWlMdWcxWTZpNWxLYUU1bmsKwqKaRYTa+R08HIDx4jks2+Df6ny6xJgx\n3M7y7AfUeJXt4EK2nemGt885x8+RvPvsH+R3HtbhpCA9/dSXMlVD1Q==\n-----END AGE ENCRYPTED FILE-----\n"
services/monitoring: Setup The goal is to create a monitoring setup where each server monitors itself when it comes failing systemd services, disk or RAM filling up, …. In addition each prometheus will monitor remote prometheus and alertmanager instances for signs of failure (e.g. being unreachable, errors in notification delivery, dropping alerts). A lot of metrics (especially histograms from prometheus or alertmanager) are being dropped before ingestion to disk save on space and memory. Depending on how many servers we may or may not have in the future this could probably use some kind of overhaul since we rightnow have n^2 monitoring peer relationships (not even speaking of possible duplicated alerts).
2022-12-31 22:40:07 +01:00
},
{
"recipient": "age1w3wqxt5t00hjv43dcxlr5rjec5mvuzz9ajc8k04azq0gfx0ncgysu6mdmm",
hosts/hamilton: init
2023-08-12 11:02:30 +02:00
"enc": "-----BEGIN AGE ENCRYPTED FILE-----\nYWdlLWVuY3J5cHRpb24ub3JnL3YxCi0+IFgyNTUxOSBIYW9Gb3pPTTAwRC96a3Vp\nbFZyem8yQjZYemtYS2o4eDM5U252OVd1OVFjClFBam9pVjN5SFFQWFRIT3RhM1pV\nYkdxWGVhVjR0MklNMlpuSVFOWUVTZmMKLS0tIExPbGVRZUhIQ3Y5WDZtMityd3Vm\nSTlRODlTaGxTZkx2YUt0bUt5RmxiajgKww2Y2nKuZDlPyqwUIhbrxAXKnQhD7ymV\nQPz3yEKSnug2Z4UJzxigARKjOC5udJV0/OC+Pg+7EjaMViPheZKPkA==\n-----END AGE ENCRYPTED FILE-----\n"
},
{
"recipient": "age1uw83n25fx9th2q5y2yedeyzmtzk5yjtwx0kh054v5r2mxc0utuwqacdf77",
"enc": "-----BEGIN AGE ENCRYPTED FILE-----\nYWdlLWVuY3J5cHRpb24ub3JnL3YxCi0+IFgyNTUxOSBtb3diZVRiZmgra2JaeERP\nbnBhSHJqU01pK1Z1WFFwSW9EeFpFMXdTdGdNCjNoT0gwM1l4RGdCNFI1bmRLeHkx\nL05CWXpaeUYweVk5ekZQUFdSTHhrR3cKLS0tIG9IQlhxMEdSYitaUGczelNrK2JJ\nWkRZMFkyc0dxWVF6bzl4cVRPbU1lRU0KxNOmERyKlVhe0TmSwaWQccBFA+wstGjT\nTjRbBISfhiSrsET6sEdZtd4nzk2U1ovGNjMMQVig6f5HiIHrjHQq5Q==\n-----END AGE ENCRYPTED FILE-----\n"
services/monitoring: Setup The goal is to create a monitoring setup where each server monitors itself when it comes failing systemd services, disk or RAM filling up, …. In addition each prometheus will monitor remote prometheus and alertmanager instances for signs of failure (e.g. being unreachable, errors in notification delivery, dropping alerts). A lot of metrics (especially histograms from prometheus or alertmanager) are being dropped before ingestion to disk save on space and memory. Depending on how many servers we may or may not have in the future this could probably use some kind of overhaul since we rightnow have n^2 monitoring peer relationships (not even speaking of possible duplicated alerts).
2022-12-31 22:40:07 +01:00
}
],
Add adb and admin htpasswd user Also updated instructions for editing the .htpasswd
2023-01-03 16:07:00 +01:00
"lastmodified": "2023-01-03T15:04:58Z",
"mac": "ENC[AES256_GCM,data:4PTqDajceBpa2P/FCojNHIKbIDWpktIfID8x+M6cCCDm78yUcORnQhayQh6jnqx8BICD2tEtLZnaK/dkSgP15rlzPVeigkbLK7mcscJCPQKiVkAz7NghUvHK2humyd2ERsHd+vE8+lJ9TnLWap+nVamc0kTdWqgxJtm4w7MPP6s=,iv:PyfROMfOTP74hVlsVZIARe+0rlnFVyNEn4cmT1+Do44=,tag:MvUuLXDV5DkoY50FC5ELEg==,type:str]",
services/monitoring: Setup The goal is to create a monitoring setup where each server monitors itself when it comes failing systemd services, disk or RAM filling up, …. In addition each prometheus will monitor remote prometheus and alertmanager instances for signs of failure (e.g. being unreachable, errors in notification delivery, dropping alerts). A lot of metrics (especially histograms from prometheus or alertmanager) are being dropped before ingestion to disk save on space and memory. Depending on how many servers we may or may not have in the future this could probably use some kind of overhaul since we rightnow have n^2 monitoring peer relationships (not even speaking of possible duplicated alerts).
2022-12-31 22:40:07 +01:00
"pgp": [
{
hosts/hamilton: init
2023-08-12 11:02:30 +02:00
"created_at": "2023-08-12T09:40:00Z",
"enc": "-----BEGIN PGP MESSAGE-----\n\nwV4DOnsoj685gdcSAQdA1Ybc+5QxMtgirLjmBTsKh2qARuDxT/bbwsmwIsLC5i0w\nEJeP/A/uM+xQyidCNhGQTn5ummw2b6tEkbgsj0W+lw7rvpXmVv/fsmRUAd6Xle40\n0lEBygugsLr8Mxx2VtU0Q1zbUoAIE2Fmd4etqBQoDKUVsWzT4PQIrXxa1AO2psDK\nYRZ+urojM1PIviKHxUSTdx5iq1877QkMh1q6MwNdzd3bC7M=\n=0HCi\n-----END PGP MESSAGE-----",
Use full key fingerprint for e1mo in sops
2023-07-23 16:02:25 +02:00
"fp": "67BEE56343B6420D550EDF2A6D617FD0A85BAADA"
services/monitoring: Setup The goal is to create a monitoring setup where each server monitors itself when it comes failing systemd services, disk or RAM filling up, …. In addition each prometheus will monitor remote prometheus and alertmanager instances for signs of failure (e.g. being unreachable, errors in notification delivery, dropping alerts). A lot of metrics (especially histograms from prometheus or alertmanager) are being dropped before ingestion to disk save on space and memory. Depending on how many servers we may or may not have in the future this could probably use some kind of overhaul since we rightnow have n^2 monitoring peer relationships (not even speaking of possible duplicated alerts).
2022-12-31 22:40:07 +01:00
},
{
hosts/hamilton: init
2023-08-12 11:02:30 +02:00
"created_at": "2023-08-12T09:40:00Z",
"enc": "-----BEGIN PGP MESSAGE-----\n\nhQIMAxFMPvz46t7rAQ//d4UF77U2quxmZKgoCT/6I9qfO0EVPLklX9dvV9hWE3DS\niHDXBhbQEUiMWbHQMEM5xZOmayx95ljow3SQsB2ydPAmh/u56vN2Vi1iKj8dYZ90\nEc3OPJe6jx0uXN61h3jTA4Zd5fM6WfS4162YJE4qyCc+id6H9C4oQZUEKY9Yg1Lq\n7hXoVCYWz7E7fxc4hLyXXeK9PQNfzPkAZPA/nm5yc8fv6UNpmUdA1/TJapdjRYq5\n9krsPTksTyuiEu77HhL0MKXL2ohzN9nXbCSUSRMtVxUZLtcQ44NpW35RO26h3Vpi\ngmrT+mrpxW3oTBa+g9jiivQMHnn0o1xDPckMs3p4nSuSAJj6sNYIG5C0q3U+avRl\nSXbryfXebP0GezDFPduavOcJZ9XlGV3Oyrg7m2VZURK45muIcl0TFmSfr8FUE6dN\nul62w1qQXtVchh2xm1tu0a8nXI/1X9c1ciPbL8CZ88CQAFf9PLKHouef+bQnUdHU\n5qSleIehMKLI08PXDLvSgQW51boUJ3sqF97pPkWZIOFwzT6D2skN6Lflhdpugsbw\nc5qdDqSh+VpPJrlpaDgyCruCsypSFHb3NWOLW9wHL1mvFHCnNTbTX9rJz9/N/iFE\npQPjoEkYivayZ/VWW5oPAQ6YEnX4Mb30Je/Mj/piSBZSrdBMBEBYxh5ggME5GvbS\nXgFV/rYbKpW+KNtNZuwP9Z0bsocUfC96hnEAPRLLmhNIpAaUzU50lJD8XA7fZBOd\nlHe5c07iPyCqsiVrs4m+RVNmB7IULwr/L3gjTjAMxE4Z438nkrF4lrgO3wRzMV8=\n=mlBS\n-----END PGP MESSAGE-----\n",
services/monitoring: Setup The goal is to create a monitoring setup where each server monitors itself when it comes failing systemd services, disk or RAM filling up, …. In addition each prometheus will monitor remote prometheus and alertmanager instances for signs of failure (e.g. being unreachable, errors in notification delivery, dropping alerts). A lot of metrics (especially histograms from prometheus or alertmanager) are being dropped before ingestion to disk save on space and memory. Depending on how many servers we may or may not have in the future this could probably use some kind of overhaul since we rightnow have n^2 monitoring peer relationships (not even speaking of possible duplicated alerts).
2022-12-31 22:40:07 +01:00
"fp": "B1480CFF9BBE8E2648A26A640B2E7C171E3AD6D7"
Add mommes GPG key to sops
2023-07-23 16:01:04 +02:00
},
{
hosts/hamilton: init
2023-08-12 11:02:30 +02:00
"created_at": "2023-08-12T09:40:00Z",
"enc": "-----BEGIN PGP MESSAGE-----\n\nhF4DyBlv2iMmB8kSAQdA6svYhM1VtUlzZZBD2CUt7RpLMu/gEI7bvWuZZFMGlEUw\nEvg9ODjP9LqscGaE6Fg1XMRiseseuW2xLDfZ8cVI3DG90xmh9l85JqQV7QnZMjco\n1GgBCQIQXQfLSY7ASniqfJZvSIeEnOlig0thXhaRpkKXASS2Kjqt32rY5snFsVXi\nEt/j3h5Aay8MgSPE3yx3Jy4/43pMTuDbPfsaa5yE+4VmfKAHquJBQttrMU2QK5C2\nJTpLt9dwBvQFjg==\n=XsfZ\n-----END PGP MESSAGE-----\n",
Add mommes GPG key to sops
2023-07-23 16:01:04 +02:00
"fp": "5D22C6EC4A6E52469819B56D5EBCCEF2F33F7661"
services/monitoring: Setup The goal is to create a monitoring setup where each server monitors itself when it comes failing systemd services, disk or RAM filling up, …. In addition each prometheus will monitor remote prometheus and alertmanager instances for signs of failure (e.g. being unreachable, errors in notification delivery, dropping alerts). A lot of metrics (especially histograms from prometheus or alertmanager) are being dropped before ingestion to disk save on space and memory. Depending on how many servers we may or may not have in the future this could probably use some kind of overhaul since we rightnow have n^2 monitoring peer relationships (not even speaking of possible duplicated alerts).
2022-12-31 22:40:07 +01:00
}
],
"unencrypted_suffix": "_unencrypted",
"version": "3.7.3"
}
}
Reference in a new issue Copy permalink