QueueMetrics > MySQL storage and Qloaderd/Uniloader

Wherein we discuss multi-server and partitions...

(1/1)

Kevlar:
Up until recently we have been running the single server license of Queuemetrics. However, we are migrating branch offices off of their legacy pbx systems and a few of them either make use of queues or are wanting to add in that functionality. As such, we have increased our licensing to the five server version.

As I set this up, I am faced with a bit of a question. Our original Asterisk box writes to partition P01. Now should I set up my next asterisk box to have qloaderd write to P02, or will it cause a conflict if both use P01? I can use the other settings in QueueMetrics to keep each branch only seeing its own stats. Before I start dumping a second instance into the same partition I would like some advice about best practices here.

The call load is not overly heavy. The busiest site of the one we are doing will have 100-200 calls per day. All sites total will be around 600 calls per day to the queues. Let me know if I would need to provide any other pertinent information. Thanks.

Kevlar:
Think I just found the answer to my question. Use seperate partitions and set up the cluster setup in configuration.properties.

QueueMetrics:
+1  ;)

Navigation

[0] Message Index