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

Re-enable Storage Metrics #5762

Closed
decko opened this issue Sep 2, 2024 · 1 comment · Fixed by #5891
Closed

Re-enable Storage Metrics #5762

decko opened this issue Sep 2, 2024 · 1 comment · Fixed by #5891
Labels
Feature

Comments

@decko
Copy link
Member

decko commented Sep 2, 2024

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context about the feature request here.
@decko decko mentioned this issue Sep 2, 2024
Closed
@bmbouter
Copy link
Member

bmbouter commented Oct 1, 2024 •
edited
Loading

At the pulpcore meeting today we identified a design we want to try:

  1. Use a TaskSchedule (as is, no arguments)
  2. Have that task run every 5 minutes
  3. Have that 1 task report on all domains
  4. Review the report in a few months if the assumptions are correct

@decko decko mentioned this issue Oct 9, 2024
Merged
decko added a commit to decko/pulpcore that referenced this issue Oct 10, 2024
@decko
Re-enable Storage Metrics emmiter and refactor it.
d38d95e 
This refactors the code used to retrieve the space utilized by
domain's artifacts and emit a `pulp_space_usage` metric value
using OpenTelemetry SDK.

Closes pulp#5762
decko added a commit to decko/pulpcore that referenced this issue Oct 10, 2024
@decko
Re-enable Storage Metrics emmiter and refactor it.
1473c22 
This refactors the code used to retrieve the space utilized by
domain's artifacts and emit a `pulp_space_usage` metric value
using OpenTelemetry SDK.

Closes pulp#5762
decko added a commit to decko/pulpcore that referenced this issue Oct 10, 2024
@decko
Re-enable Storage Metrics emmiter and refactor it.
0e53bb7 
This refactors the code used to retrieve the space utilized by
domain's artifacts and emit a `pulp_space_usage` metric value
using OpenTelemetry SDK.

Closes pulp#5762
decko added a commit to decko/pulpcore that referenced this issue Oct 10, 2024
@decko
Re-enable Storage Metrics emitter and refactor it.
f587b98 
This refactors the code used to retrieve the space utilized by
domain's artifacts and emit a `pulp_space_usage` metric value
using OpenTelemetry SDK.

Closes pulp#5762
decko added a commit to decko/pulpcore that referenced this issue Oct 11, 2024
@decko
Re-enable Storage Metrics emitter and refactor it.
6d10585 
This refactors the code used to retrieve the space utilized by
domain's artifacts and emit a `pulp_space_usage` metric value
using OpenTelemetry SDK.

Closes pulp#5762
decko added a commit to decko/pulpcore that referenced this issue Oct 11, 2024
@decko
Re-enable Storage Metrics emitter and refactor it
77dc479 
This refactors the code used to retrieve the space utilized by
domain's artifacts and emit a `pulp_space_usage` metric value
using OpenTelemetry SDK.

Closes pulp#5762
decko added a commit to decko/pulpcore that referenced this issue Oct 11, 2024
@decko
Re-enable Storage Metrics emitter and refactor it
0eacf6d 
This refactors the code used to retrieve the space utilized by
domain's artifacts and emit a `pulp_space_usage` metric value
using OpenTelemetry SDK.

Closes pulp#5762
decko added a commit that referenced this issue Oct 14, 2024
@decko
Re-enable Storage Metrics emitter and refactor it
356d5b5 
This refactors the code used to retrieve the space utilized by
domain's artifacts and emit a `pulp_space_usage` metric value
using OpenTelemetry SDK.

Closes #5762
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature
Projects
None yet
Milestone
No milestone
3 participants
@decko @bmbouter @dkliban