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

Fix Packit metrics "Copr builds (queued, started, finished)" chart #2430

Open
majamassarini opened this issue May 16, 2024 · 0 comments
Open
Labels
area/other Related to some other area/category than the specified ones. complexity/single-task Regular task, should be done within days. gain/low This doesn't bring that much value to users. impact/low This issue impacts only a few users. kind/bug Something isn't working. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.

Comments

@majamassarini
Copy link
Member

majamassarini commented May 16, 2024

The Copr builds (queued, started, finished) in http://metrics.osci.redhat.com/d/iuAkAaWMk/packit?orgId=1 is not working as expected.

Fix it.

This card is an outcome from the share debugging Packit tips and tricks. Do we need something else, apart from fixing the chart, for making this charts useful when debugging Packit?
If yes, please create a follow up card.

See also #2519 for follow-ups.

@majamassarini majamassarini added kind/bug Something isn't working. complexity/single-task Regular task, should be done within days. impact/low This issue impacts only a few users. area/other Related to some other area/category than the specified ones. gain/low This doesn't bring that much value to users. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related. labels May 16, 2024
@majamassarini majamassarini changed the title Fix Packit metrics *Copr builds (queued, started, finished)* chart. Fix Packit metrics "Copr builds (queued, started, finished)" chart May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/other Related to some other area/category than the specified ones. complexity/single-task Regular task, should be done within days. gain/low This doesn't bring that much value to users. impact/low This issue impacts only a few users. kind/bug Something isn't working. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.
Projects
Status: priority-backlog
Development

No branches or pull requests

1 participant