icon/x Created with Sketch.

Splunk Cookie Policy

We use our own and third-party cookies to provide you with a great online experience. We also use these cookies to improve our products and services, support our marketing campaigns, and advertise to you on our website and other websites. Some cookies may continue to collect information after you have left our website. Learn more (including how to update your settings) here.
Accept Cookie Policy

Accept License Agreements

This app is provided by a third party and your right to use the app is in accordance with the license provided by that third-party licensor. Splunk is not responsible for any third-party apps and does not provide any warranty or support. If you have any questions, complaints or claims with respect to this app, please contact the licensor directly.

Thank You

Downloading Thirdlane FreeMetrics
To install your download
For instructions specific to your download, click the Details tab after closing this window.

Flag As Inappropriate

Thirdlane FreeMetrics

Overview
Details
Thirdlane FreeMetrics is a free Splunk application that produces charts and reports from Call Detail and Queue Log records generated by Asterisk based PBXs, including Thirdlane PBX, Thirdlane Multi Tenant PBX and Thirdlane Call Center.
Every call center manager is responsible for tracking and improving a variety of call center metrics and requires advanced and easy to use tools for constant evaluation of agent and overall call center performance. Thirdlane FreeMetrics software lets call center managers to track and analyze call center performance metrics and key performance indicators with the precision required for making better informed management decisions.

Introduction

Welcome to Thirdlane FreeMetrics. Thirdlane FreeMetrics is a Splunk
app for analyzing logs produced by Asterisk based solutions and
provides PBX and Call Center administrators with a set of tools to get a
comprehensive accurate picture of PBX usage or Call Center performance.

Support

This app is maintained by Third Lane Technologies. LLC. For setup help
or any questions please post them on answers.splunk.com and tag them
with ThirdlaneFreeMetrics (case sensitive).

Dependencies

If your Asterisk CDR or Queue Log records are stored in a database, this
app requires Splunk DB Connect (http://apps.splunk.com/app/958/) app
from Splunkbase. You do not need to install Splunk DB Connect if both
your CDR and Queue Log data is stored in text files.

Installing

After downloading Thirdlane FreeMetrics application from Thirdlane
website, go to Manage Apps in apps menu, and select Install app from
file. After installation completes, you will get a prompt requesting
system restart. Once Splunk is restarted Thirdlane FreeMetrics will be
available in the apps menu.

Setup

In order to use Thirdlane FreeMetrics you have to configure source types
indicating whether you will be working with data stored in database or
text files. You can do this using Thirdlane FreeMetrics setup screen,
where you will be able to specify source type for Asterisk CDR, and
Asterisk Queue Log.

Note that you can always change the source type later using settings
button in navigation menu of Thirdlane FreeMetrics.

Getting data in

Thirdlane FreeMetrics recognizes four types of data sources:

  • asterisk_cdr_text - use this when working with CDR data stored in
    text files

  • asterisk_cdr_db - use this when working with CDR data stored in
    database

  • asterisk_queue_log_text - use this when working with Queue Log
    data stored in text files

  • asterisk_queue_log_db - use this when working with Queue Log data
    stored in database

Asterisk Queue_Log in text file

To start working with Queue Log stored in text file you need to:

  1. Create data input in Files & Directories. You should specify
    asterisk_queue_log_text as a source type and in Index section
    select Set the destination index as thirdlane.

  2. In Thirdlane FreeMetrics app settings select queue_log source type
    as Text.

Thirdlane FreeMetrics expects the following order of fields in the Queue
Log and will extract the following fields:

  • time_unix

  • callid

  • queuename

  • agent

  • event

  • data

  • data1

  • data2

  • data3

  • data4

  • data5

Asterisk Queue Log in database

To start working with database based Queue Log you need to:

  1. Install Splunk DB Connect.

  2. In Splunk DB Connect create database connection to your database.

  3. In Splunk DB Connect create Database Input. In it specify
    Sourcetype as asterisk_queue_log_db, and Splunk Index as
    thirdlane

  4. In Thirdlane FreeMetrics app settings select queue_log source type
    as Database.

Thirdlane FreeMetrics expects following field names in database table
queue_log:

  • time_unix

  • callid

  • queuename

  • agent

  • event

  • data

  • data1

  • data2

  • data3

  • data4

  • data5

If your database schema is different from the above, you have two
options:

  • Create custom view for your existing table based on the requirements
    as per above (recommended).

  • Specify an SQL query when creating database input.

Asterisk CDR in text file

To start working with text based CDR you need to:

  1. Create data input in Files & Directories. As source type specify
    asterisk_cdr_text and in Index section select Set the
    destination index as thirdlane.

  2. In Thirdlane FreeMetrics app settings select CDR source type as
    Text.

Thirdlane FreeMetrics expects the following order and will extract the
following fields from text based CDR:

  • accountcode

  • src

  • dst

  • dcontext

  • clid

  • channel

  • dstchannel

  • lastapp

  • lastdata

  • start

  • answer

  • end

  • duration

  • billsec

  • disposition

  • amaflags

  • uniqueid

  • userfield

Asterisk CDR in database

To start working with database based CDR you need to:

  1. Install Splunk DB Connect.

  2. In Splunk DB Connect create database connection to your database.

  3. In Splunk DB Connect create Database Input. In it specify
    Sourcetype as asterisk_cdr_db, and Splunk Index as
    thirdlane

  4. In Thirdlane FreeMetrics app settings select CDR source type as
    Database.

Thirdlane FreeMetrics expects following field names in database table
cdr:

  • accountcode

  • src

  • dst

  • dcontext

  • clid

  • channel

  • dstchannel

  • lastapp

  • lastdata

  • start

  • answer

  • end

  • duration

  • billsec

  • disposition

  • amaflags

  • uniqueid

  • userfield

If your database schema is different from the above, you have two
options:

  • Create custom view for your existing table based on the requirements
    as per above (recommended).

  • Specify an SQL query when creating database input

AppInspect Tooling

Splunk AppInspect evaluates Splunk apps against a set of Splunk-defined criteria to assess the validity and security of an app package and components.

Are you a developer?

As a Splunkbase app developer, you will have access to all Splunk development resources and receive a 50GB license to build an app that will help solve use cases for customers all over the world. Splunkbase has 1000+ apps and add-ons from Splunk, our partners and our community. Find an app or add-on for most any data source and user need, or simply create your own with help from our developer portal.

Follow Us:
© 2005-2019 Splunk Inc. All rights reserved.
Splunk®, Splunk>®, Listen to Your Data®, The Engine for Machine Data®, Hunk®, Splunk Cloud™, Splunk Light™, SPL™ and Splunk MINT™ are trademarks and registered trademarks of Splunk Inc. in the United States and other countries. All other brand names, product names, or trademarks belong to their respective owners.