about summary refs log tree commit diff
path: root/modules/services/monitoring (follow)
Commit message (Collapse)AuthorAgeFilesLines
* profiles/monitoring: a bunch of fixesFranck Cuny2023-05-121-1/+1
|
* profiles/loki: fix a few configuration errorsFranck Cuny2023-05-121-1/+1
|
* profiles/monitoring: move loki to a profileFranck Cuny2023-05-122-113/+0
| | | | | Add a nginx virtualhost for loki too, so that we can use a valid SSL certificate.
* profiles/monitoring: move promtail to a profileFranck Cuny2023-05-122-66/+0
|
* profiles/monitoring: move node exporter to a profileFranck Cuny2023-05-122-20/+0
|
* profiles/nginx: move common configuration to a profileFranck Cuny2023-05-091-0/+11
| | | | | | Both tahoe and carmel are using nginx, and we can simplify the configuration by moving common parts to the profile and have these hosts import it.
* profile/acme: default DNS provider is gandiFranck Cuny2023-05-081-8/+3
| | | | | | | | | | Add the API key for gandi to the secrest, create a profile for acme with my defaults. The profile is loaded by tahoe since that's where our services are running on. Update all the servers in nginx to listen on their wireguard interface.
* modules/monitoring: set the host's name as a label for promtailFranck Cuny2023-04-231-2/+2
|
* hosts/tahoe: loki and prometheus listen only on the wg0 interfaceFranck Cuny2023-04-233-7/+33
| | | | | | | I don't want to have to deal with authentication and TLS certificates for these endpoints. If they are only listening on the wireguard interface I can trust that only authorized hosts are sending traffic to these endpoints. I trust what's running on these machines.
* modules/monitoring: consolidate all monitoring services togetherFranck Cuny2023-04-237-0/+14539
This will help to organize and structure monitoring modules a bit better.