Grafana alerting: ignore alerts for failing to append Stacks block #0

[MicaiahReid]

When Chainhook fails to ingest a stacks block, it logs the error Unable to process Stacks Block #..., which causes an S4 alert in Grafana.

We do want to be aware of Chainhook failing to ingest a block, but there are some cases where it's tedious. For example, whenever the Stacks blockchain restarts, it emits a block #0. We shouldn't be handling this block, so we shouldn't log an error. We should implement some custom way to prevent this block from logging errors, or we should create a rule in Grafana to avoid causing alerts for this.

[MicaiahReid]

Or perhaps we need to investigate why the stacks node is sending us this block in the first place.