Observability
GitHub Actions runner observability and monitoring information
WarpBuild collects telemetry data to display metrics and logs for your runners. This page provides information about the observability collection process and port usage.
Observability Collection
WarpBuild agents running on your runners collect the following observability 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 logs and metrics can be viewed in the WarpBuild UI's Observability page.
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.
Observability only collects metrics and logs for jobs that are longer than ~1 minute.
Port Usage
WarpBuild observability uses port 33931 for data collection and communication with the WarpBuild platform and uses OpenTelemetry for data collection.
Data Privacy
WarpBuild observability 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 observability data is encrypted in transit.
If you have any queries regarding the observability, please reach out at [email protected].
Last updated on