Yeah, we have that with our customers sometimes. To me, an app should either be running full whack - maxing out bandwidth on CPU, disk, memory or network - or completely idle. Chuntering along at 2% is a bug. For the ones that put ‘monitoring tools’ that raise errors when we reach 100% on something, we set a Linux CGroup to throttle the offending resource. Takes longer, obviously, but not worth arguing with their network deployment teams 🤷 .