Information Collection
To better understand real-world usage patterns, quality and reliability, CASA collects runtime telemetry and crash reports from users and sends periodic reports back to NRAO. This information is anonymous with no personal identifiable information (PII) or science data included.
Telemetry
Telemetry records task usage activity (task name, start time, end time) during CASA runs. Periodically, these reports will be batched together and sent to NRAO.
You can disable telemetry by adding the following line in ~/.casa/config.py
telemetry_enabled = False
Telemetry adds log files in the "rcdir" (e.g., ~/.casa) directory and submits the data at CASA startup after a predefined interval. This can be configured in the ~/.casa/config.py file by setting telemetry_submit_interval to a desired value in seconds. The default value is 1 week.
The log file cache directory can be changed by setting "telemetry_log_directory" in ~/.casa/config.py. "telemetry_log_directory" must be an absolute path.
Maximum telemetry log usage can be set with "telemetry_log_limit" (in kilobytes). CASA will check for the logfile size periodically and disable Telemetry when the limit is reached. The check interval can be set with "telemetry_log_size_interval" (seconds).
Summary of all available options in .casa/config.py:
telemetry_log_directory: /tmp
telemetry_log_limit: 1650
telemetry_log_size_interval: 30
telemetry_submit_interval: 20
Crash Reporter
Crash reports are triggered whenever a CASA task terminates abnormally (e.g., unhandled C++ exception, segfault, etc.). The crash reports include:
- program call stack
- filesystem mount information
- CASA log
- memory information
- operating system version
- CPU information
You can disable crash reports by adding the following line in ~/.casa/config.py
crashreporter_enabled = False