Epic Fail: Using a Monitoring Tool for Diagnostics
Earlier in the week I posted a blog about Monitoring vs. Diagnostics; where I noted the skills, tools, and ultimately the visibility required to proactively monitor an environment versus re-actively diagnose, are very different. I’m sure those of you who have lived this challenge would agree. For those who have not lived to tell the tale, I’ll share this example from the field.
Please note I am not attempting to call out or embarrass anyone. The nuance and balance between monitoring and diagnostics is lost on all but the most seasoned end user computing professionals. It’s quite common that desktop workload-focused IT teams are ill prepared to solve a diagnostics problem with a monitoring solution. In this case, our example organization was experiencing crippling performance of its most important tier one application: the electronic health record (EHR) solution from Epic Systems.
Not Sized for Growth or Spikes
Our story begins at a large health care organization that…
Read the entire article here, Epic Fail: Using a Monitoring Tool for Diagnostics
via the fine folks at Liquidware Labs