<div dir="auto">Gotcha. I have some xlog info stuff in thing is we weren't catching unforeseen things like 'dispatcher had no nodes'. I'm now using a syslog regex to alert for 'dispatcher' and maybe I'll do one for 'core' minus anything with the word 'parse'. Baby steps..</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Feb 14, 2019, 5:23 PM Brandon Armstead <<a href="mailto:brandon@cryy.com">brandon@cryy.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div dir="auto">I would also say - implement your own routing logic / info shaking data you wish to make sense of, then change debug level to lower value, change debug level higher when actually  reproducing and investigating a bug/issue.  </div></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Feb 14, 2019 at 6:57 AM Daniel-Constantin Mierla <<a href="mailto:miconda@gmail.com" target="_blank" rel="noreferrer">miconda@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div text="#000000" bgcolor="#FFFFFF">
    <p>Hello,</p>
    <p>maybe you can make some filtering based on the path of the files
      printing the error messages, so if you want to "ignore" parsing
      errors, then skip alerts what have "core/parser/" in the path.</p>
    <p>Otherwise, it is not that easy to add so many options to be able
      to control every errors/warnings/... when to print them.</p>
    <p>There could be also solutions to block traffic from devices
      sending broken SIP packages continuously/for long interval of
      time.</p>
    <p>Cheers,<br>
      Daniel<br>
    </p>
    <div class="m_-1860973526553415774m_-711966149861612586moz-cite-prefix">On 14.02.19 03:58, Daniel Greenwald
      wrote:<br>
    </div>
    <blockquote type="cite">
      
      <div dir="ltr">Curious how other folks are dealing with the volume
        of logs that Kamailio generates. We are currently sending them
        to syslog and alerting on WARN and above but the amount of alert
        noise is unbearable. For example (there are many variations):
        <div><span style="font-family:monospace"><span style="color:rgb(0,0,0)">ERROR: <core>
              [core/tcp_read.c:297]: tcp_read_data(): error reading:
              Connection reset by peer</span><br>
          </span></div>
        <div><span style="font-family:monospace"><span style="color:rgb(0,0,0)">INVITE:WARNING: sanity
              [sanity.c:776]: check_parse_uris(): failed to parse</span><br>
            From header<br>
          </span></div>
        <div><span style="font-family:monospace"><span style="color:rgb(0,0,0)"> INVITE:ERROR: <core>
              [core/parser/parse_from.c:75]: parse_from_header(): b</span><br>
            ad From header<br>
          </span></div>
        <div><span style="font-family:monospace"><br>
          </span></div>
        <div><span style="font-family:monospace">The fact that these are
            WARN/ERROR level and from core makes me wonder how we can
            possibly make alerts relevant. Any input would be
            appreciated.</span></div>
        <div><span style="font-family:monospace"><br>
          </span></div>
        <div><span style="font-family:monospace">Thanks,</span></div>
        <div><span style="font-family:monospace"><br>
          </span></div>
        <div><span style="font-family:monospace">Daniel G</span></div>
      </div>
      <br>
      <fieldset class="m_-1860973526553415774m_-711966149861612586mimeAttachmentHeader"></fieldset>
      <pre class="m_-1860973526553415774m_-711966149861612586moz-quote-pre">_______________________________________________
Kamailio (SER) - Users Mailing List
<a class="m_-1860973526553415774m_-711966149861612586moz-txt-link-abbreviated" href="mailto:sr-users@lists.kamailio.org" target="_blank" rel="noreferrer">sr-users@lists.kamailio.org</a>
<a class="m_-1860973526553415774m_-711966149861612586moz-txt-link-freetext" href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" target="_blank" rel="noreferrer">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
    </blockquote>
    <pre class="m_-1860973526553415774m_-711966149861612586moz-signature" cols="72">-- 
Daniel-Constantin Mierla -- <a class="m_-1860973526553415774m_-711966149861612586moz-txt-link-abbreviated" href="http://www.asipto.com" target="_blank" rel="noreferrer">www.asipto.com</a>
<a class="m_-1860973526553415774m_-711966149861612586moz-txt-link-abbreviated" href="http://www.twitter.com/miconda" target="_blank" rel="noreferrer">www.twitter.com/miconda</a> -- <a class="m_-1860973526553415774m_-711966149861612586moz-txt-link-abbreviated" href="http://www.linkedin.com/in/miconda" target="_blank" rel="noreferrer">www.linkedin.com/in/miconda</a>
Kamailio World Conference - May 6-8, 2019 -- <a class="m_-1860973526553415774m_-711966149861612586moz-txt-link-abbreviated" href="http://www.kamailioworld.com" target="_blank" rel="noreferrer">www.kamailioworld.com</a>
Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- <a class="m_-1860973526553415774m_-711966149861612586moz-txt-link-abbreviated" href="http://www.asipto.com" target="_blank" rel="noreferrer">www.asipto.com</a></pre>
  </div>

_______________________________________________<br>
Kamailio (SER) - Users Mailing List<br>
<a href="mailto:sr-users@lists.kamailio.org" target="_blank" rel="noreferrer">sr-users@lists.kamailio.org</a><br>
<a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
</blockquote></div></div>-- <br><div dir="ltr" class="m_-1860973526553415774gmail_signature" data-smartmail="gmail_signature">Sent from Gmail Mobile</div>
</blockquote></div>