QueueMetrics > QueueMetrics installation

QM 1.6 and realtime queue_log

<< < (4/7) > >>

QueueMetrics:
You could use something like


--- Quote ---ALTER TABLE `queueu_log` CHANGE `time` `time` VARCHAR( 30 ) NOT NULL
--- End quote ---

Old data may be deleted....
I would like to see which data you write to it.

trymes:
OK, I haven't tried firing up the queue_log via MySQL again, but here is what happened when modifying my table. It seems as if no data was lost (not that I had much real data...).


--- Code: ---mysql> use asterisk;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
mysql> select * from queue_log;
+----+------------+------------------+-----------+------------------------+----------------+----------+
| id | time       | callid           | queuename | agent                  | event          | data     |
+----+------------+------------------+-----------+------------------------+----------------+----------+
|  1 | 1288362313 | NONE             | NONE      | NONE                   | CONFIGRELOAD   |          |
|  2 | 1288362334 | 1288362186.10990 | 400       | Local/127@from-queue/n | COMPLETECALLER | 11|132|2 |
+----+------------+------------------+-----------+------------------------+----------------+----------+
2 rows in set (0.01 sec)

mysql> ALTER TABLE `queue_log` CHANGE `time` `time` VARCHAR( 30 ) NOT NULL;
Query OK, 2 rows affected (0.03 sec)
Records: 2  Duplicates: 0  Warnings: 0

mysql> select * from queue_log;
+----+------------+------------------+-----------+------------------------+----------------+----------+
| id | time       | callid           | queuename | agent                  | event          | data     |
+----+------------+------------------+-----------+------------------------+----------------+----------+
|  1 | 1288362313 | NONE             | NONE      | NONE                   | CONFIGRELOAD   |          |
|  2 | 1288362334 | 1288362186.10990 | 400       | Local/127@from-queue/n | COMPLETECALLER | 11|132|2 |
+----+------------+------------------+-----------+------------------------+----------------+----------+
2 rows in set (0.00 sec)

--- End code ---

I will test this once call volume is down.

Tom

trymes:
OK, so to clear things up, I tried the ALTER statement, and I get this error still. How, I do not know.


--- Code: ---/var/log/asterisk/full:[Nov  3 13:37:57] VERBOSE[25801] config.c:   == Binding queue_log to mysql/general/queue_log
/var/log/asterisk/full:[Nov  3 13:37:57] WARNING[25801] res_config_mysql.c: Realtime table general@queue_log: column 'time' cannot be type 'int(10) unsigned' (need char)

--- End code ---

So, I thought, let's just delete the whole table and start again. Which I did. I used this to create the table:


--- Code: ---CREATE TABLE `queue_log` (
  `id` int(10) unsigned NOT NULL auto_increment,
  `time` varchar(30) NOT NULL default '',
  `callid` varchar(32) NOT NULL default '',
  `queuename` varchar(32) NOT NULL default '',
  `agent` varchar(32) NOT NULL default '',
  `event` varchar(32) NOT NULL default '',
  `data` varchar(255) NOT NULL default '',
  PRIMARY KEY (`id`)
);
--- End code ---

I still get the same error. Any ideas? I mean, I can only presume that you guys had this working at some point in order to implement the functionality on QM? Can you look at how the development machine was set up and tell me if it differs from what I am doing?

Tom

trymes:
No news is bad news, I presume?

Come on, this is a published feature of the program, I can only presume that the devs had it working at some point?

Tom

QueueMetrics:
Yes, but they accessed a client's system during development.
We plan to address this with a tutorial for 1.8.

Navigation

[0] Message Index

[#] Next page

[*] Previous page