Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - chesstrian

Pages: [1] 2
1
Improving QueueMetrics / Re: Get many call records.
« on: June 05, 2013, 17:12:55 »
I mean to the audio files.

2
Improving QueueMetrics / Get many call records.
« on: May 22, 2013, 17:48:57 »
It would be great if it's possible to get all call records from an agent or selected agents in a date range. Others filters would be great :)

3
Of course you can link, modify and do whatever you need :).

I did it as an exercise, because I like Asterisk and NodeJS for realtime applications, i'm doing a monitor based on queue_log file, so that was the beginning.

4
I have programed a little script in Node JS which gather every line from queue_log file and put it into MongoDB; it haven't been tested with log rotation and needs support for MySQL and others DBs, if you have any comment or improvement, it will be appreciated.

It would be great if this is useful for someone.

You can check for sources here: https://github.com/chesstrian/qlog2db

5
It was permissions, tomcat user needs to be in asterisk group.  :)

6
Now it works  ;D. Thank you very much!

7
Storage is working, but Queuemetrics doesn't recognize regex in the name of the directory.

Queuemetrics Logs:

Apr 30, 2013 8:41:28 AM it.loway.tpf.U listFiles
SEVERE: The directory '/var/spool/asterisk/monitor/%YY/%MM/%DD/' might not exist
Apr 30, 2013 8:41:28 AM it.loway.tpf.U listFiles
SEVERE: The directory '/var/spool/asterisk/monitor/%YY/%MM/%DD/' might not exist
Apr 30, 2013 8:41:28 AM it.loway.tpf.U listFiles
SEVERE: The directory '/var/spool/asterisk/monitor/%YY/%MM/%DD/' might not exist

but there are records in /var/spool/asterisk/monitor/2013/04/30/. :(

This is my log, i haven't logs about "LocalFilesByDay" is fully registered, how can i see it?

8
It doesn't work, thanks anyway.  :'(

9
Storage is working, but Queuemetrics doesn't recognize regex in the name of the directory.

Queuemetrics Logs:

Apr 30, 2013 8:41:28 AM it.loway.tpf.U listFiles
SEVERE: The directory '/var/spool/asterisk/monitor/%YY/%MM/%DD/' might not exist
Apr 30, 2013 8:41:28 AM it.loway.tpf.U listFiles
SEVERE: The directory '/var/spool/asterisk/monitor/%YY/%MM/%DD/' might not exist
Apr 30, 2013 8:41:28 AM it.loway.tpf.U listFiles
SEVERE: The directory '/var/spool/asterisk/monitor/%YY/%MM/%DD/' might not exist

but there are records in /var/spool/asterisk/monitor/2013/04/30/. :(

10
This is not working for me, are there any mandatory additional change?.  :-[

11
Running QueueMetrics / Re: Call Outcomes and Stins
« on: June 11, 2010, 23:34:36 »

13
Well, i think that subject is clear. Here there are some views:

qloaderd.log
 |Thu Jun 10 20:29:52 2010|Loaded 41000 lines so far...
 |Thu Jun 10 21:34:43 2010|Loaded 100 lines so far...
 |Thu Jun 10 21:43:16 2010|Loaded 41100 lines so far...
 |Thu Jun 10 22:11:16 2010|Heart is still beating... Imported: 41115 lines.
 |Thu Jun 10 22:11:17 2010|Heart is still beating... Imported: 130 lines.


# grep 1276088424.31309 /var/log/asterisk/queue_log
1276088450|1276088424.31309|500|NONE|ENTERQUEUE||45481262
1276088451|1276088424.31309|500|Local/3644@from-dinamicqueues/n|CONNECT|1|1276088450.31323|1
1276088722|1276088424.31309|500|Local/3644@from-dinamicqueues/n|COMPLETECALLER|1|271|1
1276088731|1276088424.31309|NONE|Agent/3644|CALLSTATUS|PA121

Here we can see that logs in queue_log file is good

mysql> SELECT * FROM queue_log WHERE call_id='1276088424.31309';
+-----------+------------+------------------+-------+------------+----------------+-------+------------------+-------+-------+----------+------------------+
| partition | time_id    | call_id          | queue | agent      | verb           | data1 | data2            | data3 | data4 | serverid | unique_row_count |
+-----------+------------+------------------+-------+------------+----------------+-------+------------------+-------+-------+----------+------------------+
| P001      | 1276088450 | 1276088424.31309 | 500   | NONE       | ENTERQUEUE     |       | 45481262         |       |       |          |                1 |
| P001      | 1276088450 | 1276088424.31309 | 500   | NONE       | ENTERQUEUE     |       | 45481262         |       |       |          |                2 |
| P001      | 1276088451 | 1276088424.31309 | 500   | Agent/3644 | CONNECT        | 1     | 1276088450.31323 | 1     |       |          |                1 |
| P001      | 1276088451 | 1276088424.31309 | 500   | Agent/3644 | CONNECT        | 1     | 1276088450.31323 | 1     |       |          |                2 |
| P001      | 1276088722 | 1276088424.31309 | 500   | Agent/3644 | COMPLETECALLER | 1     | 271              | 1     |       |          |                1 |
| P001      | 1276088722 | 1276088424.31309 | 500   | Agent/3644 | COMPLETECALLER | 1     | 271              | 1     |       |          |                2 |
| P001      | 1276088731 | 1276088424.31309 | NONE  | Agent/3644 | CALLSTATUS     | PA121 |                  |       |       |          |                1 |
| P001      | 1276088731 | 1276088424.31309 | NONE  | Agent/3644 | CALLSTATUS     | PA121 |                  |       |       |          |                2 |
+-----------+------------+------------------+-------+------------+----------------+-------+------------------+-------+-------+----------+------------------+
8 rows in set (6.92 sec)

If delete duplicate rows whit a sentence like "DELETE FROM queue_log WHERE unique_row_count=2;", the problems about stints and reports desappears from QueueMetrics, but Reports is saw in any moment, so, change database manually is not a posible solution, any sugestion will be apreciated.

PD: Problems after logs rotation.

14
Running QueueMetrics / Re: Call Outcomes and Stins
« on: June 10, 2010, 23:56:26 »
Hi people, the problem is that qloader put one line twice. Looking why.

15
Running QueueMetrics / Re: Call Outcomes and Stins
« on: June 10, 2010, 22:50:34 »
Hi guys, working in these troubles, i can see that when stints is in true, every call has more that 1 stint, but problems appears since june 6, day of the first rotate of logs. I'm using MySQL storage, so i don't know what is wrong with the rotations. Any help will be apreciated.

Pages: [1] 2