Asterisk 1.8.16 Monitoring Tools

Home » Asterisk Users » Asterisk 1.8.16 Monitoring Tools
Asterisk Users 4 Comments

Hello, I want to monitor my Asterisk 1.8, inbound, outbound, status calls, queue call? Any suggestions?

I found Monast, I’m having issues configurating.


4 thoughts on - Asterisk 1.8.16 Monitoring Tools

  • You want “live” monitoring or “after the fact”? The “hard way” to do “live”
    monitoring would be an active tail of /var/log/asterisk/full. After the fact you could read /var/log/asterisk/cdr-csv/Master.csv. In realtime I
    think these have database equivalents.

    —–Original Message—

  • Danny Nicholas wrote:

    I would imagine that the preferred way to do ‘live monitoring’ in an automated fashion would be through AMI and not by having something actively trying to follow log messages (and certainly not the full set of them). Log messages aren’t designed to be machine readable and the amount of extraneous stuff that has nothing to do with what you would be attempting to monitor with them would be staggering.

    If you don’t need it to be automated, there are log messages which will provide data about most happenings like this which you can observe in realtime with the CLI. Also, AMI can come into play if you need something more readable. For something like queues for instance, you could have a web interface using AMI to populate all sorts of data pertaining to queues, the members within them, etc and have it all shown to you in a nice easy to read view. But that sort of thing might take a bit of work.

  • Hello Motty, it really depends on what you want to do and the level of detail you want. There are a number of free and commercial applications that can help you in doing this 🙂

    2012/11/9 motty.cruz

  • Hey Motty,

    The simplest way I’ve found is having an asterisk console open (asterisk -r) with verbosity to level 12. Alternatively you could tail -f the full log (in /var/log/asterisk) – I like to parse it with something like ccze to colour code things.

    The better solution I’ve found is to use MySQL (or the equivalent database program you like) realtime to store my queues and use AGI or recode into LUA to log outbound calls to the same database. There is some fairly basic information on this at Once you’ve got all your data sorted how you want, you can develop whatever frondend application you want – perl scripts to monitor for trigger events, a nice web interface – the possibilities are endless!

    Best of luck,


    —–Original Message—