Loki sert son API en HTTPS via le cert step-ca (http_tls_config + cert-sync owned loki, motif .path). Alloy pousse en https + tls_config (ca=root_ca). Vars : serveur_loki_tls_actif, client_journal_loki_tls. Prouvé : Loki HTTPS /ready 200 (vérif root_ca), HTTP rejeté (400), 4 hôtes expédient des logs en https, 0 erreur loki.write après la transition. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
19 lines
776 B
YAML
19 lines
776 B
YAML
---
|
|
client_journal_paquets:
|
|
- alloy
|
|
|
|
client_journal_service: "alloy"
|
|
client_journal_utilisateur: "alloy"
|
|
client_journal_config: "/etc/alloy/config.alloy"
|
|
|
|
# Point de collecte Loki (obs-01, serveur_loki, VLAN 14).
|
|
client_journal_loki_url: "http://10.0.14.11:3100/loki/api/v1/push"
|
|
|
|
# Depot apt officiel Grafana (partage avec serveur_loki / serveur_grafana).
|
|
client_journal_depot_cle_url: "https://apt.grafana.com/gpg-full.key"
|
|
client_journal_depot_cle_fichier: "/etc/apt/keyrings/grafana.asc"
|
|
client_journal_depot_source: "deb [signed-by=/etc/apt/keyrings/grafana.asc] https://apt.grafana.com stable main"
|
|
|
|
# --- TLS (zero-confiance) : Alloy pousse vers Loki en https + verifie root_ca ---
|
|
client_journal_loki_tls: false
|
|
client_journal_loki_ca: "/etc/step/certs/root_ca.crt"
|