search

thoth-station / kebechet

I'm Kebechet bot, goddess of freshness - I will keep your source code fresh and up-to-date
24 stars 20 forks source link

Add metrics about workflow latency (per manager) #993

Open pacospace opened 2 years ago

pacospace commented 2 years ago

As Thoth Owner,

I want to have a way to monitor latency for each of the Kebechet managers for the SLO

sesheta commented 2 years ago

@pacospace: This issue is currently awaiting triage. If a refinement session determines this is a relevant issue, it will accept the issue by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
KPostOffice commented 2 years ago

Hey @pacospace can you explain a bit more what you are looking for? Are you asking for metrics on how long the managers take to run?

pacospace commented 2 years ago

Hey @pacospace can you explain a bit more what you are looking for? Are you asking for metrics on how long the managers take to run?

We currently can see in metrics the time taken by the kebechet workflow, but we don't know how much time is used from each manager activated. It would be useful to also monitor how much time each manager takes as we run all managers in the same workflow.

pacospace commented 2 years ago
codificat commented 2 years ago

/triage accepted /assign @KPostOffice /priority important-soon

sesheta commented 2 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

goern commented 2 years ago

/remove-lifecycle stale /priority backlog

sesheta commented 2 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

codificat commented 2 years ago

hmmm it seems the bots were taking a nap during the previous attempt.

/remove-lifecycle rotten /priority backlog /remove-priority important-soon

codificat commented 2 years ago

/sig user-experience