Handle errors gracefully in monitor to prevent crashes

[rickydebojeet]

Currently, the monitor in the repository does not handle errors gracefully, which can lead to complete crashes when unexpected conditions occur. Proper error handling in the monitor is required to ensure that errors are caught and managed without causing the monitor to crash.

Acceptance Criteria:

• Identify areas in the monitor code where unhandled exceptions or errors can occur.
• Implement appropriate error-handling mechanisms around risky operations.
• Log errors for debugging purposes without terminating the entire monitor process.
• Add tests to verify that the monitor continues running even when errors are encountered.

This will improve the reliability of the monitor.

[rickydebojeet]

Some of the error handling that needs to be done:

• When loading the configuration, proper checks should be added. For example, if no interface with the given name is found, it should show the error correctly and shouldn't crash.
• If no config file is loaded, then NFs asking for startup should be handled gracefully.
• All memory allocations should have corresponding free statements on errors; otherwise, memory leaks will exist.
• The variables which is always positive shouldn't use int variables.
• On crash, segfault in the application, the server shouldn't crash.
• The NIC configuration should be NIC independent.
• Load route should also configure the NIC ingress - configure where the packets should be redirected.

[arghyadipchak]

What's the update on these?

[rickydebojeet]

@adityakansara1, let's discuss this upcoming weekend.

[adityakansara1]

Sure

[arghyadipchak]

To be fixed in monitor-rs