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.

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

Verify the metrics for the solvers sync and details #2535

Open
2 tasks
harshad16 opened this issue Apr 29, 2022 · 4 comments
Open
2 tasks

Verify the metrics for the solvers sync and details #2535

harshad16 opened this issue Apr 29, 2022 · 4 comments
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 triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@harshad16
Copy link
Member

harshad16 commented Apr 29, 2022

The solver metrics contain details of the number of days it takes to sync results for the new solver. we should verify if the metrics have more information as follows:

  • How many packages are synced?
  • can the metrics show up as new solvers ?

Acceptance Criteria

@harshad16 harshad16 added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 29, 2022
@sesheta sesheta added the needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. label Apr 29, 2022
@harshad16
Copy link
Member Author

/triage accepted
/priority important-soon
/sig observability
/lifecycle frozen

@sesheta sesheta added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/accepted Indicates an issue or PR is ready to be actively worked on. 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 and removed needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. labels Jun 6, 2022
@harshad16 harshad16 moved this to Next in SIG-Observability Sep 22, 2022
@codificat codificat moved this to 🔖 Next in Planning Board Sep 26, 2022
@VannTen
Copy link
Member

VannTen commented Oct 17, 2022

Can we make this a more actionnable ? Especially:

  • what tool are we talking about ?
  • what it the purpose ? (if it's verifying some metric maybe it's a documentation thing which should be updated ?)

@VannTen
Copy link
Member

VannTen commented Oct 17, 2022

/triage needs-information

@sesheta sesheta added the triage/needs-information Indicates an issue needs more information in order to work on it. label Oct 17, 2022
@harshad16
Copy link
Member Author

/triage accepted

@harshad16 harshad16 removed the triage/needs-information Indicates an issue needs more information in order to work on it. label Oct 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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 triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Status: 🔖 Next
Status: 🔖 Ready
Development

No branches or pull requests

3 participants