Telemetry data details

I use the telemetry information for two purposes,

1. to capture bugs, ranging from obvious crashes to obscure memory leaks, and
2. to identify areas and parts of algorithms that run slower than expected.

While hard crashes eventually result in a support request, people seldom report performance problems, making the data collected during actual recoveries indispensable.

General

All Klennet tools send the following information:

• Software build number.
• General system information
  • operating system version, including service pack number, if installed;
  • list of installed locales;
  • time zone;
  • CPU model and number of cores;
  • amount of physical memory installed;
  • hypervisor type if running inside a virtual machine.
• List of all physical disks attached to the system, including models, but not serial numbers.
• Performance data for long operations, including the time it took to complete the operation, CPU, disk, and memory usage.
• Crash data, consisting of error condition, error code whenever applicable, and stack trace.
• Normal shutdown indication (to differentiate between normal shutdown, crash, and encountering an endless loop).

Data specific to Klennet Recovery

• List of all the features used.
• Validation results - number of files declared valid or invalid after recovery is complete.
• List of file extensions not recognized during validation. The top five extensions are sent.
• When using RAID analysis, the RAID level and block size.
• When creating a disk image, a target disk image format is sent.

Data specific to Klennet ZFS Recovery

• If encrypted pool analysis is enabled, the number and type of passwords and keys provided are sent, but not the keys themselves.
• Disk layout analysis log, including
  • some disk addresses but not data at these addresses;
  • scoring information;
  • final vdev layout (RAID level and disk order).
• The number of object sets processed, the number of files discovered, and the total size of these files.
• The number of files for which checksums were tested and the number of valid files (with matching checksums).
• Various cache performance information.
• Number and distribution of bad blocks across disks.

Data specific to Klennet Carver

• Configuration settings.
• Block size detection scoring data.
• The number of files processed; the number of files declared good and declared damaged (including scoring data).
• Fragmentation data (how many files had a specific number of fragments on disk).
• For some of the image and video files (when incompatible encoding is encountered),
  • codec identifiers;
  • image resolution;
  • audio sampling rate.

Discontinued tools

Data specific to Klennet Disk Imager

• The number of bad blocks or areas encountered while copying.
• The number of successful and unsuccessful attempts to reset the USB disk and/or hub. On a failed reset attempt, the model name of the offending device is sent, but not its serial number.

Data specific to Klennet RAID Viewer

• GPU model, amount of GPU memory installed, and the number of computational groups and threads available.