Metric clarification

3 comments

• 
  Martin Kretzschmar May 16, 2024 11:01 Official comment

  Hi Adam,

  TotalBootTimeMs (uberAgent:OnOffTransition:BootDetail2) and TotalBootDurationMs (uberAgent:OnOffTransition:BootProcesses) contain the same value. We just need them in different sourcetypes for visualization purposes and dashboard performance.

  Further details can be found here.

  Thanks
  Martin

• 0
  
  Adam Bizzer May 17, 2024 07:25

  Hey Martin, thank you very much for your answer!
  
  Does TotalBootDurationMs include AD login time?
  What metrics can we use, to rule out someone going for coffee?
  We want to completely rule out human elements, we are only interested in the machines and log on server's performance metrics.
  How can we exclude login time from the machine boot up process, until we get to desktop?
  What are the good fields for identifying issues related to slow start up and log in process?
  
  Cheers,
  Adam

• 0
  
  Martin Kretzschmar May 17, 2024 13:35

  Hi Adam,

  Let me break down the values:

  TotalBootDurationMs

  The time from Windows start to the desktop being shown and the system reaching an 80% idle state.
  This is the sum of MainPathBootTimeMs and PostBootTimeMs. If TotalBootTimeMs is empty, it means that Windows stopped collecting data too early, or because the user waited longer before logging in.

  MainPathBootTimeMs

  From the beginning to the start of the shell (typically explorer.exe).
  The user has successfully logged in, and the shell is starting.

  PostBootTimeMs

  From shell start to the system reaching an 80% idle state. This time is accumulated by checking the CPU and storage utilization in 500ms time windows. If the cumulative time of both CPU and storage utilization is below 20%, the idle time of this window (500ms – max [CPU time, Disk time] in the window) is added to the total idle time until 5 seconds is reached. The metric reports this duration minus the 5 seconds of collected idle time. The desktop is now ready to use.

   

  So yes, TotalBootDurationMs includes AD logon time, but if you're interested in the actual user logon duration, there are dedicated sourcetypes for that (docs), with detailed breakdowns.

  To exclude "coffee times" you can look at:

  UserLogonWaitDurationMs

  The measurement starts with the welcome display screen, thus as soon as the user can perform a login. It stops with the successful login.

   

  I hope that helps

  Thanks
  Martin