Reporting

Contents

• Reporting
  • Totem Panels
    • Import Default Configuration and Demo Dashboards
    • Data flow
      • 1. Replication from XiVO PBX to XiVO CC
      • 2. Replication from XiVO CC to Elasticsearch
    • Elasticsearch data purging
    • Check the status

Totem Panels

The XiVO CC comes with the ELK [1] stack. This offers the possibility to do some dashboard to visualize, for example, your call center activity.

This can also be used to explore your data and analyze it.

Example:

See also

• Import Default Configuration and Demo Dashboards section to have the demo dashboard.
• Data flow section to learn about what is put inside Elasticsearch.

[1]	ELK: Elasticsearch, Logstash, Kibana - see https://www.elastic.co

Import Default Configuration and Demo Dashboards

Preconfigured panels and index pattern are available on our gitlab repository.

1. Download the sample panels from https://gitlab.com/xivocc/sample_reports/blob/master/kibana-set/kibana.json
2. Import this json file in Kibana:

• Goto Kibana management ‣ Saved objects` menu

  

• Click on Import button,

• In the new menu select the previously kibana.json downloaded file

• If not checked, activate the Automatically overwrite all saved object ? toggle

• Click on Import button

You can now browse the sample reports in Dashboard

Note that to work on your environment, the CC - Queues dashboard must edited to change the queues name.

Data flow

Event data (i.e. the queue_log table) is replicated in two steps:

1. Replication from XiVO PBX to XiVO CC

Data are replicated almost instantaneously with the db_replic service. See also the Replication schema. To see replication status open /var/log/xivo-db-replication/xivo-db-replication.log on XiVO.

2. Replication from XiVO CC to Elasticsearch

Data are replicated every 1 minute with Logstash.

The information about the last replicated id is lost when the Logstash container is recreated (e.g. when upgrading to another LTS). In this case Logstash re-replicates the last 7 days of data. Note that as the data are already stored in Elasticsearch, no progress will be visible and no new data will appear for few minutes.

Elasticsearch data purging

Elasticsearch is configured to keep at least 30 days of data.

Check the status

To check the ELK stack:

• Go to the Kibana monitoring page

  

• Activate the monitoring if it wasn’t:

  

• And then you can see