Deployment Metrics

Chris Blyth's Avatar

Chris Blyth

16 May, 2017 11:56 AM


Our deployment has a lot of nuget steps (typically over 100) some of which deploy to multiple machines.
In an attempt to speed up our deployments we want to dig into actual deployments to try and find steps which take a long time to deploy.

We have recently upgraded to 3.13.0 and can see that on the task log each step/machine has a time to execute (attached)
However, this seems to include the time where the task is not actually running, but waiting on other tasks which effects the metrics i am trying to gather.
Whilst i agree that the UI is correct in terms of how long that block was running for (in this example it was nearly 5 minutes due to a 4 minute wait) is there a way to gather a metric on exactly how long each deployment step is taking (essentially how long it takes to run the deploy.ps1

Many thanks in advance for any assistance you can give!


  1. Support Staff 1 Posted by Vanessa Love on 17 May, 2017 10:23 AM

    Vanessa Love's Avatar

    Hi Chris,

    Thanks for getting in touch! Do you know about the full deployment logs? They give a bit more granular permissions.
    If you look under RAW logs as the option - it should assist in timing for each part of the step.
    Here is a doc image which shows where that toggle is:

    Please let me know if that is what you were looking for.

  2. 2 Posted by Chris Blyth on 19 May, 2017 08:35 AM

    Chris Blyth's Avatar

    Hi Vanessa,

    I am aware of the full deployment logs however, this makes it very difficult to try and analyse quite how long each part of our deployment process takes to identify where we can make improvements.

  3. Support Staff 3 Posted by Vanessa Love on 22 May, 2017 09:21 AM

    Vanessa Love's Avatar

    Hi Chris,

    We directly parse the logs to show the times you do see on the overview page, there is no other source of data im afraid.


  4. 4 Posted by Chris Blyth on 25 May, 2017 08:08 AM

    Chris Blyth's Avatar

    Hi Vanessa,

    Thanks for your feedback.

    I don't supose you will share your parsing code with us ;)

  5. Support Staff 5 Posted by Nick Josevski on 26 May, 2017 11:59 AM

    Nick Josevski's Avatar

    Hi Chris,

    That's cool what you're trying to do :)

    The parsing code isn't something easily shared, there's quite a lot to it as it's used to get all the information about the deployment. When we were implementing the timing display UI feature we factored in total running time, what you're trying to determine is the core work of the step that's a bit more parsing effort.

    I checked the API response it may have enough detail for what you want to calculate. But I suggest you double check for your deployments, if you go to the API route api/tasks/ServerTasks-<yourtasknumber>/details will return you a Task and it will have ActivityLogs, you'll see the LogElements array and it will have the entries, look for the script related ones like Deploying package or Making sure a Website or Executing script on and you can extract the OccurredAt times for those entries, and then subtract that time from the next step that starts after it, or if it's the last step then the time of The deployment completed successfully.

    If you determine the API call data doesn't have enough detail and you really want to parse the server logs, don't use the raw ones returned form the UI as they are already processed to a human readable format. In the Server\Tasks\ logging folder where Octopus runs, pick the files for the deployments you do want to analyse.

    The structure of each line is a comma delimited set of details.

    ["ServerTasks-2310_ABCDEF/STEP_LEVEL1_GUID/SECTION_GUID/ANOTHER_SECTION_GUID","INF","2017-05-25T13:11:52.6685530+00:00","Executing script on TEST","",0]

    You'll want to make use of "INF" or "VBS" only (and not "PLN" entries as they are created up front on creation - well before deployment happens). Again you're looking for the lines that represent the real start and end of processing effort you want to measure.

    Hope this helps.


Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:


Already uploaded files

  • Capture.PNG 26.5 KB

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac