Resource processor porter install logs are frequently truncated in log analytics #3992
Labels
bug
Something isn't working
Comments
marrobi
added a commit
that referenced
this issue
Aug 1, 2024
Related to #3992 Modify the `shell_output_logger` function in `resource_processor/shared/logging.py` to split lengthy log outputs into smaller chunks before logging. * **Chunk Log Output**: - Add `chunk_log_output` helper function to split the log output into smaller chunks. - Update `shell_output_logger` to use `chunk_log_output` for logging lengthy outputs in chunks. * **Tests**: - Add `test_shell_output_logger_chunked_logging` to verify chunked logging functionality. - Add `test_chunk_log_output` to test the `chunk_log_output` helper function. --- For more details, open the [Copilot Workspace session](https://copilot-workspace.githubnext.com/microsoft/AzureTRE/issues/3992?shareId=XXXX-XXXX-XXXX-XXXX).
|
Closed in #4048 |
github-project-automation
bot
moved this from In Progress
to Done
in Azure TRE - Engineering
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When the resource processor installs a porter image, the logs include lengthy terraform which is often over the maximum field size for Log Analytics, resulting in truncated data.
If you're trying to determine why a component has failed to install, the error is generally at the bottom, hence its not helpful to have truncated output.
The text was updated successfully, but these errors were encountered: