| commit | 695da0b90ff32e53c080e7666d07cac1f3065af1 | |
| author | Nathan Scott <nathans@redhat.com> | |
| Fri, 24 Jun 2016 05:01:24 +0000 (24 15:01 +1000) | ||
| committer | Nathan Scott <nathans@redhat.com> | |
| Fri, 24 Jun 2016 05:01:24 +0000 (24 15:01 +1000) | ||
| tree | a049be8c25a0f76f87eb8648a039e4ea2b3a5ef6 | treesnapshot (tar.gz zip) |
| parent | 9613f182e9df099011a0531365b8a3df69119b8c | commitdiff |
pmlogger: auto-reconnect to pmcd whenever possible
Extend Dave's consistency checking to also allow pmlogger
to reconnect automatically to pmcd (just like pmie always
has).
This is important for the common case of a pmcd restart on
a host monitored by a central pmlogger farm. Previously,
we were open to some minutes of missed data until the cron
pmlogger_check kicked in - now it is instantaneous.
Its worth noting that we still always start a new pmlogger
with each new day, even with this change in place.
Verify the auto-reconnection and presence of a mark record
via the qa/389 test script.
Extend Dave's consistency checking to also allow pmlogger
to reconnect automatically to pmcd (just like pmie always
has).
This is important for the common case of a pmcd restart on
a host monitored by a central pmlogger farm. Previously,
we were open to some minutes of missed data until the cron
pmlogger_check kicked in - now it is instantaneous.
Its worth noting that we still always start a new pmlogger
with each new day, even with this change in place.
Verify the auto-reconnection and presence of a mark record
via the qa/389 test script.