Guide to connecting to Radiostatistics
0
Which server do you use
We can connect your station to the Radiostatistics service only if you use one of these servers: icecast, shoutcast or hls.
You will need to specify the type of server in the email to us in step 5.
You will need to specify the type of server in the email to us in step 5.
1
Select the data transfer method
1) You give us access to data via ftp, http, rsyslog protocols on your servers, and we get your log files. Giving access via ftp to access.log files is a priority option.
2) We open access on our server to receive data, and you transmit the log files via ftp, http, rsyslog protocols. In this option, we provide the details for uploading files. It is important that the upload takes place at 00:00-01:00 local time in order for all logs for the past day to be processed.
2) We open access on our server to receive data, and you transmit the log files via ftp, http, rsyslog protocols. In this option, we provide the details for uploading files. It is important that the upload takes place at 00:00-01:00 local time in order for all logs for the past day to be processed.
2
Place the status file
To receive real-time reports, a status file must be placed in the Icecast web directory.
Download the status file from here.
Place it in the Icecast web directory.
The path to the web directory can be viewed in the Icecast configuration file in the <path> section, in the <webroot> division. The Icecast web directory has the name web, other status files are also located there, for example, status.xsl, status2.xsl and others.
Download the status file from here.
Place it in the Icecast web directory.
The path to the web directory can be viewed in the Icecast configuration file in the <path> section, in the <webroot> division. The Icecast web directory has the name web, other status files are also located there, for example, status.xsl, status2.xsl and others.
3
Open access to log files
Make sure that the name of the log file with listening data has the name access.log or corresponds to the masks access.log*, access.log.YYYYMMDD*. By default, Icecast generates file names already in this form. If the file name is different, rename it to access.log* or access.log.YYYYMMDD*.
Check that the name of the log file with metadata about the broadcast of the radio station, containing information on the played songs and artists, has the name playlist.log. If the file name is different, rename it to playlist.log.
The path to the directory with log files can be viewed in the Icecast configuration file in the <path> section, in the <logdir> division.
Make sure that the log files with listening data and metadata are not empty.
If there are several broadcast servers, then arrange the files in this order:
EDGE_1/
├── access.log
├── access.log.YYYYMMDD*
└── playlist.log.YYYYMMDD*
EDGE_2/
├── access.log
├── access.log.YYYYMMDD*
└── playlist.log.YYYYMMDD*
EDGE_3/
├── access.log
├── access.log.YYYYMMDD*
└── playlist.log.YYYYMMDD*
...
EDGE_1 and others are directories with arbitrary names containing Icecast logs for a specific distributing server.
Check that the name of the log file with metadata about the broadcast of the radio station, containing information on the played songs and artists, has the name playlist.log. If the file name is different, rename it to playlist.log.
The path to the directory with log files can be viewed in the Icecast configuration file in the <path> section, in the <logdir> division.
Make sure that the log files with listening data and metadata are not empty.
If there are several broadcast servers, then arrange the files in this order:
EDGE_1/
├── access.log
├── access.log.YYYYMMDD*
└── playlist.log.YYYYMMDD*
EDGE_2/
├── access.log
├── access.log.YYYYMMDD*
└── playlist.log.YYYYMMDD*
EDGE_3/
├── access.log
├── access.log.YYYYMMDD*
└── playlist.log.YYYYMMDD*
...
EDGE_1 and others are directories with arbitrary names containing Icecast logs for a specific distributing server.
4
Check the date and time on the server
Check whether the time zone, current time and date on the server are set correctly.
For Linux systems, the current time and time zone can be checked by running the 'date' command.
For reliability, we recommend setting up time synchronization with ntp servers.
Please note that if you have several broadcast servers, the time on all servers should be the same.
For Linux systems, the current time and time zone can be checked by running the 'date' command.
For reliability, we recommend setting up time synchronization with ntp servers.
Please note that if you have several broadcast servers, the time on all servers should be the same.
5
Write us an e-mail
Write an email to nester@mediadata.report
Subject of the letter: connection to Radiostatistics.
In the letter, specify the following information sequentially:
Subject of the letter: connection to Radiostatistics.
In the letter, specify the following information sequentially:
1
Name of radio station
Enter the name of the radio station in Latin.
2
Broadcasting server
Icecast, shoutcast or hls.
3
The method of transferring log files
Specify whether you will open access to your servers or transfer data to our servers. Additionally, specify the type of protocol: ftp, http, or rsyslog.
4
Identification data to access log files
Give us the identification data to access the log files using the selected method: server address, login, password.
5
Time zone
Specify your time zone.
6
Status file
Attach a link to the status file.
What's next?
In case of successful connection, we will send you an e-mail with the login and password to the Radiostatistics. Otherwise, we will clarify technical issues in the reply letter.
In any case, we are always in touch. If something does not work out, write to us in WhatsApp via the widget at the bottom of the screen or by email. We will definitely find a solution to make the necessary settings.
In any case, we are always in touch. If something does not work out, write to us in WhatsApp via the widget at the bottom of the screen or by email. We will definitely find a solution to make the necessary settings.
© All Rights Reserved.
nester@medidata.report