Conversation
0xfornax
left a comment
There was a problem hiding this comment.
We either have both clients running locally or externally managed so the code could be simplified and a few tests removed.
|
I actually disagree with the premise here. Low disk space alerts are important, even for VC-only machines. They have a tendency to fill up with logs or docker images- and when they do fill up, clients can't write-ahead to slashing protection databases and stop attesting. It seems to me that the However, |
fixed d6b3398 |
I agree it is a better idea to keep the critical disk space alerts and adjust the threshold. To simplify things I reverted the changes about the disk space alerts and will just focus on the port checks since it is a more obvious problem & solution. |
This PR limits some of the alerts that appear when your EC/CC are externally managed. Critical warnings about ports that aren't open aren't applicable in an externally managed configuration. For port warnings, the configuration is checked in the code that checks for port connectivity.
Tested via new unit tests