Telemetry FAQ

This is a list of frequently asked questions about Telemetry.


How long does it take to get Telemetry up and running?
This depends on the complexity of your application, but in most cases you can get things up and running in about 15 minutes.
How hard is it to remove Telemetry when I'm ready to ship my software?
Simply #define NTELEMETRY 1, recompile, and it's gone!
How much overhead does Telemetry take?
In most situations, Telemetry's overhead scales directly with the amount of markup you have enabled. Telemetry uses a single memory buffer you provide at startup so its memory impact is well understood.
Can I have Telemetry 'always on'?
Yes! It's often a good practice to leave Telemetry on but 'paused', only recording when you encounter a particularly slow area of your app.
How big are Telemetry's data files?
Uncompressed Telemetry data files vary in size depending on the amount of markup enabled, but long sessions can easily run into multiple gigabytes of data.
What file format does Telemetry use?
Telemetry uses a custom file format. Command line tools are available to extract session data into .CSV files.
What platforms does Telemetry support?
Telemetry has run-time support for Windows (XP SP3, Vista, 7, 8, 10), and XBOX One, Sony PS4, Android, and Linux (x86 and ARM). The Telemetry Visualizer is available for 64-bit Windows.
Do you offer .Net, Python, Lua, etc. bindings?
We do not provide bindings for alternate languages, however Telemetry is a C/C++ library and as such is easy to integrate with most scripting languages