Influx database

From version 2.60 TimeToPic Logger will have capability send TimeToPic traces (events and valueabs) to Influx database for further analysis. With time series it is possible to analyse numbers when logs are very long in terms of time (and perform additional analysis with other tools). Secondly, numbers are collected to database that makes sharing of results easier.

Setup requirements

To test you need following:

  • TimeToPic Logger v2.60 installed
  • TimeToPic test app installed (comes with installer bundle)
  • Influx database running somewhere
  • Influx database ports are accessible (HTTP) by computer that runs TimeToPic Logger
  • Influx database data write is enabled without authentication
  • Influx Chronograf installed onto Influx machine


Check that Influx is running and take down server address.

Restart TimeToPic Logger. Then press settings button. This is active only when there is no active connection.

Type connection string to edit box, press enter and click done. Enter your connection string using notation "http://<address>:<port>". Influx data port is typically 8086.

Initial test

Start test app, move mouse top on green boxes.

If connection to Influx is established, you should see database icon on right of settings icon. If you move mouse top of it, it will reveal to where connection is made.

Refresh Influx db view and you should see new database.

Open data explorer, click "USEDMEMKB" and value. You should see some kind of time serie about memory use.

Notation of tracelines

TimeToPic Logger sends TimeToPic events and TimeToPic valueabs kind log-lines to Influx. This allows measuring of values (values) and event durations (event).

Channel name is used as measurement name as is.

If channel name follows format "InfluxExample|tag1=tagvalue1|myTag=exampleTagValueC", TimeToPic Logger creates Influx tags from channel name. Previous example will be interpreted as tag following way:

"InfluxExample" will be measurement name, tag1 will name of tag. Tagvalue1 will be tag1 value. MyTag will be name of 2nd tag. ExampleTagValueC, will name of tag.

So, if you want trace value without tags, use <measurementname> as channelname.

If want tags, use notation <measurement>|<tagname1>=<tagvalue>|<tagname2>=<tagvalue>. Tagnames needs to be unique.

Current limitations

For now following limitations apply:

  • http connection only ( no https)
  • no authentication. R&D use!
  • If connection drops (no response to heartbeat ping), it is not recovered.
  • Database is always wiped when session starts.