Navigation Menu

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

High-level dashboard #7

Open
nzoschke opened this issue Dec 12, 2012 · 1 comment
Open

High-level dashboard #7

nzoschke opened this issue Dec 12, 2012 · 1 comment

Comments

@nzoschke
Copy link
Owner

Ferret should be logging all measurements in a normalized format, meaning both the Librato and l2met data API offer generalized ways to get and interpret monitoring data.

Use one of these data sources to build a high-level dashboard configuration and view.

Service Status
git clone green
git push ruby yellow
HTTP curl green

Defining red/yellow/green for each service informs a lot about the monitoring.

HTTP curl uptime should be extremely high, ~99.X % which means that we need to monitor the HTTP services at a high frequency and a high concurrency.

Git uptime can be more relaxed, perhaps 98%

@nzoschke
Copy link
Owner Author

Someday sparklines!

Service 24h Trend Status
git clone ▁▂▅▂▁▁▂▂▂ green
git push ruby ▁▂▃▃▂▅▅▇▇ yellow
HTTP curl ▁▁▁▂▁▁▂▁▁▁ green

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

1 participant