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

agent does not report inodes usage #1793

Open
nioncode opened this issue Sep 12, 2024 · 3 comments
Open

agent does not report inodes usage #1793

nioncode opened this issue Sep 12, 2024 · 3 comments

Comments

@nioncode
Copy link

Describe the bug

ops-agent seems to not collect the system.filesystem.inodes.usage metric.

To Reproduce
Steps to reproduce the behavior:

  1. Run a GCE VM with Ops Agent --version=2.48.0 and default config.
  2. Wait for metrics to show up in Cloud Monitoring.
  3. See that there are metrics for disk usage, but NOT inodes usage

Expected behavior
Inodes usage should be collected and available in Cloud Monitoring.

Environment (please complete the following information):

  • VM distro / OS: Ubuntu 24.04
  • Ops Agent version: 2.48.0
  • Ops Agent configuration: default

Additional context
It seems like the metric is explicitly filtered out in the ops-agent (see

"system.filesystem.inodes.usage",
). Is there any reason for this? Can this be overridden with a custom config?

Copy link

This issue was marked stale due to lack of activity. It will be closed in 14 days.

@github-actions github-actions bot added the Stale label Nov 15, 2024
@nioncode
Copy link
Author

Still relevant to us.

@jefferbrecht
Copy link
Member

Hi @nioncode,

That the metric is missing is intentional. The short answer is that there's no platform-side agent.googleapis.com/... metric schema defined yet for an inode metric (although there are comparable ones for e.g. GKE platform metrics); the longer answer is that we can accept this as a feature request and work to resolve that blocker so that we can get it added to the Ops Agent. We'll add an internal tracker for this and see whether we can get it prioritized.

Apologies for the lack of response so far.

@jefferbrecht jefferbrecht removed the Stale label Dec 5, 2024
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

No branches or pull requests

2 participants