[PUP-8511] Total time reported in report probably isn't reflective of reality Created: 2018/03/05  Updated: 2018/03/13  Resolved: 2018/03/13

Status: Closed
Project: Puppet
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: Melissa Stone Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relates to PUP-920 Add catalog application information t... Closed
Template: PUP Bug Template
Epic Link: Agent Run Report Improvements
Sub-team: Coremunity
Team: Platform Core
Method Found: Needs Assessment
QA Risk Assessment: Needs Assessment


Currently when we compile a report of the puppet run, we include a bunch of metrics on how long it took to run certain parts of the puppet run. This is great getting this information, but we also provide a total time metric. This total is simply the sum of all the other times reported in the report. I don't have a lot of faith this is wholly accurate of reality. It relies on the assumption that we've collected run times for all aspects of the puppet run, and none of the time reported are subsets of other times reported. I feel like there is a better way of determining the total time it took to run puppet, and the current way is is too naive for what we need. This is going to take more investigation to flush out exactly the best way to solve this, and if my hunch is totally wrong or not.


Comment by Melissa Stone [ 2018/03/13 ]

Dup of PUP-6344

Generated at Sat Jul 11 01:14:35 PDT 2020 using Jira 8.5.2#805002-sha1:a66f9354b9e12ac788984e5d84669c903a370049.