Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Configure alerter with 0x API Key (#2164)
# Description I was looking into why we did not receive an emergency alert during the MEVBlocker outage last week. It turns out that our alert pod broke when 0x started requiring API keys. As a consequence, all our API calls received 401 errors and we thus didn't identify any solutions as unsettleable. This issue was raises as an alert in the barn alert channel (since the alerter itself only runs in staging), but didn't catch attention. It didn't show up before, because the alerter only attempts to query 0x when there are no settlements for a longer period of time (which usually doesn't happen). Therefore this issue could only be identified when an outage was actually in progress. This PR focusses on fixing the use of the 0x API. I think we should also revisit how we ensure that the alert pod is working correctly, but I don't have a great idea how off the top of my head. Maybe we can log "error" into a metric which itself could be used for prod or emergency alerts. # Changes - [ ] Configure binary with a mandatory API key and use this in 0x requests ## How to test Local curl test that the query with the correct API key set returns 200 instead of 401
- Loading branch information