Hi, this is 2011 replying
>Complex UIs around simple tools often make one less productive not more.
I said "Slick" UI, not "Complicated" UI. You can see all the following within about 4 clicks on the interface
* Database status (IOPS, RAM, locks etc.)
* CPU / RAM on your app / web-servers
* Request throughput and request processing time for your web application broken down by host if need be.
* Memcache status.
* Details information regarding which methods were called for each request and how long each method executed by that request lasted.
* Response time from the user's perspective.
* Background task processing.
All in near real-time.
Of course, because the information is archived you can see all this in a historical context in a nicely presented manner. You said GUIs "Often" reduce productivity and I agree, but in this case you are wrong in my opninon.
How many log files / separate apps do you need to access to get that clear a picture?
> You have a dev server, right?
Yes, a dev server I do not want to gunk up with some app + DB etc. for monitoring a part the live site.
>You test your apps before they go live, right? You should already have your own profiling data. Or do you out-source that too?
What has that got to do with anything I said? This is about monitoring / diagnosing live sites.
I have to wonder if you have you actually used it? It sounds like you have already written it off because when you heard it was web app with a *Gasp* GUI and "grep / awk / sed are good enough damnit, get off my lawn."
Logs are useful for diagnosing problems after the fact (Although NewRelic does make things easier too), not for real-time monitoring.
- Product Round-up Smartwatch face off: Pebble, MetaWatch and new hi-tech timepieces
- Geek's Guide to Britain The bunker at the end of the world - in Essex
- FLABBER-JASTED: It's 'jif', NOT '.gif', says man who should know
- If you've bought DRM'd film files from Acetrax, here's the bad news
- VIDEO Herschel Space Observatory spots galaxies merging