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

Add metrics for number of inodes #781

Merged
merged 3 commits into from
Feb 25, 2024

Conversation

jamesbornholt
Copy link
Member

Description of change

We track the total number of inodes as well as tracking them by kind. I did this by updating how we use gauges to work better for our current metrics stack, so that we don't just emit the same value every 5 seconds forever.

Does this change impact existing behavior?

No.


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and I agree to the terms of the Developer Certificate of Origin (DCO).

This is a small change to their behavior: they'll now emit if they're
changed to zero, whereas before they would not. But I think that's the
behavior we want anyway.

Signed-off-by: James Bornholt <bornholt@amazon.com>
We were abusing absolute counters to get the "only emit when changed"
behavior, which gauges now provide too.

Signed-off-by: James Bornholt <bornholt@amazon.com>
We track the total number of inodes as well as tracking them by kind.

Signed-off-by: James Bornholt <bornholt@amazon.com>
Copy link
Contributor

@arsh arsh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jamesbornholt jamesbornholt added this pull request to the merge queue Feb 25, 2024
Merged via the queue into awslabs:main with commit 6d7c194 Feb 25, 2024
24 checks passed
@jamesbornholt jamesbornholt deleted the inode-metric branch February 25, 2024 22:52
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