Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
pacospace opened this issue Sep 18, 2020 · 25 comments
Open

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

pacospace opened this issue Sep 18, 2020 · 25 comments
Assignees
@xtuchyna
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/observability Categorizes an issue or PR as relevant to SIG Observability

Comments

@pacospace
Copy link
Contributor

pacospace commented Sep 18, 2020 •
edited
Loading

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
Copy link
Member

goern commented Sep 18, 2020

/kind feature

@sesheta sesheta added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 18, 2020
@goern
Copy link
Member

goern commented Sep 18, 2020

/milestone investigator-v0.5.0

@sesheta sesheta added this to the investigator-v0.5.0 milestone Sep 18, 2020
@xtuchyna xtuchyna mentioned this issue Sep 24, 2020
Closed
@goern
Copy link
Member

goern commented Nov 23, 2020

@xtuchyna @pacospace what is the status of this?

@xtuchyna
Copy link
Member

@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
Copy link
Contributor Author

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

@pacospace pacospace mentioned this issue Jan 15, 2021
Closed
@pacospace pacospace mentioned this issue Jan 26, 2021
Closed
@pacospace
Copy link
Contributor Author

pacospace commented Jan 26, 2021 •
edited
Loading

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

@xtuchyna
Copy link
Member

xtuchyna commented Jan 26, 2021 •
edited by pacospace
Loading

Requirements as for know:

  • Check mi-scheduler new version released ( New patch release 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

@goern
Copy link
Member

goern commented Feb 2, 2021

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?"

This was referenced Feb 18, 2021
Closed
Closed
@pacospace
Copy link
Contributor Author

Requirements as for know:

  • 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:

  • Check mi-scheduler new version released ( New patch release 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)

Steps:

@xtuchyna xtuchyna mentioned this issue Feb 18, 2021
Merged
2 tasks
@sesheta
Copy link
Member

sesheta commented May 19, 2021

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 sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 19, 2021
@goern
Copy link
Member

goern commented May 31, 2021

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

/remove-lifecycle stale

@sesheta sesheta removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 31, 2021
@xtuchyna
Copy link
Member

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

This was referenced May 31, 2021
Merged
Merged
@goern
Copy link
Member

goern commented May 31, 2021

/kind demo

@sesheta sesheta added the kind/demo This is an Issue or PR someone want to give a demo or request a demo. label May 31, 2021
@goern
Copy link
Member

goern commented Jun 10, 2021

/priority important-soon

@pacospace
Copy link
Contributor Author

/assign @xtuchyna

@goern goern removed this from the investigator-v0.5.0 milestone Jul 20, 2021
@sesheta
Copy link
Member

sesheta commented Aug 24, 2021

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 sesheta added the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Aug 24, 2021
@harshad16
Copy link
Member

/remove-lifecycle rotten

@sesheta sesheta removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Sep 15, 2021
@pacospace pacospace mentioned this issue Sep 15, 2021
Open
24 tasks
@goern goern mentioned this issue Sep 16, 2021
Closed
@sesheta
Copy link
Member

sesheta commented Dec 14, 2021

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 sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 14, 2021
@sesheta
Copy link
Member

sesheta commented Jan 13, 2022

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 sesheta added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 13, 2022
@goern goern removed the kind/demo This is an Issue or PR someone want to give a demo or request a demo. label Jan 18, 2022
@sesheta
Copy link
Member

sesheta commented Feb 17, 2022

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

/close

@sesheta
Copy link
Member

sesheta commented Feb 17, 2022

@sesheta: Closing this issue.

In response to this:

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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@sesheta sesheta closed this as completed Feb 17, 2022
@pacospace pacospace reopened this Feb 21, 2022
@sesheta sesheta added the needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. label Feb 21, 2022
@sesheta
Copy link
Member

sesheta commented Feb 21, 2022

@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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@pacospace pacospace added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. labels Feb 21, 2022
@pacospace pacospace removed their assignment Feb 21, 2022
@goern
Copy link
Member

goern commented Jul 19, 2022

@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!

@harshad16 harshad16 moved this to 🆕 New in Planning Board Oct 7, 2022
@codificat codificat added the sig/observability Categorizes an issue or PR as relevant to SIG Observability label Jan 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xtuchyna xtuchyna

Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/observability Categorizes an issue or PR as relevant to SIG Observability
Projects
Planning Board
Status: 🆕 New
Milestone
No milestone
Development

No branches or pull requests
6 participants
@goern @codificat @harshad16 @pacospace @sesheta @xtuchyna