Ability to view the full step logs
long-term
E
Elderly Quail
Currently the step logs are getting truncated when it is exceeding a size of 5MB. The workaround suggested to save the script output to a file and make it available in an object store is not helpful and having issues using this workaround in the run test step. We should be able to see the full step logs even if it is exceeding the sizes of 5MB
Log In
Canny AI
Merged in a post:
Increase the log size limit and lines of logs for CD steps
U
Umber Hedgehog
Increase log size and line limits for CD steps. The situation is like - We are hitting a 5000 terminal buffer line limit, we can hit 10000 lines too in some situations. We also have no logs available for the pipeline execution which means we lost important data.
Canny AI
Merged in a post:
Full Logs in Console without Truncation
I
Ivory Starfish
In the UI when viewing the logs on a job, on our long runs its being truncated and not showing the full logs. We would like the full logs to be shown in the UI for our Devs to review easily without having to navigate to another application.
example of truncation:
Canny AI
Merged in a post:
Provide a way to view complete rendered manifest in UI
R
Representative Llama
In first gen the rendered manifest was shown completely in the logs. However in the next gen due to log line length limitation , if manifest is bigger this gets truncated.
This enhancement request is for providing a way to view the complete rendered manifest in the UI.
I
Iron grey Chicken
Rohan Gupta please share latest update on this request since it was marked in-progress ~6 months back
N
Nofar Bluestein
Merged in a post:
CI Log Truncation
I
Indigo Wolverine
Information below taken from an email from Aaron. Victoria's Secret is running into an issue with CI step log truncation.
"I see a hard cap of 5MB listed here https://developer.harness.io/docs/continuous-integration/troubleshoot-ci/troubleshooting-ci/ and no other answers as far as I can search.
If they expire sooner than normal based on their size, that could be acceptable. But it’s extremely frustrating to lose the beginning info from an execution before it’s even completed."
Just one example, and it isn’t an exceptionally verbose log, just a build step that logs one line for each of the 230k files it builds.
Prateek Mittal
Hi Kelly,
I checked the execution of the pipeline, and it is displaying 26942 lines of logs. Do you know if the truncation is happening at the starting of the logs or at the end of logs? And what was the expected log size?
Thanks,
Prateek
Pranav Rastogi
Merged in a post:
Ability to view the logs more than 5000 lines
E
Ethical Grasshopper
CUrrently Harness log service has a limit of 5000 lines as per https://developer.harness.io/docs/continuous-delivery/manage-deployments/deployment-logs-and-limitations/
Logs rendered in the Harness UI are truncated from the top if the logs exceed the 5000 line limit.
This limit would not be enough for us hence please provide an option to change this limit to a higher value.
Pranav Rastogi
long-term
R
Relaxed Pinniped
Pranav Rastogi The 5000 line limit for deploy logs has forced us to write output to a log file then push to s3 for retrieval from Harness. This is an added expense for storage now.