# Timestamps on build logs \[repeat request\] **URL:** \ **Category:** Product Feedback\ **Created:** [August 21, 2020, 5:07pm UTC](https://discuss.circleci.com/t/timestamps-on-build-logs-repeat-request/37173 "2020-08-21T17:07:41Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![vladistan](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/vladistan/32/25523_2.png) [@vladistan](https://discuss.circleci.com/u/vladistan)\ **Post date:** [August 21, 2020, 5:07pm UTC](https://discuss.circleci.com/t/timestamps-on-build-logs-repeat-request/37173/1 "2020-08-21T17:07:41Z")
This is a repeat request. Having timestamps on each line is essential for optimizing the build times. Both Jenkins and Go.CD had this feature for ever. I was advocating to switch our org to CircleCI from Traivs, I assumed you have such feature implemented. Unfortunately looks like my assumption was wrong. ---
**Author:** ![Kate\_Catlin](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/kate_catlin/32/22838_2.png) [@Kate\_Catlin](https://discuss.circleci.com/u/Kate_Catlin)\ **Post date:** [August 24, 2020, 9:14pm UTC](https://discuss.circleci.com/t/timestamps-on-build-logs-repeat-request/37173/3 "2020-08-24T21:14:39Z")
Hi @vladistan thanks for posting! I don’t see another post from you but welcome to our community. Can you tell me more about where you’re trying to see timestamps? And do you mean timestamp as in “what time/date this ran” or “how long it took to run”? Hope we can help you out! ---
**Author:** ![vladistan](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/vladistan/32/25523_2.png) [@vladistan](https://discuss.circleci.com/u/vladistan)\ **Post date:** [August 24, 2020, 9:31pm UTC](https://discuss.circleci.com/t/timestamps-on-build-logs-repeat-request/37173/4 "2020-08-24T21:31:57Z")
Here is the other post, it was not by me but by another user: [Timestamps on build logs](https://discuss.circleci.com/t/timestamps-on-build-logs/13591/2) What I am looking for is just to have a time and date on each line of the build log showing when this line was printed. Something like this Jenkins plugin below: > **[Timestamper](https://plugins.jenkins.io/timestamper/)** > > Adds timestamps to the Console Output ---
**Author:** ![dijitali](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/dijitali/32/21063_2.png) [@dijitali](https://discuss.circleci.com/u/dijitali)\ **Post date:** [October 22, 2020, 4:28pm UTC](https://discuss.circleci.com/t/timestamps-on-build-logs-repeat-request/37173/5 "2020-10-22T16:28:40Z")
I’d echo this request. Currently we’re prepending the following to various bash commands to give us line-by-line timestamps of when commands ran to help with debugging and generally give more context when reviewing build/deployment logs: ``` date -u +"%Y-%m-%dT%H:%M:%SZ" ``` ---
**Author:** ![drichelson](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/drichelson/32/13382_2.png) [@drichelson](https://discuss.circleci.com/u/drichelson)\ **Post date:** [April 30, 2021, 5:20pm UTC](https://discuss.circleci.com/t/timestamps-on-build-logs-repeat-request/37173/6 "2021-04-30T17:20:53Z")
+1000 just now I am debugging a super long docker build step and line by line timestamps would be amazing! ---
**Author:** ![ekulabuhov](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/ekulabuhov/32/29178_2.png) [@ekulabuhov](https://discuss.circleci.com/u/ekulabuhov)\ **Post date:** [January 18, 2022, 4:40pm UTC](https://discuss.circleci.com/t/timestamps-on-build-logs-repeat-request/37173/7 "2022-01-18T16:40:57Z")
This would be super useful when optimizing the build time. ---
**Author:** ![ryanmckay](https://avatars.discourse-cdn.com/v4/letter/r/4bbf92/32.png) [@ryanmckay](https://discuss.circleci.com/u/ryanmckay)\ **Post date:** [September 6, 2022, 8:44pm UTC](https://discuss.circleci.com/t/timestamps-on-build-logs-repeat-request/37173/8 "2022-09-06T20:44:14Z")
Yes please, same thing I want to see what is taking so long in a long-running docker build. I also used this feature in Jenkins and found it very useful. ---
**Author:** ![gonzaloserrano](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/gonzaloserrano/32/28727_2.png) [@gonzaloserrano](https://discuss.circleci.com/u/gonzaloserrano)\ **Post date:** [January 19, 2023, 4:03pm UTC](https://discuss.circleci.com/t/timestamps-on-build-logs-repeat-request/37173/9 "2023-01-19T16:03:26Z")
hey @KateCatlin, we are very interested in this to debug timing issues, i.e, why things take long to execute. Are the specs clear enough? Is this something that you have in your backlog? Thanks ---
**Author:** ![kstech-roadie](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/kstech-roadie/32/32194_2.png) [@kstech-roadie](https://discuss.circleci.com/u/kstech-roadie)\ **Post date:** [January 27, 2023, 3:02pm UTC](https://discuss.circleci.com/t/timestamps-on-build-logs-repeat-request/37173/10 "2023-01-27T15:02:43Z")
+1 need this feature ---
**Author:** ![agrawaltarun](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/agrawaltarun/32/32231_2.png) [@agrawaltarun](https://discuss.circleci.com/u/agrawaltarun)\ **Post date:** [February 1, 2023, 6:25am UTC](https://discuss.circleci.com/t/timestamps-on-build-logs-repeat-request/37173/11 "2023-02-01T06:25:00Z")
Any update on this feature request. This will be really helpful for us as well. ---
**Author:** ![arigesher](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/arigesher/32/2534_2.png) [@arigesher](https://discuss.circleci.com/u/arigesher)\ **Post date:** [April 10, 2023, 11:36pm UTC](https://discuss.circleci.com/t/timestamps-on-build-logs-repeat-request/37173/12 "2023-04-10T23:36:25Z")
This may be useful to others: one can use a bit of shell piping to get timestamps, as outlined here: > **[Add Timing Data to Each Output Line](https://support.circleci.com/hc/en-us/articles/360053200971-Add-Timing-Data-to-Each-Output-Line)** > > Timing Data > Debugging where jobs spend most of their time can be useful in optimizing your pipeline, along with debugging spikes in job completion time. > Example > Generally, logging timing data is up... tl;dr `- run: example_command | while read line; do echo "$(date +%T) > $line"; done;` ---
**Author:** ![pwillis-eiq](https://avatars.discourse-cdn.com/v4/letter/p/9dc877/32.png) [@pwillis-eiq](https://discuss.circleci.com/u/pwillis-eiq)\ **Post date:** [July 19, 2023, 5:41pm UTC](https://discuss.circleci.com/t/timestamps-on-build-logs-repeat-request/37173/13 "2023-07-19T17:41:14Z")
Still no timestamps? Wow. How is this not a 5-line change for a very useful feature? ---
**Author:** ![emilycook](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/emilycook/32/31613_2.png) [@emilycook](https://discuss.circleci.com/u/emilycook)\ **Post date:** [July 19, 2023, 6:14pm UTC](https://discuss.circleci.com/t/timestamps-on-build-logs-repeat-request/37173/14 "2023-07-19T18:14:38Z")
Feature requests have moved to our platform on canny. It seems we have one already open for this – please go vote for it and write comments if it’s something you would like to see prioritized > **[Add option to Jobs to automatically Timestamp build logs with elapsed time or...](https://ideas.circleci.com/cloud-feature-requests/p/add-option-to-jobs-to-automatically-timestamp-build-logs-with-elapsed-time-or-ut)** > > While CCI allows you to separate builds into steps, it's very common to find that a singular step is multi-phased itself.