Running Lightbend Telemetry with the sandbox basically means two things; start the sandbox and then run your configured application.


The sandbox utilizes ConductR and Docker to start all the required software. The section below shows you how to run and manage the ConductR sandbox.

Run sandbox

To run Lightbend Telemetry with the ConductR sandbox, use the ConductR sandbox command with the monitoring feature enabled and specify the versions of ConductR and Cinnamon to use.

$ sandbox run 2.1.4 --feature monitoring v2.5

This will start a Docker image as a container containing ConductR bundles for Elasticsearch, Kibana and Grafana.

The monitoring feature version can be set to a specific version of Cinnamon, or to a version series. If no version is specified then the latest version will be used. For example, these are possible options for this version of Cinnamon: "v2", "v2.5", "v2.5.0".

Make sure that the sandbox environment is up and running before proceeding. This means you should wait until all ConductR bundles are in the #RUN column when typing conduct info:

$ conduct info
ID               NAME                     #REP  #STR  #RUN
bdfa43d-e5f3504  conductr-haproxy            1     0     1
85dd265          conductr-elasticsearch      1     0     1
06d370b          conductr-kibana             1     0     1
d4bdc6c          cinnamon-grafana-docker     1     0     1

Stop sandbox

To shut the sandbox down:

$ sandbox stop

Run application

Once the sandbox environment is running the next step is to run your configured application. The way you run it depends on the build tool you have selected.

Before your application starts to run, Lightbend Telemetry will be initialized. If you have followed the configuration setup then data is going to be published from your application into Elasticsearch. This is done in regular pulses and it may take a couple of seconds before data is starting to show up in Grafana and Kibana.


ConductR commands

This section contains some good-to-know ConductR commands:

# List all bundles that are running in the sandbox environment
$ conduct info

# Load/start/stop/unload bundles
$ conduct load <BUNDLE_ID>
$ conduct run <BUNDLE_ID>
$ conduct stop <BUNDLE_ID>
$ conduct unload <BUNDLE_ID>

# Help
$ conduct help