Firewall Support Center

Palo Alto Traffic Logs: How to Read “Incomplete” and “Aged-Out”

A PAN-OS traffic log shows allow, the application field reads incomplete, and the session end reason is aged-out. Read each field separately. The action tells you the recorded policy decision. The application field describes classification. The end reason explains how the session ended from the firewall’s perspective.

Follow one connection. In Monitor → Logs → Traffic, filter for the test’s source, destination, port, and time. Compare ingress and egress interfaces and the bytes in both directions. If the client sends traffic and no reply is recorded, verify the destination listener, host firewall, and return route. If the firewall sees traffic in both directions, inspect the actual handshake and application behavior. An aged-out entry can also occur in ordinary UDP sessions.

Worked example. A client tests HTTPS. The log shows bytes sent, zero bytes received, and a later timeout. The destination confirms it received the connection attempt but its reply followed a different gateway. Engineers correct the approved route and repeat the test. The browser loads, traffic appears in both directions, and the new log matches the intended rule.

See Palo Alto Networks’ Traffic log field documentation and the vendor’s note on aged-out sessions.