[OAK-4542] PerfLogger should also allow a threshold to log at INFO

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.0.33, 1.2.17, 1.4.5, 1.5.6, 1.6.0
• Labels: monitoring performance
• Assignee: Vikas Saurabh
• Reporter: Vikas Saurabh
• Created: 06/Jul/16 13:13
• Updated: 13/Jul/16 12:32
• Resolved: 12/Jul/16 11:55

Description

Currently, PerfLogger logs at DEBUG if time spent in operation is more that threshold ms.

We should also be able to have a second level threshold of time, beyond which the log should happen at INFO. It helps to catch cases for which the timing gets too poor at the onset of some performance issue and by the time of investigation (opportunity to add DEBUG logger) is too late already.

Issue Links

• is required by: OAK-4543 Add info about event generation and consumption by observer
• requires: OAK-3361 Reduce PerfLogger isDebugEnabled overhead