Skip to content

Conversation

@khrm
Copy link
Contributor

@khrm khrm commented Jun 22, 2021

Added an initial metrics implementation for TektonPipeline and
TektonTrigger.

Changes

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

See the contribution guide for more details.

Release Notes

@tekton-robot tekton-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. labels Jun 22, 2021
@tekton-robot tekton-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jun 22, 2021
@tekton-robot tekton-robot added size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jun 22, 2021
@khrm khrm force-pushed the metrics branch 2 times, most recently from 9e90ecb to e597a78 Compare June 22, 2021 14:02
@khrm khrm changed the title WIP: Add Install Metrics for TektonPipeline and TektonTrigger Add Install Metrics for TektonPipeline and TektonTrigger Jul 5, 2021
@tekton-robot tekton-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 5, 2021
@nikhil-thomas
Copy link
Member

/approve

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 4, 2021
@nikhil-thomas
Copy link
Member

@khrm
this patch will count each reconcile loop as a new install, wouldn't it. 🤔

@nikhil-thomas
Copy link
Member

/hold
holding just to make sure that we all agree on what we count as an install. 🧑‍💻

@tekton-robot tekton-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 4, 2021
@tekton-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nikhil-thomas, vdemeester

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:
  • OWNERS [nikhil-thomas,vdemeester]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@savitaashture
Copy link
Contributor

savitaashture commented Aug 10, 2021

@khrm Can we add logic for Dashboard also to count installation ?

@khrm
Copy link
Contributor Author

khrm commented Aug 12, 2021

@savitaashture Sure we can add that.

Added an initial metrics implementation for TektonPipeline and
TektonTrigger.
@tekton-robot tekton-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 4, 2021
@tekton-robot
Copy link
Contributor

@khrm: PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@vdemeester
Copy link
Member

@khrm needs a rebase
@nikhil-thomas @tektoncd/operator-maintainers @tektoncd/operator-collaborators we should consider operator installation and component installation (pipeline, …) as two different metrics.

@nikhil-thomas
Copy link
Member

@khrm needs a rebase
@nikhil-thomas @tektoncd/operator-maintainers @tektoncd/operator-collaborators we should consider operator installation and component installation (pipeline, …) as two different metrics.

yup, the operator installation metric will be taken care of by OLM.

With the recent refactoring in our reconcilers by @sm43 , we can differentiate between a component install, component upgrade and regular reconcile events. This will help us take care of the component specfic metrics better.

@nikhil-thomas
Copy link
Member

closing this as #445 merged

@khrm khrm deleted the metrics branch June 7, 2023 12:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants