QoS is difficult to implement over the Internet, because hey, you don’t own all the gear between you and the destination.

And even if you do own all the bits, QoS is hard to monitor. How do you know you’ve gotten it right? If it’s not working the way you want, how can you tell?

When you’ve got all of that sorted, what do you do about it?

These, among other things, are QoS “gotchas” you’ve maybe run into. To help us form a network design strategy to cope with these gotchas is Peter Welcher, a network architect at NetCraftsmen, a consultancy in the Washington DC area that supports folks around the world.

We’re going to hit some QoS limitations to lead off the show, and then spend the rest of our time focused on how to monitor QoS in an actionable way.

Sponsor: ExtraHop

Today’s show is sponsored in part by ExtraHop, the enterprise cyber analytics company delivering performance and security from the inside out. ExtraHop offers complete visibility with machine learning to help you make quick, confident decisions about your IT environment. Explore the ExtraHop Performance Platform at extrahop.com/packetpushers.

Show Links:

Some QoS Gotchas – NetCraftsmen

NetCraftsmen

Peter Welcher’s blogs at NetCraftsmen

Peter Welcher on Twitter

Quality of Service (QoS) Fundamentals In 27 Lessons – Packet Pushers Ignition