Raise exception if exit code is not 0 in container monitoring port parsing

Cage, Gregoryrequested to merge
135-raise-exception-monitor into dev

Summary of Changes

Opening this for now. Not sure if this is going to fix all issues. From testing locally, the container monitor seemed to stop. On the sns node, it was unclear if this helped to be honest. Some of the attempts from yesterday are no longer there. But the monitoring seemed to last for a while even with this change...

Checklist

  • The MR has a clear and concise title
  • Code is self-documented and follows style guidelines.
  • Automated tests are written and pass successfully.
  • Regression tests (e.g. manually triggered system tests, manual GUI/tool tests, ...) are performed to make sure the MR does not break anything (when applicable)
  • Readme file is present and up-to-date.

Documentation Updates

Additional Notes

Closes #135 (closed)

Merge request reports