<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Thanks for the tip on 'metrics' I am studying it now.<br>
    <br>
    Cheers, Eric<br>
    <br>
    <div class="moz-cite-prefix">On 2014-11-13, 10:32 AM, Donald McLean
      wrote:<br>
    </div>
    <blockquote
cite="mid:CA+W6VsYoa-m=2wF+LaCPuDgwJg2oVKmQ1p3jf8P7jnqhMoxxAA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div>
            <div>Eric,<br>
              <br>
            </div>
            That's an interesting problem. I would be tempted to wrap
            one of those three (custom appender, filter, or
            turbo-filter) around a Metrics object:<br>
            <br>
            <a moz-do-not-send="true"
              href="https://dropwizard.github.io/metrics/3.1.0/">https://dropwizard.github.io/metrics/3.1.0/</a><br>
            <br>
          </div>
          Being that rates are one of the things that Metrics supports
          out of the box.<br>
          <br>
        </div>
        Donald<br>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Thu, Nov 13, 2014 at 1:21 PM, Eric
          Kolotyluk <span dir="ltr"><<a moz-do-not-send="true"
              href="mailto:eric.kolotyluk@gmail.com" target="_blank">eric.kolotyluk@gmail.com</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">I found an
            interesting problem while configuring our Amazon Kinesis
            Connector. After starting up our service everything looks
            fine, but after 15 minutes or so, all hell breaks loose.<br>
            <br>
            The Connector is Amazon's code, and it does not throw any
            exceptions that our code can catch, rather it just reports a
            lot of errors in the log stream. This is clearly an insane
            situation that we need to catch, so I was thinking of
            writing a custom appender, filter, or turbo-filter to
            monitor the log stream for insanity. For example, errors per
            minute over some threshold.<br>
            <br>
            Does this seem like the right way to address this problem?
            Have other people used similar techniques, or other
            techniques to sanity check the log stream?<br>
            <br>
            Cheers, Eric<br>
            _______________________________________________<br>
            Logback-user mailing list<br>
            <a moz-do-not-send="true" href="mailto:Logback-user@qos.ch"
              target="_blank">Logback-user@qos.ch</a><br>
            <a moz-do-not-send="true"
              href="http://mailman.qos.ch/mailman/listinfo/logback-user"
              target="_blank">http://mailman.qos.ch/mailman/listinfo/logback-user</a><br>
          </blockquote>
        </div>
        <br>
        <br clear="all">
        <br>
        -- <br>
        <div class="gmail_signature">Family photographs are a critical
          legacy for<br>
          ourselves and our descendants. Protect that<br>
          legacy with a digital backup and recovery plan.</div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Logback-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Logback-user@qos.ch">Logback-user@qos.ch</a>
<a class="moz-txt-link-freetext" href="http://mailman.qos.ch/mailman/listinfo/logback-user">http://mailman.qos.ch/mailman/listinfo/logback-user</a></pre>
    </blockquote>
    <br>
  </body>
</html>