Telemetry
WarpBuild telemetry and monitoring information
WarpBuild collects telemetry data to monitor runner performance and improve the platform. This page provides information about the telemetry collection process and port usage.
Telemetry Collection
WarpBuild agents running on your runners collect the following telemetry data:
- CPU, memory, filesystem, and network utilization metrics. This helps with understanding resource bottlenecks on the runner.
- System logs for capturing WarpBuild and other service behaviors, useful for debugging runner issues.
The collected telemetry logs and metrics can be viewed in the WarpBuild UI. To view the metrics and logs for a runner go to Instances > Click on 'Graph' icon for a runner in the list of instances. This will take you to the metrics and logs for the particular runner instance.
The chart displays info about the resource utilization on your runner instance.
The logs contains the syslogs of your runner. This is not the same as GitHub Actions runner logs that can be seen in the GitHub Actions UI.
Port Usage
WarpBuild telemetry uses port 33931 for data collection and communication with the WarpBuild platform.
Data Privacy
WarpBuild telemetry collection follows our privacy and security policies:
- No sensitive data is collected through telemetry. We only collect syslogs and utilization metrics of the runner like CPU, memory, filesystem and network.
- All telemetry data is encrypted in transit.
If you have any queries regarding the telemetry, please reach out at [email protected].
Last updated on