Queue log

Asterisk writes every queue event, such as a call entering a queue, ringing an agent, being answered, or abandoned, to its queue log. BeePanel reads the queue log and keeps its own copy of the events. Queue statistics come from it:

• the Queue performance report;
• the queue columns of the Agent performance report;
• the queue figures of the Abandoned and unanswered report;
• the wallboard's daily answered, abandoned, and service level figures.

Sources

• Database table: a queue log table on the call history source's database, such as queuelog or queue_log.
• Log file: the local Asterisk queue log file, by default /var/log/asterisk/queue_log.

BeePanel changes nothing on the PBX to read either source.

Setup proposes a table when it finds one with rows on the call history source's database. Otherwise it proposes the file that Asterisk's configuration names (astlogdir in asterisk.conf and queue_log_name in logger.conf).

Read access to the file

BeePanel runs as its own user, which cannot read the queue log by default. The installer grants that user read access to the current file, to its rotated files, and to the directory, so that new files can be read as well. It only adds read permissions: owners, groups, and file contents stay as they are. These permissions remain after uninstalling BeePanel; remove them yourself if you no longer need them.

If the grant failed, fix the cause the installer reported and run the installer again as root:

beepanel install

The installer grants access only to the queue log that Asterisk's configuration names. If you choose a different file in Settings, give the beepanel user read access to it yourself.

Rotated files compressed with gzip are read; other compression formats are not.

Setting up or changing the source

Prerequisite: a user allowed to manage BeePanel.

1. Open Management > Settings, and choose Set up or Edit on the Queue log row under Call data.
2. Under Source, choose Database table or Log file.
3. For a table, enter the Table name and the Time zone its times were written in. For a database on the same server, BeePanel fills in the server's time zone. For a file, enter the Absolute file path.
4. Choose Test read access, then Save.

When you switch sources, the events already stored are kept, and BeePanel reads the new source from its beginning.

Reading the source again

Re-read on the Queue log row reads the whole available source again and merges its events into the stored copy. Events already stored are kept, and duplicates are ignored. Use it after fixing access to files that could not be read. BeePanel never deletes queue events on its own.

Checking the result

• Test read access reports Read access verified.
• The Queue log row on the Status page shows Running, with the last line read and the processing lag.
• The Queue performance report shows your queues.

Common problems

Missing files

The Queue log row in Settings lists rotated files BeePanel could not read, with a reason for each:

• No read permission: run the installer again, or grant read access to the file yourself, then choose Re-read.
• Unsupported compression: the file is compressed with a format other than gzip.
• Corrupt gzip: the file is damaged.

Events in these files are missing from reports and from the wallboard's daily figures. The server deletes rotated files when they expire, so read them again before that happens.

Queue statistics need the queue log source

The Queue performance report shows this when no source is set up. Set one up as described above.

The source is being read but the lines are not keeping up.

The Status page marks the queue log Needs attention. Use Test read access in the editor to check the source.

Related articles

• Settings
• Call history source