Ethan Banks of Ethan Banks on Technology comments:
Shiny red lights and sundry messages can tell us when a transaction time is too high, an interface is dropping too many packets, database commits are taking too long, or a WAN link’s jitter just went south. That information is wonderful, but doesn’t resolve the issue. A course of action is required.
An interesting problem. Should a system just tell you things are broken? Or tell you that it fixed the broken things?
Read more at: Should Monitoring Systems Also Perform Mitigation?
- Unmasking Bad Actors with Gigamon - December 7, 2017
- Dedicated Wireless Troubleshooting Doesn’t Have To Break The Bank - November 28, 2017
- Are Vendors and VARs The Enemy? - November 15, 2017
- Pluribus Networks Is the Definition of “Software Defined” - November 2, 2017
- First American Title And Viptela: A Story of Resilience - October 4, 2017
- Flexible NFV with Array Networks - August 7, 2017
- Cloud onRamp – Making The Cloud More Local For Your Users - July 26, 2017
- Feeling Your Flow with Plixer - July 19, 2017
- What Are ASICs? A Human Example - July 11, 2017
- Migrating to Healthcare Cloud Apps With Acadia and Viptela - June 5, 2017