[JENKINS-38313] External Build Log storage for Jenkins

[timja]

Jenkins' logging system is one of potential scalability bottlenecks on big Jenkins instances. System logging can be redirected via JUL log appenders (or other such solutions), but there is no OOTB solution for build logs.

It would be great to have such solution. Top-level requirements:

• All or almost all build/task logging is moved from Jenkins filesystem to External Build Log Storage
• Minimize log traffic between Jenkins agents and the master, logs should be reported from slaves directly when it is possible
• External Build Log Storage has an extensible and pluggable architecture
• At least 2 reference implementations:
  • File-system-based storage (current implementation)
  • One external build log storage based on the open-source stack. Preference - Elasticsearch-Logstash-Kibana
• Jenkins Pipeline is supported out of the box
• Old logs should be browseable after changing the storage engine (Migration or parallel engines)

Design document:

• https://docs.google.com/document/d/1_bquSeA_lC7zJhQoWhxlSKJAg6b8duNbyQ15zCz-e4Y/edit#

---

Originally reported by oleg_nenashev, imported from: External Build Log storage for Jenkins

• status: In Progress
• priority: Major
• resolution: Unresolved
• imported: 2022/01/10

Epic children:

• 10004

• 10004

• 10004

• 9979

• 9980

• 9985

• 9998

• 10004

[timja]

oleg_nenashev:

I am not working on these stories anymore. I have been assigned to another project in October by my company

[timja]

oleg_nenashev:

jamesdumay This EPIC includes Changes in Pipeline, e.g. JENKINS-38381. Please do not remove labels/components

[timja]

postman:

Is there any idea when this could be ready? We've started to use pipelines and immediately ran into issues with the Jenkins system incurring a massive increase in IOPS (the master has build log storage on external filer).

Is there any short-term recommended workaround?

 

[timja]

oleg_nenashev:

postman Regarding Pipeline, see JENKINS-38381. jglick made a significant progress with the log storage improvement there (with/without external storage), but the pull request has not been landed yet afaik

[timja]

oleg_nenashev:

This EPIC is in progress again

[timja]

oleg_nenashev:

And... it was aborted again for some reasons out of my control...

[timja]

oleg_nenashev:

I have abandoned all tasks in this EPIC. As stated in https://groups.google.com/d/msg/jenkinsci-dev/uc6NsMoCFQI/AIO4WG1UCwAJ , csanchez and jglick can take over any tasks, PRs and JEPs related to this EPIC

[timja]

datadog:

Hi csanchez and jglick, we are wondering about the current status of this EPIC? We are interested in using this logging capability, and we would like to know if this is continued to be supported even in beta?

[timja]

jglick:

datadog nothing is “supported” exactly, but https://plugins.jenkins.io/pipeline-cloudwatch-logs/ continues to work (AFAIK), and JEP-210 is open to other implementations (beta-level API). At a very high level, the main limitations are

• There is no support for non-Pipeline projects.
• Pending JENKINS-52165, an implementation needs to turn on a log streaming implementation for sh-like steps which does not otherwise get much testing.
• Pending API changes to Jenkins core (incl. Stapler) and matching changes in Blue Ocean, in-Jenkins log display for running builds is inefficient. (Uses a byte offset cursor rather than an implementation-defined cursor that could be implemented efficiently.)

[timja]

[Originally duplicated by: JENKINS-32444]

[timja]

[Originally related to: JENKINS-45150]

[timja]

[Originally related to: JENKINS-26545]

[timja]

[Originally blocks: JENKINS-49327]