[PDB-3096] log time elapsed for command processing Created: 2016/10/12  Updated: 2017/04/14  Resolved: 2017/03/29

Status: Closed
Project: PuppetDB
Component/s: None
Affects Version/s: None
Fix Version/s: PDB 4.4.0

Type: New Feature Priority: Normal
Reporter: Wyatt Alt Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Blocks
Relates
Template:
Team: Systems Engineering
Story Points: 1
Sprint: PuppetDB 2017-04-05

 Description   

This would allow you to tie an intermittent slow processing issue to specific nodes very easily.



 Comments   
Comment by Ryan Senior [ 2016/10/31 ]

Info level of logging is fine here, with the certname and the processing time

Comment by Charlie Sharpsteen [ 2016/12/15 ]

Currently we log a message at info level after each command is processed that includes the certname and the command type. It would be awesome if this message also included the elapsed processing time and command size.

Comment by Susan McNerney [ 2017/04/04 ]

If this was approved for 4.2.3.2 would it be able to make it into the release that will take place by April 19? Russell Mull Ryan Senior

Comment by Russell Mull [ 2017/04/05 ]

Susan McNerney Yep. The backport should be very easy.

Comment by Susan McNerney [ 2017/04/06 ]

Approved for 4.2.3.2/PE 2016.4.4 by the Davis leads.

cc Karen Van der Veer Russell Mull

Comment by Karen Van der Veer [ 2017/04/06 ]

Susan McNerney What more is there to do on a resolved ticket?

Comment by Russell Mull [ 2017/04/06 ]

Karen Van der Veer This is fixed in 4.4, we're going to backport it to LTS.

Comment by Adam Bottchen [ 2017/04/07 ]

Created https://tickets.puppetlabs.com/browse/PE-20261 to track the potential backport effort, since this ticket is closed.

Generated at Thu Nov 14 10:44:02 PST 2019 using JIRA 7.7.1#77002-sha1:e75ca93d5574d9409c0630b81c894d9065296414.