<div dir="ltr"><br><div class="gmail_quote">2008/7/16 Tilghman Lesher <<a href="mailto:tilghman@mail.jeffandtilghman.com">tilghman@mail.jeffandtilghman.com</a>>:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">
> If they TRULY see themselves as a TELCO replacements for large shop<br>
> they REALLY need to step up to<br>
> proving INFO, WARN, ERROR messaging in a unified reliable manner. Such<br>
> as a SNMP messaging ability for all<br>
> INFO, ERROR, and WARN level messages.<br>
<br>
</div><br>That's an interesting idea, and perhaps someone might pick up on the idea and<br>
run with it. Perhaps you might and donate your efforts back to the project.<br></blockquote><div><br>From memory, I think I've read here (or developers list) a note (was it from Olle ?) aiming to unify logging, eventing, monitoring (AMI, SNMP, ...) APIs.<br>
I think that thread occurred when it was decided to include a version number in Manager interface.<br>I agree this is an interesting idea ...<br><br><br>The use case that made me ask this is here :<br><br>I've got a running system which is working ok up to a moment it stops to dial out on ISDN-BRI spans (incoming calls are ok). When Asterisk is restarted, everything runs normally for a couple of days.<br>
Each time it can't dialout, I've got such messages (though, obviously the system has unused ISDN channels and should be able to dial out) :<br><br>[Jul 11 10:01:47] WARNING[19997] app_dial.c: Unable to create channel of type 'Zap' (cause 34 - Circuit/channel congestion)<br>
<br><br><br>As a balance between finding root cause and minimizing users disturbance, I would like to configure Asterisk (and its environment) so that I can :<br>- gather data that could help to find root cause,<br>- trigger an Asterisk convenient restart after a couple of such messages.<br>
<br>What we can say Asterisk's output is stable enough but I can't make up my mind about the best way to implement the following rules :<br><br>"as soon as Asterisk issues "cause 34 - Circuit/channel congestion" logs, switch to "Debug BRI mode" (ie turn on DEGUG PRI, increase verbosity, print channels values, ...)"<br>
"as soon as the third "cause 34 - Circuit/channel congestion" message is issued (within a 30mn time frame, for instance), restart Asterisk in Standard Mode"<br><br><br>Being able to insert parsing functions between Asterisk code and pure logging functions and tie commands to such parsing functions would be perfect.<br>
Syslog-ng seems to bundle those parsing-logging functions (see <a href="http://web.suffieldacademy.org/ils/netadmin/docs/software/syslog/#toc4">http://web.suffieldacademy.org/ils/netadmin/docs/software/syslog/#toc4</a>). It should be worth to try.<br>
</div></div><br><br>Alternatives are :<br>- perl scripts<br>- nagios<br>- splunk<br>- munin<br><br>Thanks for this input. I'll try to give a deeper look into each of those.<br><br>Regards<br></div>