-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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 show stats on server #1470
Comments
Let me take on stuff like this. |
A design we should consider is that the InfluxDB system has a special database e.g. "internal" into which stats about the Servers themselves are written. This would allow the system to provide historical information about itself. This is a common design in other systems. |
Yeah, at some point we may want to enable that. For now I just wanted an in On Mon, Feb 2, 2015 at 2:10 AM, otoolep notifications@github.com wrote:
|
I like the in-memory approach ! |
Now you can show stats by hitting a specific server. This is lower priority since there are other ways to do it so pushing it out past 0.9.0 |
This is done, the framework is there, just need to add more and more stats as we need them. The story for accessing across the cluster, from any node, is to query the |
@otoolep what's the retention policy of the |
Good idea -- I mean to add that monitor config, but it slipped out of my mind. I'll take care of it. |
Users should be able to show statistics for a given server through the query:
The stats should include queries per second, writes per second, values per second (different than writes if they're batching), last heartbeat time, free hd space on the data drive, number of hearbeat failures in the last 5 minutes, and replication delay (last time it received either a heartbeat or write)
I'm sure we'll think of other things to add over time.
The text was updated successfully, but these errors were encountered: