Skip to content

Releases: dora-metrics/pelorus

v2.0.12 🎉

04 Jun 19:33
b2fff70
Compare
Choose a tag to compare

We are very pleased to announce the release of Pelorus operator 0.0.9, that is already available in the OpenShift Marketplace!

Changes

🐛 Bug Fixes

📖 Documentation

  • Introduce developer adoption outcome; add mathjax for rendering formulas @etsauer (#723)

🔡 Other changes

Full Changelog: v2.0.11...v2.0.12

v2.0.11 🎉

21 Aug 16:44
976b3be
Compare
Choose a tag to compare

We are very pleased to announce the release of Pelorus operator 0.0.8, that is already available in the OpenShift Marketplace!

New & Notable

containerimage exporter now uses certificate from the mounted to pod location

Pelorus Prometheus instance with default OpenShift and Kubernetes metrics

Changes

🚀 Features

  • Allow skopeo to use certificate from the mounted to pod location @mpryc (#1030)
  • Provide a default configuration for integrating metrics from openshif… @etsauer (#995)

📖 Documentation

🔡 Other changes

Full Changelog: v2.0.10...v2.0.11

v2.0.10 🎉

07 Jun 11:48
dec6ec9
Compare
Choose a tag to compare

We are very pleased to announce the release of Pelorus operator 0.0.7, that is already available in the OpenShift Marketplace!

New & Notable

New type for committime: containerimage

Pelorus can now collect commit data from a Container image using the new committime exporter type: containerimage. To learn how to setup Pelorus to use this new commitime exporter type, check the documentation.

New provider support for failure exporter: Azure Boards

Pelorus has now support for Azure DevOps issue tracker: Azure Boards. To learn how to setup Pelorus to collect data from it, check the documentation.

New way to see applications in Grafana

It is now possible to see applications by different hierarchy level in Software Delivery Performance - By App dashboard in Grafana. To learn how to send application names to Pelorus to enable this feature, check the documentation.

Screenshot from 2023-06-06 11-58-01

Changes

🚀 Features

🐛 Bug Fixes

📖 Documentation

🔡 Other changes

Full Changelog: v2.0.9...v2.0.10

v2.0.9 🎉

12 Apr 09:15
26742a6
Compare
Choose a tag to compare

We are very pleased to announce the release of Pelorus Operator 0.0.6, that is already available in the OpenShift Marketplace!

The biggest change is outside of our Pelorus source code - now Pelorus have it's own home within dora-metrics organization with the documentation available at https://dora-metrics.io.

Why Pelorus has it’s own organization ?

Konveyor is now a Cloud Native Computing Foundation (CNCF) Sandbox project, meaning it needs to follow CNCF set of rules for Kubernetes native projects. It has also been transferred to be managed by the Foundation.

Current Pelorus primary objective is to excel in software delivery performance metrics for the OpenShift ecosystem, which differs from the Kubernetes native approach, that is our secondary goal.

Release Notes

New & Notable

Webhook Exporter

Added option to secure webhook payload (#926)

Failure Time Exporter - JIRA exporter

Added Personal Access Token (PATs) as a form of JIRA authentication. (#918)

Commit Time Exporter - Azure devops exporter

A bug fix, which takes the Azure commit time back in shape. (#900)

Other Changes

Full Changelog: v2.0.8...v2.0.9

v2.0.8 🎉

11 Mar 20:55
88bff21
Compare
Choose a tag to compare

We are very pleased to announce the release of Pelorus operator 0.0.5, that is already available in the OpenShift Marketplace!

This release is packed with new features and bug fixes that make it easier and more enjoyable to engage.

New & Notable

Failure Time Exporter - PagerDuty backend

The inclusion of PagerDuty means that data on application failures can now be collected from a variety of sources, including Jira, GitHub, ServiceNow, and PagerDuty itself.

External Pelorus Exporter

It's now easier to monitor applications on a cluster different from the one where the Pelorus is deployed via documented external_prometheus_hosts option. This is made possible by allowing you to configure the Pelorus to collect data from exporters residing in other clusters or even outside of clusters (a simple HTTP connection to that exporter has to be made available from the Pelorus itself).

Webhook Exporter

In previous versions of Pelorus data was collected via tools that pulled data from various sources. In this latest release we are enabling users to push data to Pelorus. By pushing data vs. pulling users with security and infrastructure constraints will find it easier to collect and measure metics that also better fits their security requirements.

Introducing a new type of Pelorus exporter that enables integration with a wide range of build, deployment, and incident reporting software.

The Webhook exporter is capable of receiving data from any service that sends an appropriate HTTP POST request.

Moving forward, this Exporter will also allow for the creation of plugins that support other metric types like SLAs or SLOs, as well as the ability to receive webhooks directly from other services such as Jenkins or GitHub.

Usability Improvements (UX)

Improved OpenShift form to configure and create Pelorus instance

We have enhanced the Pelorus form for creating an it's OpenShift instance. Thanks to the reworked openAPIV3Schema, you can now conveniently configure a range of Pelorus options, such as exporter instances, Prometheus, or Thanos, directly through the OpenShift UI.

Screenshot from 2023-03-13 13-30-45

Changes

🔡 Other changes

Full Changelog: v2.0.7...v2.0.8

v2.0.7 🎉

02 Mar 14:38
3ee9fac
Compare
Choose a tag to compare

Changes

🔡 Other changes

  • New release of Pelorus with new pelorus operator to fix #849 @mpryc (#850)

Full Changelog: v2.0.6...v2.0.7

v2.0.6 🎉

28 Feb 14:08
c7478af
Compare
Choose a tag to compare

Changes

📖 Documentation

🔡 Other changes

Full Changelog: v2.0.1...v2.0.6

v2.0.1 🎉

17 Oct 19:00
c806369
Compare
Choose a tag to compare

Changes

  • Adds back support for the BitBucket 1.0 API in the BitBucket committime exporter. (#680)

🔡 Other changes

Full Changelog: v2.0.0...v2.0.1

v2.0.0 🎉

22 Sep 13:07
Compare
Choose a tag to compare

We are very pleased to announce the release of Pelorus 2.0.0!
This is the minimum viable release for Pelorus that brings the stability, features and the documentation required for our upstream community.

New & Notable

Generic Commit Time: Tekton, Binary Builds, and External Images

Support for commit time from Tekton was highly requested. Because everyone's workflow is highly customizable, we resisted the temptation to guess. Users can run a new image exporter, and can configure it to look for commit information in whatever image annotation they use.

Because they have full control over git information while building, it doesn't even need to reach out to a git forge (GitHub, BitBucket, etc.)!

As a consequence, this now supports:

  • Tekton
  • Binary Builds
  • Images put into openshift by other means

Day 2 Prometheus: Data Storage & Backup

  • Expose PV configuration for Prometheus
  • S3 Prometheus / Thanos data storage

GitHub Failure Exporter

  • Pelorus support for Github issues using issue labels

Jira Exporter Improvements

  • Expanded support for number of issues
  • ConfigMap support

Custom Certificates

You can now use custom certificates for most exporters.
Supported are:

Exporter Type Exporter Backend
Commit Time BitBucket
Commit Time Gitea
Commit Time GitHub
Commit Time GitLab
Failure GitHub

Usability Improvements (UX)

  • Pelorus exporters are now, by default, run from published images. Previously, every user was building their own image with an S2I workflow.
  • Configuration item names have been made more consistent and simpler.
  • Each exporter can now be configured from ConfigMaps, making maintenance easier.
  • Pelorus's overall configuration has been simplified.
  • A troubleshooting script has been added that will help solve the question of "why isn't my data showing up in pelorus?"
  • We now have a unified configuration system, which will log everything the exporter was configured with at startup. This will help with debugging client deployments.

Documentation

  • Configuration documentation has been completely overhauled.
  • Developer docs have been improved overall.

Demo

We have a new demo that:

  • Shows more of the pelorus workflow
  • Shows users how to use binary and 3rd party application builds with Pelorus
  • Shows off Tekton support
  • Serves as a bit of QA

Quality & Bug Fixes

  • Now documented: our openshift version support, and exporter testing strategy.
  • Fixed: time zones were incorrectly handled in some cases
  • Prow CI integration jobs on OpenShift 4.9 - 4.11 executing 70+ tests each
  • Fixed: certain metrics now report their time as the collection timestamp, making some queries / dashboards more correct.
  • We now have a unified configuration system, which will log everything the exporter was configured with at startup. This will help with debugging client deployments. This also supports falling back to older configuration item names in a cleaner manner.
  • Errors are reported in a more detailed manner when examining deeply-nested data, which is useful when inspecting openshift objects.
  • The GitLab committime collector's performance has been improved.

Developer Experience

  • We now have a way to set up a consistent developer environment with a single command, including other commandline tools (such as the openshift client).
  • We now consistently format the code automatically.

Miscellaneous

  • The GitHub committime exporter can now run without authentication, which is useful for public repositories.
  • We now eat our own dogfood by tracking our own development with pelorus.

Release notes between 2.0.0 and 1.8.2

🎉 Release

  • major release of the Pelorus project - MVR (#667)

🔡 Other changes

Full Changelog: v1.8.2...v2.0.0

v1.8.2 🎉

20 Sep 18:51
894553a
Compare
Choose a tag to compare

Changes

🔡 Other changes

  • Pre-mvr release (1.8.2) @mpryc (#655)
  • Bump grafana version to the newest one. @mpryc (#656)
  • Add script to view all grafana queries in the SDP dashboard @KevinMGranger (#661)
  • Validation of Thanos data in e2e script @mpryc (#637)
  • Add option to configure Prometheus maximum storage capacity @mpryc (#649)
  • Revert "Report resource timestamp as metric timestamp" @weshayutin (#653)
  • Automate tekton subsequent runs, add timeout for git clone @mpryc (#648)
  • verify both the app and pelorus w/ tekton @weshayutin (#647)
  • Add option to configure Prometheus retention @mpryc (#640)

Full Changelog: v1.8.1...v1.8.2