Still sending Error alerts

Somehow, this code block (even though it is just a print statement) is still appears as an error in our [alerts channel](https://gnosisinc.slack.com/archives/CQZBU9T5J/p1634648776005300).

I have also [checked with devops](https://gnosisinc.slack.com/archives/C6Z2XNL5Q/p1634651393239300) to see if they have some of their own triggers for such alerts (like any string containing "failed" or something).

https://github.com/gnosis/etherbalance/blob/c13d061ccce45ad7ed2dfa09cfe1d60c5afee1f1/src/main.rs#L151-L161

Start by inspecting src/main.rs around lines 151-161 and reproduce how that print statement reaches the alerts channel. Compare the emitted output with the linked Slack alert and the DevOps trigger context. Done means the statement no longer produces an Error alert when its behavior is otherwise unchanged.

Written by the indexing model from the issue text.