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

Collecting ideas for stats server #14

Open
henningpeters opened this issue Apr 22, 2013 · 0 comments
Open

Collecting ideas for stats server #14

henningpeters opened this issue Apr 22, 2013 · 0 comments

Comments

@henningpeters
Copy link
Contributor

I would like to implement those features that are covered by real-work use cases and not otherwise covered. I.e., I would explicitly exclude all statistics that S3 collects anyway via its logging feature.

My use case are:

  • check what and whether it is running (stable)?
  • is it fast (enough)?
  • how can I tune the configuration?
  • can I find bugs?

Here is an overview about all things that came to my mind that could get logged (not everything has a clear use case, though).

  1. operational information
  • connected endpoint
  • configuration options
  • versioning
  • security settings
  • compile flags
  • version info
  • uptime
  1. statistics on each S3 request type
  • S3 ListBucket
  • S3 GetObject
    etc.

by number of requests, sent bytes, received bytes, number of internal errors/error codes, number of retries/failures

  1. aggregate statistics on S3 requests
  • total number of requests
  • total sent bytes
  • total received bytes
  • average latency (incl. cache)
  1. cache statistics
  • size (bytes)
  • number of entries
  • number of hits
  • number of misses
  • hit/miss ratio
  1. FUSE statistics
  • number of requests by type (mkdir, forget, listxattr, etc.)
  1. real-time information
  • info on last X FUSE requests
  • info on last X S3 requests
  • info on X most frequently accessed cache items
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant