dannygroenewegen
changed title from Update scape-config example to use HTTPS for Traefik metrics to fix: Update scape-config example to use HTTPS for Traefik metrics2026-03-20 19:23:32 +00:00
3. The scape-config.example.yml file and add_node() command were updated to use a secure endpoint for the traefik metrics instead http. This requires an updated Traefik recipe that publishes the metrics on https.
The message to update the scrape_configs is in the Traefik release notes. Updating Traefik is the moment the endpoint changes, and when you should update the configs. I think that's the right spot? Only updating monitoring-ng would not require changing existing scrape_configs
The message to update the scrape_configs is in the Traefik release notes. Updating Traefik is the moment the endpoint changes, and when you should update the configs. I think that's the right spot? Only updating monitoring-ng would not require changing existing scrape_configs
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This fixes the insecure Traefik metrics endpoint. See coop-cloud/traefik#94 for details.
Update scape-config example to use HTTPS for Traefik metricsto fix: Update scape-config example to use HTTPS for Traefik metrics@@ -6,2 +6,4 @@COMPOSE_FILE="$COMPOSE_FILE:compose.grafana-smtp.yml"3. The scape-config.example.yml file and add_node() command were updated to use a secure endpoint for the traefik metrics instead http. This requires an updated Traefik recipe that publishes the metrics on https.Could you add something like: make sure to update your existing scrape_configs to use the secure endpoint
The message to update the scrape_configs is in the Traefik release notes. Updating Traefik is the moment the endpoint changes, and when you should update the configs. I think that's the right spot? Only updating monitoring-ng would not require changing existing scrape_configs