Master commit 54e5a2327ed744e220aadceb9868e8a84e95b322
Add more information in debug mode to help determine what may be holding
up the agent metric collections.


test notes:
this is not very easy to test without manipulating the agent to hold up a metric collection.  a test plugin component with very slow metric reporting could help if you have that sort of thing in your bag of tricks.

To help test this you can now use the new "delay" property in the
pattern-generator plugin (attached).

The plugin was updated to allow for a delay when reporting metrics. This
allows the plugin to be used for "slow" collection reporting when
simulating an overloaded agent or misbehaving plugin.

For example, to see debug logging in the agent when metric collection is
falling behind try (after installing the plugin and importing the Pattern resource):

1) Update pattern2 collection interval to 40s so that the two pattern metrics
   are not collected at the same time, thus creating more load.
2) Set the new "delay" plugin config prop to 25.  So, each collection will
   take 25s, and quickly the agent will fall behind.

Created attachment 604640 [details]
pattern generator plugin

to help with testing

Created attachment 604962 [details]
agent.log

verified.

Message like attached log is being thrown in the logs.

Thanks a lot, Jay, for helping me with the case.

Bulk close of old bugs in VERIFIED state.