# Jenkins build logs aggregation valuable? **URL:** \ **Category:** Using Jenkins\ **Created:** [August 3, 2022, 12:29pm UTC](https://community.jenkins.io/t/jenkins-build-logs-aggregation-valuable/3249 "2022-08-03T12:29:20Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![barceloniak1](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/barceloniak1/32/1507_2.png) [@barceloniak1](https://community.jenkins.io/u/barceloniak1)\ **Post date:** [August 3, 2022, 12:29pm UTC](https://community.jenkins.io/t/jenkins-build-logs-aggregation-valuable/3249/1 "2022-08-03T12:29:20Z")
Guys, I am looking for strong advice about solution to monitor jenkins build logs. I do have in place monitoring jenkins app logs and all functional data related to running the jenkins on the infra. However, some people come into the conclusion to ship logs from builds, as well. In very complex setup is not worth to perform such action, due to the fact that each case is different (mostly) + cost efficiency about storing them on RDS in AWS(massive). Idea of monitoring is to catch up the trends and metrics related or infra app layer from functional point of view, do you agree ? Based on, theory that is need to monitor build logs, means cost are massive + filters are not so unique and you need to deep dive to troubleshoot, anyway. Effort become pointless. Have you heard about consideration, previously such a thing ? What tools might be useful ? Thanks for discussion. ---
**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\ **Post date:** [August 3, 2022, 1:00pm UTC](https://community.jenkins.io/t/jenkins-build-logs-aggregation-valuable/3249/2 "2022-08-03T13:00:10Z")
Several different groups are finding ways to more widely use the logs from Jenkins jobs. You might consider their approaches in your investigation. The [OpenTelemetry plugin](https://plugins.jenkins.io/opentelemetry/) can export Jenkins build logs to storage and analysis services like ElasticSearch, Jaeger, and more. @darinpope has created a video that shows how to use OpenTelemetry and Jaeger to trace Jenkins pipelines. [![](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/6/6f64ea06c9bd08716e97cdeee21eaed0d814e531.jpeg "Tracing Your Jenkins Pipelines With OpenTelemetry and Jaeger") ](https://www.youtube.com/watch?v=3XzVOxvNpGM) Elastic includes a section on CI/CD observability in their documentation > **[CI/CD | Elastic Docs](https://www.elastic.co/docs/solutions/observability/cicd)** > > To help administrators monitor and troubleshoot their CI/CD platform and help developers increase the speed and reliability of their CI/CD pipelines,... [Logz.io](http://Logz.io) has a blog post that describes their use of observability on their CI/CD Pipelines: > **[Monitor Jenkins & CI/CD in 4 Steps](https://logz.io/learn/cicd-observability-jenkins/)** > > See how to add observability to CI/CD pipelines in Jenkins, enhancing build reliability and issue detection. ---
**Author:** ![barceloniak1](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/barceloniak1/32/1507_2.png) [@barceloniak1](https://community.jenkins.io/u/barceloniak1)\ **Post date:** [August 3, 2022, 2:01pm UTC](https://community.jenkins.io/t/jenkins-build-logs-aggregation-valuable/3249/3 "2022-08-03T14:01:03Z")
@MarkEWaite That’s true, the conclusion from @darinpope . However, would name it more user friendly interface in Jaeger + time tracker add-on. Nevertheless, re-writing pipeline in my case, as outcome of implementation would be case to address to an author of the pipeline. That also make sense, not sure if people would react even on data provided to them, about produced problem by them. Nothing to carry on that thread. In very short, looking for advantages of this implementation shared by you. I am seeing -measuring the time of particular step in the pipe + - evaluation of interface, but manual action is required anyway for review. ---
**Author:** ![Anshika](https://avatars.discourse-cdn.com/v4/letter/a/ea5d25/32.png) [@Anshika](https://community.jenkins.io/u/Anshika)\ **Post date:** [May 16, 2024, 9:14am UTC](https://community.jenkins.io/t/jenkins-build-logs-aggregation-valuable/3249/4 "2024-05-16T09:14:09Z")
Hey @MarkEWaite I was recently setting up Cloudbees CI rather than Jenkins-LTS. I was following the video which you shared and did follow all the steps. The traces for opentelemetry plugin is not getting generated for cloudbees CI and working for jenkins-LTS. Opentelemetry plugin is there in its marketplace. version - [ 3.1138.v80fc844ed246Latest on Mar 18 ](https://github.com/jenkinsci/opentelemetry-plugin/releases/tag/3.1138.v80fc844ed246)