Frequently Asked Questions
What is the pipetrics?
Pipetrics is a purpose-built solution for GitHub Actions observability, designed to close the gap between CI/CD pipelines and modern monitoring. In our experience, it’s surprisingly difficult to track long-term performance metrics in GitHub Actions workflows.
Pipetrics solves this by automatically collecting historical run data and providing real-time metrics for future executions. With out‑of‑the‑box support, you can gain deep pipeline performance insights without the heavy setup - no need to deploy Prometheus exporters yourself.
Our primary goal is to make GitHub Actions observability seamless and easy to integrate into your existing observability stack. That’s why we offer native Grafana integration via a Postgresql data source - enabling you to visualize, analyze, and set up Grafana alerts on key workflow metrics effortlessly.
Why use Pipetrics instead of Prometheus GitHub exporters?
There are several GitHub Actions exporters that expose similar metrics. However, the core issue lies in how Prometheus handles data. It’s a time-series database-great for continuous, regular metrics. But CI/CD pipelines aren’t like that.
Pipelines are typically event-driven. For example, a linter might run on every push, while a production deployment might happen just once a week. This irregularity causes visualizations in Prometheus to become unreliable—some jobs may even vanish when you zoom out on a graph.
Pipetrics takes a different approach. We use Postgresql instead of a time-series database, allowing us to model pipeline data more accurately. This enables consistent, actionable views-easily visualized in our built-in dashboard or Grafana.
How can I share access to repository in Pipetrics?
Security is a core principle of Pipetrics. We respect your existing permissions and assume you know best who should access your repositories. That’s why we automatically mirror the access rights of your current team and direct repository members-granting them the same access to Pipetrics insights without extra configuration.
What is the “unknown” workflow?
We mark workflows as “unknown” when we can’t retrieve their names from the GitHub API. This typically happens if a workflow has been deleted from the repository, and we can no longer access its name. However, the GitHub API still returns information about past runs of that workflow.