Telemetry

Robility flow uses anonymous telemetry to collect statistics about feature usage and performance. The Robility flow team uses this data to identify popular features and areas that need improvement based on actual usage patterns. This helps prioritize development efforts on the most impactful changes and popular features.

Privacy

The Robility flow team respects your privacy, and the team is committed to protecting your data.

Robility flow telemetry doesn’t collect any personal information or sensitive data. All telemetry data is anonymized and used solely for improving Robility flow.

Opt out of telemetry

To opt out of telemetry, set DO_NOT_TRACK=True in your Robility flow environment variables before starting Robility flow. This disables telemetry data collection.

Data that Robility flow collects

Robility flow telemetry collects data on flow runs, your environment, and component usage.

Run

This telemetry event is sent every time a flow is executed.

a. IsWebhook: Indicates whether the operation was triggered with a webhook.
b. Seconds: Duration in seconds for how long the operation lasted, providing insights into performance.
c. Success: Boolean value indicating whether the operation was successful, helping identify potential errors or issues.
d. ErrorMessage: Provides error message details if the operation was unsuccessful, aiding in troubleshooting and enhancements.

Shutdown

This telemetry event captures information about application lifecycle and runtime duration.

a. TimeRunning: Total runtime before shutdown, which is useful for understanding the application lifecycle and optimizing uptime.

Version

This telemetry event is sent once when the telemetry service starts.

a. Version: The specific version of Robility flow used, which helps in tracking feature adoption and compatibility.
b. Platform: Operating system of the host machine, which helps determine the most popular platforms for development and testing efforts
c. Python: The version of Python used, assisting in maintaining compatibility and support for various Python versions.
d. Arch: Architecture of the system, such as x86 or ARM, which helps prioritize hardware optimization and testing in the Robility flow codebase.
e. AutoLogin: Indicates whether the auto-login feature is enabled, reflecting user preference settings.
f. CacheType: Type of caching mechanism used, which impacts performance and efficiency.
g. BackendOnly: Boolean indicating whether Robility flow is running in backend-only mode, useful for understanding deployment configurations.
h. Desktop: Indicates whether Robility flow is running in desktop mode (Robility flow Desktop), helping to understand usage patterns across different deployment types.

Playground

This telemetry event monitors performance and usage patterns in the Playground environment.

a. Seconds: Duration in seconds for Playground execution, offering insights into performance during testing or experimental stages.
b. ComponentCount: Number of components used in the Playground, which helps understand complexity and usage patterns.
c. Success: Success status of the Playground operation, aiding in identifying the stability of experimental features.

Component

This telemetry event is sent for each component execution.

a. Name: Identifies the component, providing data on which components are most utilized or prone to issues.
b. Seconds: Time taken by the component to execute performance metrics.
c. Success: Whether the component operated successfully, which helps in quality control.
d. ErrorMessage: Details of any errors encountered, crucial for debugging and improvement.