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.
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).
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.
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.
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.
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:
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.
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:
Install Splunk DB Connect.
In Splunk DB Connect create database connection to your database.
In Splunk DB Connect create Database Input. In it specify
Sourcetype as asterisk_queue_log_db, and Splunk Index as
thirdlane
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:
Create data input in Files & Directories. As source type specify
asterisk_cdr_text and in Index section select Set the
destination index as thirdlane.
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:
Install Splunk DB Connect.
In Splunk DB Connect create database connection to your database.
In Splunk DB Connect create Database Input. In it specify
Sourcetype as asterisk_cdr_db, and Splunk Index as
thirdlane
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
As a Splunkbase app developer, you will have access to all Splunk development resources and receive a 10GB license to build an app that will help solve use cases for customers all over the world. Splunkbase has 1000+ apps from Splunk, our partners and our community. Find an app for most any data source and user need, or simply create your own with help from our developer portal.