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

Create SLI/SLO to monitor the use of each Kebechet Manager #546

Open pacospace opened 3 years ago

pacospace commented 3 years ago

Is your feature request related to a problem? Please describe. As Thoth Manager,

I want to have SLI about the use of Kebechet managers to monitor and prioritize next features.

Describe the solution you'd like Check how many PR are opened and merged by managers

Describe alternatives you've considered

Additional context

goern commented 3 years ago

/kind feature

goern commented 3 years ago

/milestone investigator-v0.5.0

goern commented 3 years ago

@xtuchyna @pacospace what is the status of this?

xtuchyna commented 3 years ago

@xtuchyna @pacospace what is the status of this?

I am currently working on a dashboard visualization for today's demo and the last thing that remains is just to schedule workflows for all repos that use kebechet managers.

pacospace commented 3 years ago

-> https://github.com/orgs/thoth-station/projects/13#card-50305419

pacospace commented 3 years ago

@xtuchyna what is the status? can we have some bullet points on what is missing? Thanks!!

xtuchyna commented 3 years ago

Requirements as for know:

goern commented 3 years ago

and... could we resemble something like the github punchcard for all the contributions kebechet is going? coming back to the question: "how much work is the bot saving the humans?"

pacospace commented 3 years ago

Requirements as for know:

  • [x] Check mi-scheduler new version released ( thoth-station/mi-scheduler#72 )
  • [ ] Check that creating job from mi-scheduler cronjob works and gathers knowledge
  • [ ] Fix CronJob not scheduling hourly (and maybe change that for daily)
  • [ ] Store metrics out of gathered knowledge on Ceph

pre-requisiites:

Steps:

sesheta commented 3 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 3 years ago

What is the status on this? @xtuchyna are you actively working on it?

/remove-lifecycle stale

xtuchyna commented 3 years ago

@goern this should be done, I am gonna test the data aggregation and let you know

goern commented 3 years ago

/kind demo

goern commented 3 years ago

/priority important-soon

goern commented 3 years ago

hey fellas, what is the state of this? demoable?

goern commented 3 years ago

ping?!

pacospace commented 3 years ago

/assign @xtuchyna

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

harshad16 commented 2 years ago

/remove-lifecycle rotten

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

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

sesheta commented 2 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

sesheta commented 2 years ago

@sesheta: Closing this issue.

In response to [this](https://github.com/thoth-station/kebechet/issues/546#issuecomment-1043506976): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close 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.
sesheta commented 2 years ago

@pacospace: This issue is currently awaiting triage. One of the @thoth-station/devsops will take care of the issue, and 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.
goern commented 2 years ago

@xtuchyna @Gkrumbach07 could you have a look at this, and give it a little love. plan it and relate it to one of our key results? thx!