---
title: Azure Application Gateway Bytes Processed | Blue Matador - Troubleshooting
description: Blue Matador detects when the number of bytes processed by your Azure Application Gateway is anomalous.
image: https://www.bluematador.com/hubfs/logo-1.png
---

 Docs

# Azure Application Gateway Bytes Processed

When Azure Application Gateways route traffic to your application, you can generally expect a steady stream of requests to your application. Blue Matador watches the **Throughput** metric for the number of bytes going in and out of your application gateway and creates events when this metric is anomalous. A change in the number of bytes processed can be caused by two things:

- Request rate has increased/decreased
- Request or response sizes have increased/decreased

Neither of these two situations are guaranteed problems. However, it can be useful to know when your application gateway spikes or drops in traffic, especially if it happens in a pattern you were previously unaware of. Knowing about anomalous traffic can also be useful for correlation with other infrastructure issues you’re experiencing.

If you determine that the difference in bytes processed is significant, [enable](https://docs.microsoft.com/en-us/azure/application-gateway/application-gateway-diagnostics#enable-logging-through-the-azure-portal) and check access logs for your application gateway. This can help you find which endpoints are being called with a different frequency or that have unexpected response sizes.

## Resources

---

- [Supported metrics for Application Gateway](https://docs.microsoft.com/en-us/azure/azure-monitor/platform/metrics-supported#microsoftnetworkapplicationgateway) (Microsoft Azure Documentation)
- [Back-end health, diagnostic logs, and metrics for Application Gateway](https://docs.microsoft.com/en-us/azure/application-gateway/application-gateway-diagnostics) (Microsoft Azure Documentation)