Access node logs as an artifact #7375
Labels
area/archive-logs
Archive Logs feature
area/artifacts
S3/GCP/OSS/Git/HDFS etc
type/feature
Feature request
Summary
Accessing a nodes output via
steps.pipeline.outputs.result
works great when a node's stdout is simple, but it doesn't work as well when the stdout is volumous or is complex (for example, a traceback with lots of odd characters). It also does not include contents of stderr. It would be nice if it were also possible to access the stdout/stderr outputs of a node as an artifact (e.g. under something likesteps.pipeline.outputs.log_artifact
), which can then be shared with follow-up tasks to do processing on that, post it somewhere, or send out specialized notifications.To note, this is in principle possible already with the built-in artifacting system. But this requires first writing the logs to the external storage (e.g. S3), and then reading it back in in the next step. It would be nice if this was possible without leaving the k8s/argo domain.
Use Cases
When would you use this?
Message from the maintainers:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.
The text was updated successfully, but these errors were encountered: