Cloud Computing

Asserting Azure Firewall enhancements for troubleshooting community efficiency and visitors visibility | Azure Weblog and Updates

Spread the love

IT safety directors are sometimes known as on to troubleshoot community points. As an example, a essential utility might exhibit latency or disconnections, irritating finish customers. These points could also be brought on by a latest routing replace or modifications in safety. In some circumstances, the trigger could also be as a consequence of a sudden burst in community visitors—overwhelming the community sources.

Microsoft Azure Firewall now presents new logging and metric enhancements designed to extend visibility and supply extra insights into visitors processed by the firewall. IT safety directors might use a mixture of the next to root trigger utility efficiency points:

o    Latency Probe metric is now in preview.

o    Stream Hint Log is now in preview.

o    Fats Flows Log is now in preview.

Azure Firewall is a cloud-native firewall as a service providing that permits clients to centrally govern and log all their visitors flows utilizing a DevOps strategy. The service helps each utility and network-level filtering guidelines and is built-in with the Microsoft Defender Risk Intelligence feed to filter recognized malicious IP addresses and domains. Azure Firewall is extremely accessible with built-in auto-scaling.

Latency Probe metric—now in preview

In a community infrastructure, one might observe will increase in latency relying on numerous components. The power to observe the latency of the firewall is crucial for proactively participating in any potential points with visitors or companies within the infrastructure.

The Latency Probe metric is designed to measure the general latency of Azure Firewall and supply perception into the well being of the service. IT directors can use the metric for monitoring and alerting if there’s observable latency and diagnosing if the Azure Firewall is the reason for latency in a community.

Within the case that Azure Firewall is experiencing latency, this may be as a consequence of numerous causes, akin to excessive CPU utilization, visitors throughput, or networking points. As an vital observe, this device is powered by Pingmesh expertise, which signifies that the metric measures the typical latency of the firewall itself. The metric doesn’t measure end-to-end latency or the latency of particular person packets.


Dashboard view of healthy firewall latency measured by the Latency Probe (Preview) metric
Determine 1: Dashboard view of wholesome firewall latency measured by the Latency Probe (Preview) metric.


Stream Hint logs—now in preview

Azure Firewall logging gives logs for numerous visitors—akin to community, utility, and risk intelligence visitors. At the moment, these logs present visitors via the firewall within the first try at a Transmission Management Protocol (TCP) connection, often known as the SYN packet. Nevertheless, this fails to point out the total journey of the packet within the TCP handshake. The power to observe and monitor each packet via the firewall is paramount for figuring out packet drops or uneven routes.

To dive additional into an uneven routing instance, Azure Firewall—as a stateful firewall—maintains state connections and routinely and dynamically permits visitors to efficiently come again to the firewall. Nevertheless, uneven routing can happen when a packet takes one path to the vacation spot via the firewall and takes a special path when making an attempt to return to the supply. This may be as a consequence of consumer misconfiguration, akin to including an pointless route within the path of the firewall.

In consequence, one can confirm if a packet has efficiently flowed via the firewall or if there’s uneven routing by viewing the extra TCP handshake logs in Stream Hint.

To take action, you’ll be able to monitor community logs to view the primary SYN packet and click on “allow Stream Hint” to see the extra flags for verification:

o    SYN-ACK

o    FIN

o    FIN-ACK

o    RST


By including these further flags in Stream Hint logs, IT directors can now see the return packet, if there was a failed connection, or an unrecognized packet. To allow these logs, please learn the documentation linked under.

Flow Trace logs displaying SYN-ACK and FIN packets

Determine 2: Stream Hint logs displaying SYN-ACK and FIN packets.


Prime Flows—now in preview

At the moment, Microsoft Azure Firewall Commonplace can help as much as 30 Gbps and Azure Firewall Premium can help as much as 100 Gbps of visitors processing. Nevertheless, in any case, typically visitors flows can both be unintentionally or deliberately “heavy” relying on the dimensions, period, and different components of the packets. Since these flows can doubtlessly impression different flows and the processing of the firewall, it’s vital to observe these visitors flows, to make sure that the firewall can carry out optimally.

The Prime Flows log—or industry-known as Fats Flows—log reveals the highest connections which can be contributing to the very best bandwidth in a given time-frame via the firewall.

This visibility gives the next advantages for IT directors:

o    Figuring out the highest visitors flows traversing via the firewall.

o    Figuring out any sudden or anomaly visitors.

o    Deciding what visitors ought to be allowed or denied, based mostly on outcomes and objectives.

To allow these logs, please learn the documentation linked under.

Dashboard view of Top Flow logs displaying traffic with the top flow rates.
Determine 3: Prime Stream logs displaying visitors with the highest stream charges.

Subsequent steps

For extra info on Azure Firewall and all the pieces we lined on this weblog publish, see the next sources:

· Azure Firewall documentation.

· Azure Firewall Supervisor documentation.

· Deploy and configure Azure Firewall logs and metrics.

· Allow Stream Hint and Prime Flows Logs Tutorial.

Leave a Reply

Your email address will not be published. Required fields are marked *