Logs previous exception if present #1097
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previous exception messages are now also listed. Before it was easily masked what the true cause of the error was.
It could happen, that the container did not boot correctly and then the metrics could not be read also. However as error only the fail in reading the metrics was reported.
This is now changed from:
To:
Greptile Summary
Enhanced error logging across the application by including previous exception information, improving the ability to diagnose root causes of cascading failures, particularly for container boot and metric reading issues.
previous_exception=exc.__context__
parameter in error logging calls throughout/cron/client.py
/api/main.py
and/runner.py
changes