This tutorial shows you how to set up a telemetry backend server to manage your records and how to instrument your application with the telemetry API.

Clear Linux* OS includes a telemetry and analytics solution (also known as telemetrics) as part of the OS, which records events of interest and reports them back to the development team using the telemetrics client daemons.

The Clear Linux OS telemetry client can be enabled or disabled and records can be redirected to a desired location. More detailed information about using and configuring the telemetrics client is found in the Telemetry guide.


For this tutorial, you can use an existing Clear Linux OS system, or you can start with a clean installation of Clear Linux OS on a new system.

New Installation

To setup a new system for your telemetry backend server, follow the Install Clear Linux* OS on bare metal getting started guide and:

  1. Choose to install Clear Linux OS.
  2. Join the Stability Enhancement Program during the installation process to enable the telemetrics client components.
  3. Select the manual installation method with the following settings: * Set the hostname to clr-telem-server * Create an administrative user named clear and add this user to sudoers Create and enable a new user space * Choose the dev-utils, network-basic, and openssh-server bundles from the bundle list


Bundles can also be added to your system after this install process completed. The bundles listed here are a minimal set needed to complete the setup of the telemetry backend server and applications.

Existing System

If you are using an existing Clear Linux OS system, make sure you have installed the telemetry and dev-utils bundles. Use the swupd utility with the bundle-list option and check for “telemetrics” in the list:

sudo swupd bundle-list

If you need to install the bundles, use swupd to do so.

sudo swupd bundle-add telemetrics dev-utils

More information about enabling and configuring the telemetry client can be found at Enable telemetry.

You will need to run some of the commands in this tutorial with root privileges. You can create a new user or add your user to the sudoers list Create and enable a new user space.

Setting up the telemetry backend server

We’ll be using the file from the clearlinux/telemetrics-backend Git repository to install required dependencies for the web server applications. The script also configures nginx and uwsgi, deploys snapshots of the applications, and starts all required services.

Clone the clearlinux/telemetrics-backend Git repository

With all prerequisite software bundles installed, log in with your administrative user, and from your $HOME directory, run git to clone the telemetrics-backend repository into the $HOME/telemetrics-backend directory:

git clone


You may need to set up the https_proxy environment variable if you have issues reaching

Run the script to install the backend server

Change your current working directory to telemetrics-backend/scripts.

cd telemetrics-backend/scripts

Run the ./ -h to see the list of options for the script:

./ -h
Deploy snapshot of the telemetrics-backend

     -a    Perform specified action (deploy, install, migrate, resetdb,
           restart, uninstall; default: deploy)
     -d    Distro to deploy to (ubuntu, centos or clr; default: ubuntu)
     -h    Print these options
     -H    Set domain for deployment (only accepted value is "localhost" for
     -r    Set repo location to deploy from
     -s    Set source location (default: "master" branch from git repo)
     -t    Set source type (tarball, or git; default: git)
     -u    Perform complete uninstallation

The is a bash shell script that allows you to perform the following actions:

  • deploy - install a complete instance of the telemetrics backend server and all required components. This is the default action if no -a argument is given on the command line.
  • install - installs and enables all required components for the telemetrics backend server.
  • migrate - migrate database to new schema.
  • resetdb - reset the database.
  • restart - restart the nginx and uWSGI services.
  • uninstall - uninstall all packages.


The uninstall option does not perform any actions if the distro is set to Clear Linux OS and will only uninstall packages if the distro is Ubuntu

Next, we will install the telemetrics backend server with the following options:

  • -a install to perform an install
  • -d clr to install to a Clear Linux OS distro
  • -H localhost to set the domain to localhost

We do not need to set the following options since the values are set to the correct values we want by default:

  • -r sets the repo location for git to clone from.
  • -s master to set the location, or branch.
  • -t git to set the source type to git.


The shell script has minimal error checking and makes several changes to your system. Be sure that the options you define on the cmdline are correct before proceeding.

To begin the installation with the options defined:

Run the shell script from the $HOME/telemetrics-backend/scripts directory:

./ -H localhost -a install -d clr

The script will start and list all the defined options and prompt you for the PostgreSQL database password as shown below:

host: localhost
distro: clr
action: install
source: master
type: git
DB password: (default: postgres):

For the DB password:, press the Enter key to accept the default password postgres.

The swupd begins installing the required software bundles to set up the telemetrics backend server. The output will look similar to the following:

swupd-client bundle adder 3.12.7
Copyright (C) 2012-2017 Intel Corporation

Downloading packs...

Extracting application-server pack for version 18740
Extracting database-basic-dev pack for version 18670
Extracting database-basic pack for version 18670

Extracting c-basic pack for version 18800
Extracting os-core-dev pack for version 18800
Extracting web-server-basic pack for version 18680
Installing bundle(s) files...
Calling post-update helper scripts.
Possible filedescriptor leak : 8 (socket:[30833])
Bundle(s) installation done.


This script uses sudo to run commands and you may be prompted to enter your user password at any time while the script is executing. If this occurs, enter your user password to execute the sudo command.


You may also see an informational message about setting the :envvar:` https_proxy` environment variable if this variable isn’t set.

Once the swupd command is complete, the script begins processing the requirements to install and implement the telemetrics server. Finally, the script enables the server and provides output that finishes with something similar to:

Successfully built alembic Flask-Migrate itsdangerous Mako MarkupSafe python-editor SQLAlchemy uWSGI WTForms
Installing collected packages: SQLAlchemy, MarkupSafe, Mako, python-editor, six, python-dateutil, alembic, click, Werkzeug, Jinja2, itsdangerous, Flask, Flask-SQLAlchemy, Flask-Migrate, WTForms, Flask-WTF, psycopg2, uWSGI
Running install for psycopg2 ... done
Successfully installed Flask-0.12.2 Flask-Migrate-2.1.0 Flask-SQLAlchemy-2.2 Flask-WTF-0.14.2 Jinja2-2.9.6 Mako-1.0.7 MarkupSafe-1.0 SQLAlchemy-1.1.13 WTForms-2.1 Werkzeug-0.12.2 alembic-0.9.5 click-6.7 itsdangerous-0.24 psycopg2-2.7.3 python-dateutil-2.6.1 python-editor-1.0.3 six-1.10.0 uWSGI-2.0.15

Once all the server components have been installed you are prompted to enter the PostgreSQL database password to change it as illustrated below:

Enter password for 'postgres' user:
New password:
Retype new password:
passwd: password updated successfully

Enter postgres for the current value of the password and then enter a new password, retype it to verify the new password and the PostgreSQL database password will be updated.

The script finalizes installation and finishes.

Created symlink /etc/systemd/system/ → /usr/lib/systemd/system/postgresql.service.
Cloning into 'telemetrics-backend'...
remote: Counting objects: 344, done.
remote: Compressing objects: 100% (53/53), done.
remote: Total 344 (delta 30), reused 50 (delta 20), pack-reused 268
Receiving objects: 100% (344/344), 130.20 KiB | 1.40 MiB/s, done.
Resolving deltas: 100% (177/177), done.
Already using interpreter /usr/bin/python3
Using base prefix '/usr'
New python executable in /var/www/telemetry/venv/bin/python3
Not overwriting existing python script /var/www/telemetry/venv/bin/python (you must use /var/www/telemetry/venv/bin/python3)
Installing setuptools, pip, wheel...done.
INFO  [alembic.runtime.migration] Context impl PostgresqlImpl.
INFO  [alembic.runtime.migration] Will assume transactional DDL.
INFO  [alembic.runtime.migration] Running upgrade  -> 3230c615d6e0, empty message
INFO  [alembic.runtime.migration] Running upgrade 3230c615d6e0 -> 466cf2f35d67, empty message

Install complete (installation folder: /var/www/telemetry)

Once the installation is complete you can use your web browser and view the new server by opening the web browser on your system and type in localhost in the address bar.

You should see a web page similar to the one shown in figure 1:

Telemetry UI

Figure 1: Telemetry UI

Redirect telemetry records

Telemetry records generated by the telemetrics clients are sent to the server location defined in the /usr/share/defaults/telemetrics/ telemetrics.conf configuration file. You can customize this setting by copying this file to /etc/telemetrics/telemetrics.conf and changing the server= setting to your new server location.

  1. Create the /etc/telemetrics directory and make it your current working directory.

    sudo mkdir -p /etc/telemetrics
    cd /etc/telemetrics
  2. Copy the default telemetrics.conf file to the new /etc/telemetrics directory.

    sudo cp /usr/share/defaults/telemetrics/telemetrics.conf
  3. Edit the new /etc/telemetrics/telemetrics.conf file with your editor using the sudo directive and change the server= setting to http://localhost/v2/collector and save this change in the new file.


    You can also use the fully qualified domain name for your server instead of localhost.

  4. Restart the telemetry daemons to reload the configuration file.

    telemctl restart

Test the new telemetry backend server

Clear Linux OS includes a telemetry test probe called hprobe that will send a hello record to the telemetry backend server. To test that the telemetry records are now going to your new destination, run the :command:` hprobe` command to send a hello record to the server as follows:


The record should show up on your new server console as shown in figure 2:

Telemetry UI

Figure 2: Telemetry UI

You have now set up the Clear Linux OS telemetry backend server, and redirected records from your client to your server.

Creating custom telemetry events

For the following steps, we’ll be sending records to the backend server we’ve just set up. If you prefer to keep records locally and not send them to a server, follow the Telemetry guide and enable :record_retention_enabled: in your etc/telemetrics/telemetrics.conf to keep the records locally.

There are two ways to create custom telemetry events: using telem-record-gen and using the telemetry API in your applications.

Using telem-record-gen

Enabling telemetry during installation gives us everything we need to create custom telemetry events, even from C programs, because the telemetry bundle provides a simple pipe-based CLI program named telem-record-gen that can be called trivially:

~ $ telem-record-gen --help
  telem-record-gen [OPTIONS] - create and send a custom telemetry record

Help Options:
  -h, --help            Show help options

Application Options:
  -f, --config-file     Path to configuration file (not implemented yet)
  -V, --version         Print the program version
  -s, --severity        Severity level (1-4) - (default 1)
  -c, --class           Classification level_1/level_2/level_3
  -p, --payload         Record body (max size = 8k)
  -P, --payload-file    File to read payload from
  -R, --record-version  Version number for format of payload (default 1)
  -e, --event-id        Event id to use in the record


The C library ( - man 3 telemetry) uses the same API parameters and will yield the same effect as telem-record-gen.

Let’s try generating a simple heartbeat event with telem-record-gen, similar to the hprobe heartbeat probe that Clear Linux OS includes by default.

~ $ telem-record-gen -c org.clearlinux/hello/world -p "hello there"

We won’t see anything happen on the console, but we can track existing and previous telemetry events with telemctl:

~$ sudo telemctl journal -V -c org.clearlinux/hello/world -i
org.clearlinux/hello/world     Tue 2018-11-06 23:00:48 UTC 72e55923fd21c75142c24dcfe0ae0a79 143f2580dcf80267f8f1dfe448f3c975 75f547ff-e55b-44b1-9333-1106098bd448
hello there

Using the telemetry API in your C application


More details about the the telemetry API are available in the telemetry guide.

Confirm that the telemetrics header file is located on the system at usr/include/telemetry.h The latest version of the file can also be found on github for reference, but installing the telemetry bundle will install the header file that matches your Clear Linux OS version.

You will need to include the following headers in your code to use the API:

#define _GNU_SOURCE
#include <stdlib.h>
#include <stdio.h>
#include <string.h>
#include <telemetry.h>

Use the following code to create the variables we need to hold the data for the record we will be creating:

uint32_t severity = 1;
uint32_t payload_version = 1;
char classification[30] = "org.clearlinux/hello/world";
struct telem_ref *tm_handle = NULL;
char *payload;
int ret = 0;
Type: uint32_t
Value: Severity field value. Accepted values are in the range 1-4, with 1 being the lowest severity, and 4 being the highest severity. Values provided outside of this range are clamped to 1 or 4. [low, med, high, crit]
Type: uint32_t
Value: Payload format version. The only supported value right now is 1, which indicates that the payload is a freely-formatted (unstructured) string. Values greater than 1 are reserved for future use.
Type: char array
Value: It should have the form, DOMAIN/PROBENAME/REST: DOMAIN is the reverse domain to use as a namespace for the probe (e.g. org.clearlinux); PROBENAME is the name of the probe; and REST is an arbitrary value that the probe should use to classify the record. The maximum length for the classification string is 122 bytes. Each sub-category may be no longer than 40 bytes long. Two / delimiters are required.
Type: Telem_ref struct pointer
Value: Struct pointer declared by the caller, The struct is initialized if the function returns success.
Type: char pointer
Value: The payload to set

For this example, we’ll set the payload to “hello” by using asprintf()

if (asprintf(&payload, "hello\n") < 0) {

The functions asprintf() and vasprintf() are analogs of sprintf(3) and vsprintf(3), except that they allocate a string large enough to hold the output including the terminating null byte (‘0’), and return a pointer to it via the first argument. This pointer should be passed to free(3) to release the allocated storage when it is no longer needed.

Create the new telemetry record

The function tm_create_record() initializes a telemetry record and sets the severity and classification of that record, as well as the payload version number. The memory needed to store the telemetry record is allocated and should be freed with tm_free_record() when no longer needed.

if ((ret = tm_create_record(&tm_handle, severity,  classification, payload_version)) < 0) {
 printf("Failed to create record: %s\n", strerror(-ret));
 ret = 1;
 goto fail;

Set the payload field of a telemetrics record

The function tm_set_payload() attaches the provided telemetry record data to the telemetry record. The current maximum payload size is 8192b.

if ((ret = tm_set_payload(tm_handle, payload)) < 0) {
  printf("Failed to set record payload: %s\n", strerror(-ret));
  ret = 1;
  goto fail;

The free() function frees the memory space pointed to by ptr, which must have been returned by a previous call to malloc(), calloc(), or realloc(). Otherwise, or if free(ptr) has already been called before, undefined behavior occurs. If ptr is NULL, no operation is performed.

Send a record to the telemetrics daemon

The function tm_send_record() delivers the record to the local telemprobd(1) service. Since the telemetry record was allocated by the program it should be freed with tm_free_record() when it is no longer needed.

if ((ret = tm_send_record(tm_handle)) < 0) {
  printf("Failed to send record to daemon: %s\n", strerror(-ret));
  ret = 1;
  goto fail;
} else {
  printf("Successfully sent record to daemon.\n");
  ret = 0;
tm_handle = NULL;

return ret;

Full sample application with compiling flags

Create a new file test.c add the following code.

#define _GNU_SOURCE
#include <stdlib.h>
#include <stdio.h>
#include <string.h>
#include <telemetry.h>

int main(int argc, char **argv)
      uint32_t severity = 1;
      uint32_t payload_version = 1;
      char classification[30] = "org.clearlinux/hello/world";
      struct telem_ref *tm_handle = NULL;
      char *payload;

      int ret = 0;

      if (asprintf(&payload, "hello\n") < 0) {

      if ((ret = tm_create_record(&tm_handle, severity, classification,
                                  payload_version)) < 0) {
              printf("Failed to create record: %s\n", strerror(-ret));
              ret = 1;
              goto fail;

      if ((ret = tm_set_payload(tm_handle, payload)) < 0) {
              printf("Failed to set record payload: %s\n", strerror(-ret));
              ret = 1;
              goto fail;


      if ((ret = tm_send_record(tm_handle)) < 0) {
              printf("Failed to send record to daemon: %s\n", strerror(-ret));
              ret = 1;
              goto fail;
      } else {
              printf("Successfully sent record to daemon.\n");
              ret = 0;
      tm_handle = NULL;

      return ret;

Compile with the gcc compiler, using this command:

gcc test.c -ltelemetry -o test_telem

Test to ensure the program is working:

Successfully sent record to daemon.

Verify record was received

To verify that the heartbeat message was received by the telemetry backend server you can check the telemetry client journal, and specify the classification as org.clearlinux/hello/world

sudo telemctl journal -V -c org.clearlinux/hello/world -i
Classification                 Time stamp                  Record ID                        Event ID                         Boot ID
org.clearlinux/hello/world     Tue 2018-11-06 22:58:25 UTC b11db07c58c90d8f496ff963df6c43de 24699c2d60c12d154692875b599ca957 75f547ff-e55b-44b1-9333-1106098bd448
Total records: 1

A full example of the heartbeat probe in C is documented in the source code. For more information about telemetrics in Clear Linux OS refer to the Telemetry guide.

You can also look for the record on the telemetry backend server.