v-m: Do not scrape/alert on Graylog
Graylog is down because Elasticsearch corrupted itself again, and this time, I'm just not going to bother fixing it. I practically never use it anymore anyway, and I want to migrate to Grafana Loki, so now seems like a good time to just get rid of it.etcd
parent
380af211ec
commit
1f28a623ae
|
@ -33,13 +33,6 @@ groups:
|
|||
collectd_processes_ps_count_processes{processes=~"samba|smbd|winbindd|krb5kdc"} < 1
|
||||
for: 5m
|
||||
|
||||
- name: Graylog
|
||||
rules:
|
||||
- alert: unprocessed messages
|
||||
expr: >-
|
||||
org_graylog2_journal_entries_uncommitted > 100
|
||||
for: 1h
|
||||
|
||||
- name: mdraid
|
||||
rules:
|
||||
- alert: mdraid missing disk
|
||||
|
|
|
@ -186,16 +186,6 @@ scrape_configs:
|
|||
- targets:
|
||||
- homeassistant.pyrocufflink.blue
|
||||
|
||||
- job_name: graylog
|
||||
scheme: https
|
||||
metrics_path: /api/plugins/org.graylog.plugins.metrics.prometheus/metrics
|
||||
basic_auth:
|
||||
username: %{SCRAPE_GRAYLOG_TOKEN}
|
||||
password: token
|
||||
static_configs:
|
||||
- targets:
|
||||
- graylog.pyrocufflink.blue:443
|
||||
|
||||
- job_name: gitea
|
||||
scheme: https
|
||||
static_configs:
|
||||
|
|
Loading…
Reference in New Issue