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?
- Revealing Security Threats with ExtraHop Reveal(x) - February 13, 2018
- The Logic Of Tables with Broadcom SDKLT - February 8, 2018
- Getting Ready for GDPR - January 18, 2018
- Going Faster with 400Gbps Ethernet and Andy Bechtolsheim - January 12, 2018
- Architecting Container Direction with Nirmata - January 5, 2018
- Continuing the SD-WAN Discussion At FutureWAN - January 4, 2018
- Keeping An Eye On Containers with Ixia CloudLens - January 4, 2018
- Balancing The Cost Of Your Application Delivery Controllers with KEMP Metered Licensing - December 27, 2017
- Arista vs. Cisco – The Tale Up To Now - December 14, 2017
- Unmasking Bad Actors with Gigamon - December 7, 2017