Skip to content

Releases: freepik-company/tekton-exporter

tekton-exporter-helm-chart-0.3.0

14 Nov 10:54
Compare
Choose a tag to compare

A Helm chart to deploy Tekton Exporter into a Kubernetes cluster

v0.3.0

21 Feb 01:59
Compare
Choose a tag to compare

Changes

  • Refactor functions in charge of parsing Kubernetes resources: objects from the watchers' events are now handling the errors more carefully
  • Watchers and events' processing logic are now separated: a shorter watcher is simpler and easier to debug. Now the watcher calls a handler function for each event. When the event fails to be processed, the watcher log the failure but goes for the next event

Contributors

@achetronic

v0.2.1

20 Feb 21:09
4887f73
Compare
Choose a tag to compare

Fixes

  • Watchers for *Run objects are restarted when they return an error
  • Manage most errors inside goroutines (watchers) instead of throwing them to the main process (treat them as completely separated processes)
  • Inside watchers, extracting information from malformed *Run objects can end with missing data. Now the default behavior is to log the error and skip the object not to crash other metrics
  • Error messages templates were moved to constants
  • GVR definition for Taskrun and Pipelinerun resources are now defined as variables on top

Contributors

@achetronic

v0.2.0

18 Feb 04:08
Compare
Choose a tag to compare

Fixes

  • Refactor some functions: This will allow the project implement more metrics when needed with ease

Features

  • Add namespace label to all the metrics
  • Add _duration_seconds metric for PipelineRun and TaskRun objects. Moreover, those metrics have two new labels: start_timestamp and completion_timestamp. These timestamps are fixed, so they will not increase the cardinality of the metric and will add some benefits on dashboards that will use it

Contributors

@achetronic

v0.1.1

16 Feb 19:57
Compare
Choose a tag to compare

Fixes

  • Post-parse comma-separated flag --populated-labels: Depending on how the flag was passed and the environment in which the command-line interface (CLI) was running, the Cobra flags library did not properly separate the values when they were divided by commas. This issue did not occur when setting the flag multiple times with just one value per setting. To address this, we now perform post-processing on the flag to ensure that commas are consistently used as separators as expected.

Contributors

@achetronic

v0.1.0

16 Feb 11:22
Compare
Choose a tag to compare

🎉🎉 First release

Contributors

@achetronic