Telemetry Overview
Telemetry Guide
Introduction
Devtron collects anonymous telemetry data that helps the Devtron team in understanding how the product is being used and in deciding what to focus on next.
The data collected is minimal, non PII, statistical in nature and cannot be used to uniquely identify an user.
Please see the next section to see what data is collected and sent. Access to collected data is strictly limited to the Devtron team.
As a growing community, it is very valuable in helping us make the Devtron a better product for everyone!
What data is collected
Here is a sample event JSON which is collected and sent:
Key | Description |
---|---|
| Name of the event |
| Unique user id or client id |
| devtron version |
| kubernetes cluster version |
| event type |
| Unique client id |
Inception (operator)
Inception sends the installation and upgradation events of the Devtron tool to measure the churn rate.
Events which are sent by Inception :
InstallationStart
InstallationInProgress
InstallationSuccess
UpgradeStart
UpgradeInProgress
UpgradeSuccess
Event is same as sample json with event name mentioned above.
Devtron (orchestrator)
Orchestrator sends the summary events of the Devtron tool to measure the daily usage.
Events which are sent by Orchestrator :
Heartbeat
Summary
Orchestrator sends the Summary
event once in 24 hours with the daily operation done by user.
Here is a sample summary JSON which is available under properties:
Key | Description |
---|---|
| cd pipeline created in last 24 hour |
| ci pipeline created in last 24 hour |
| total cluster in the system |
| total environment in the system |
| total non prod apps created |
| total user created in the system |
Dashboard(Not Collected Anymore)
Dashboard sends the events to measure dashboard visit of the Devtron tool.
Events which are sent by Orchestrator : * identify
Dashboard sends the identify event when user visits the Dashboard for the first time.
Where data is sent
The data is sent to Posthog server.
Last updated