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

[3pt] Describe components exposing metrics / pushing metrics in monitoring folder in thoth application. #2373

Open
pacospace opened this issue Feb 22, 2022 · 5 comments
Assignees
Labels
area/documentation Issues or PRs related to documentation, tutorials, examples, ... documentation Improvements or additions to documentation kind/documentation Categorizes issue or PR as related to documentation. 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. 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

@pacospace
Copy link
Contributor

Is your feature request related to a problem? Please describe.

Describe the solution you'd like
Describe components exposing metrics / pushing metrics in monitoring folder in thoth application.

Describe alternatives you've considered

Additional context

@pacospace pacospace added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 22, 2022
@sesheta sesheta added the needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. label Feb 22, 2022
@pacospace
Copy link
Contributor 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 Feb 22, 2022
@pacospace pacospace added the sig/observability Categorizes an issue or PR as relevant to SIG Observability label Feb 22, 2022
@goern
Copy link
Member

goern commented Feb 28, 2022

is this something we would describe as YAML and convert it to configs, or is this meant for humans?

@harshad16 harshad16 added documentation Improvements or additions to documentation area/documentation Issues or PRs related to documentation, tutorials, examples, ... kind/documentation Categorizes issue or PR as related to documentation. labels Apr 21, 2022
@harshad16 harshad16 changed the title Describe components exposing metrics / pushing metrics in monitoring folder in thoth application. [3pt] Describe components exposing metrics / pushing metrics in monitoring folder in thoth application. May 2, 2022
@harshad16 harshad16 self-assigned this May 16, 2022
@sesheta
Copy link
Member

sesheta commented Aug 15, 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 Aug 15, 2022
@codificat codificat moved this to 🆕 New in Planning Board Sep 6, 2022
@codificat codificat moved this from 🆕 New to 🔖 Ready in Planning Board Sep 6, 2022
@sesheta
Copy link
Member

sesheta commented Sep 14, 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 Sep 14, 2022
@harshad16
Copy link
Member

/remove-lifecycle rotten
/lifecycle frozen

@sesheta sesheta 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. labels Sep 15, 2022
@harshad16 harshad16 moved this to Next in SIG-Observability Sep 22, 2022
@goern goern moved this from 🔖 Next to 📋 Backlog in Planning Board Feb 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/documentation Issues or PRs related to documentation, tutorials, examples, ... documentation Improvements or additions to documentation kind/documentation Categorizes issue or PR as related to documentation. 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. 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: 📋 Backlog
Status: 🔖 Ready
Development

No branches or pull requests

4 participants