@p4u1 could you resolve the merge conflicts from main again? i just tested it and it loads, haven't had an alert yet
done
actually not sure where these alerts are sent!
hmm, for us it works
> @p4u1 could you resolve the merge conflicts from main again? i just tested it and it loads, haven't had an alert yet
done
> actually not sure where these alerts are sent!
hmm, for us it works
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.
b85b53223dtof1b88a1546this is very useful, thanks! i didn't know about apdex
@@ -174,6 +174,7 @@ It is possible to enable the following alerts, by uncommenting the corresponding- node disk space: `ALERT_NODE_DISK_SPACE_LEFT`- node memory usage: `ALERT_NODE_MEMORY_USAGE`<<<<<<< Updated upstreamyou have merge conflicts commited over here!
@@ -182,3 +183,6 @@ To be able monitor hard drive health data, you need to configure`collect-smartctl-json.sh` script provided here (via cronjob or asa `smartd` hook). This is a limitation on Docker Swarm, which preventsthe `smartctl_exporter` from running on privileged mode.=======here too
@@ -184,1 +185,4 @@the `smartctl_exporter` from running on privileged mode.=======- traefik apdex: `ALERT_TRAEFIK_APDEX`>>>>>>> Stashed changesand here
@@ -11,2 +11,4 @@export MATRIX_ALERTMANAGER_ENTRYPOINT_VERSION=v1export GF_ALERTS_NODE_VERSION=v3<<<<<<< Updated upstream=======in this file too
@@ -24,6 +24,13 @@ services:target: /var/lib/grafana/dashboards/backup.json- source: gf_alerts_nodetarget: /etc/grafana/provisioning/alerting/node.yml<<<<<<< Updated upstreamin this file too
woops, resolved all merge conflicts
@p4u1 could you resolve the merge conflicts from main again? i just tested it and it loads, haven't had an alert yet
actually not sure where these alerts are sent!
done
hmm, for us it works