Ignore log output for the Consul heartbeat timer

[jwreagor]

Recently, we added a feature that logs timing/timer events when our log level is set to DEBUG (#534). This, or a combination with something else, is presenting excessive log output we simply do not need.

It looks like the following...

DEBU[0000] control: initialized router for control server
DEBU[0000] control: listening to /var/run/containerpilot.socket
DEBU[0000] event: {Startup global}
INFO[0000] control: serving at /var/run/containerpilot.socket
DEBU[0000] job1.Run start
INFO[0000] telemetry: serving at 127.0.0.1:9090
DEBU[0005] timer: {TimerExpired containerpilot.heartbeat}
INFO[0005] Service registered: containerpilot
DEBU[0010] timer: {TimerExpired containerpilot.heartbeat}
DEBU[0015] timer: {TimerExpired containerpilot.heartbeat}
DEBU[0020] timer: {TimerExpired containerpilot.heartbeat}
DEBU[0025] timer: {TimerExpired containerpilot.heartbeat}

This issue should be resolved by safely ignoring this log output by matching on the containerpilot.heartbeat event timer name. The original goal of this log output was to help debug jobs with intervals/timers.

Steps to reproduce

• Enable the telemetry endpoint
• Set log level to DEBUG

[jwreagor]

Actually, this looks like it is setup by the service registry for the telemetry endpoint. It would still be nice to remove this unnecessary log output.

[jwreagor]

This can be added to #559 as well.