Skip to content

Move memory breakdown metrics to new endpoint #11788

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

Merged
merged 1 commit into from
Jul 23, 2024

Conversation

mkuratczyk
Copy link
Contributor

Move metrics introduced in #11746 to a dedicated endpoint (/metrics/memory-breakdown).

Collecting them on a large system (tens of thousands of processes or more) can be time consuming as we iterate over all processes. By putting them on a separate endpoint, we make that opt-in

Related docs:
rabbitmq/rabbitmq-website#1985

I'm still playing around with the best visualization for these metrics, but what I have so far proves that things work:
Screenshot 2024-07-23 at 11 53 41

Collecting them on a large system (tens of thousands of processes
or more) can be time consuming as we iterate over all processes.
By putting them on a separate endpoint, we make that opt-in
@michaelklishin
Copy link
Collaborator

#11743.

@michaelklishin michaelklishin merged commit f4b80f4 into main Jul 23, 2024
189 checks passed
@michaelklishin michaelklishin deleted the memory-breakdown-endpoint branch July 23, 2024 10:46
michaelklishin added a commit that referenced this pull request Jul 24, 2024
Move memory breakdown metrics to new endpoint (backport #11788)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants