pelorus
by
dora-metrics

Description: Automate the measurement of organizational behavior

View on GitHub ↗

Summary Information

Updated 1 hour ago
Added to GitGenius on August 6th, 2021
Created on January 20th, 2019
Open Issues & Pull Requests: 155 (+0)
Number of forks: 85
Total Stargazers: 254 (+0)
Total Subscribers: 18 (+0)

Issue Activity (beta)

Open issues: 116
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,210 days
Stale 30+ days: 116
Stale 90+ days: 116

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • kind/bug (95)
  • docs (73)
  • kind/feature (70)
  • mvr (56)
  • needs-triage (44)
  • ci (32)
  • committime-exporter (30)
  • tool-sharpening (28)

Most active issues this week

No issue events were indexed in the last 7 days.

Repository Insights (GitGenius)

Median issue/PR response: 0.0 hours
Mean response time: 208.7 days
90th percentile: 739.8 days
Tracked items: 22

Most active contributors

Detailed Description

Pelorus is a Python-based tool designed to automate the measurement of organizational behavior through DORA metrics, which are key performance indicators for software delivery and operational excellence. The project is maintained by the dora-metrics organization and provides a framework for collecting, analyzing, and reporting on metrics that reflect DevOps maturity and continuous delivery capabilities.

The repository focuses on implementing DORA metrics measurement, which includes deployment frequency, lead time for changes, mean time to restore, and change failure rate. These metrics are fundamental to understanding software delivery performance and organizational transformation. Pelorus serves as an observability and monitoring solution that enables teams to track their progress toward continuous delivery excellence and benchmark their performance against industry standards.

According to GitGenius activity tracking, the repository shows moderate engagement with a median issue and pull request response latency of 0.0 hours and a mean latency of 5008.4 hours across 22 tracked items, indicating variable response times. The most frequently applied issue labels are needs-triage with 17 occurrences, kind/bug with 11 occurrences, and kind/feature with 6 occurrences, suggesting the project maintains an active backlog of improvements and bug fixes. The primary contributor tracked by GitGenius is etsauer with 28 events, followed by vimalkansal with 4 events and achdmbp with 3 events.

The project is classified across multiple domains including benchmarking, performance measurement, continuous integration, and site reliability engineering. It integrates with Kubernetes environments and is recognized as part of the Cloud Native Computing Foundation ecosystem. The tool functions as a data collection and analysis framework for distributed systems, enabling infrastructure monitoring and service performance evaluation.

The repository documentation indicates that the current active development occurs on the master branch, while the branch containing these details represents Pelorus Next, a future iteration not yet in active use. The project includes Prow CI periodic end-to-end tests for OpenShift version 4.16, demonstrating integration with Red Hat's OpenShift platform and continuous testing infrastructure.

GitGenius identifies overlapping contributors between Pelorus and other repositories including kgateway-dev/kgateway, velero-io/velero, and vmware-tanzu/velero, suggesting shared development community involvement across cloud-native and infrastructure projects. The classification as a reporting framework and analysis tool reflects its role in aggregating metrics data and presenting actionable insights for DevOps teams and organizational leadership seeking to measure and improve their software delivery capabilities.

pelorus
by
dora-metricsdora-metrics/pelorus

Repository Details

Fetching additional details & charts...