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

[Epic] Metrics for the devsecops tools #2563

Open
1 of 6 tasks
harshad16 opened this issue May 17, 2022 · 4 comments
Open
1 of 6 tasks

[Epic] Metrics for the devsecops tools #2563

harshad16 opened this issue May 17, 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/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@harshad16
Copy link
Member

harshad16 commented May 17, 2022

As DevSecOps operators, we would like to have metrics for the DevSecOps tools, so we could create a Grafana dashboard for monitoring.
We would like to have metrics out the component that is used by the Thoth DevSecOps, like pipeline, argocd, and cluster metrics itself. we would like to create the dashboard for the various operations carried out via these tools.

Acceptance Criteria

@sesheta sesheta added the needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. label May 17, 2022
@harshad16
Copy link
Member Author

/triage accepted

@sesheta sesheta added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. labels May 17, 2022
@harshad16
Copy link
Member Author

/sig devsecops
/kind feature
/priority important-soon

@sesheta sesheta added sig/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps. kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Jun 6, 2022
@sesheta
Copy link
Member

sesheta commented Sep 4, 2022

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 Sep 4, 2022
@harshad16 harshad16 added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Sep 6, 2022
@harshad16
Copy link
Member Author

/remove-lifecycle stale
/lifecycle frozen

@sesheta sesheta added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 6, 2022
@harshad16 harshad16 moved this to Epics in SIG-Observability Sep 22, 2022
@codificat codificat moved this to 🔖 Next in Planning Board Sep 26, 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/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Status: 🔖 Next
Status: 🗺 Epics
Development

No branches or pull requests

2 participants