TrafficLogPayload
Schema for a forwarded PAN-OS traffic log entry. Traffic logs capture session metadata for every network connection processed by the firewall, providing comprehensive network visibility for security operations, compliance, and analytics.
Properties
| Name | Type | Description |
|---|---|---|
| receive_time | string | Timestamp when the log entry was received by Strata Logging Service from the generating firewall device. |
| serial | string | Serial number of the Palo Alto Networks firewall or Prisma Access node that generated this log entry. |
| type | string | Log type identifier, always TRAFFIC for traffic log entries. |
| subtype | string | Traffic log subtype indicating what session lifecycle event triggered this log entry. |
| src | string | Source IP address of the network session. |
| dst | string | Destination IP address of the network session. |
| sport | integer | Source port number of the network session. |
| dport | integer | Destination port number of the network session. |
| proto | string | IP protocol name or number for the session (e.g., tcp, udp, icmp). |
| app | string | Application identified by PAN-OS App-ID, such as ssl, web-browsing, dns, or a specific SaaS application name. |
| action | string | Enforcement action applied to the session by the matching security policy rule. |
| bytes_sent | integer | Total bytes sent from client to server in this session. |
| bytes_received | integer | Total bytes received by client from server in this session. |
| session_id | string | Unique session identifier assigned by the firewall for this network session. |
| rule_name | string | Name of the security policy rule that matched and processed this session. |
| src_zone | string | Source security zone from which the session originated. |
| dst_zone | string | Destination security zone to which the session is destined. |
| src_user | string | Source user identity associated with the session if User-ID is enabled on the ingress zone. |
| dst_user | string | Destination user identity if available. |
| nat_src | string | Post-NAT source IP address after address translation. |
| nat_dst | string | Post-NAT destination IP address after address translation. |
| nat_sport | integer | Post-NAT source port after port address translation. |
| nat_dport | integer | Post-NAT destination port after port address translation. |
| packets_sent | integer | Total packets sent from client in this session. |
| packets_received | integer | Total packets received by client in this session. |
| session_duration | integer | Total session duration in seconds. |
| device_name | string | Hostname of the firewall that generated this log entry. |
| vsys | string | Virtual system name or identifier on the firewall. |
| log_forwarding_profile | string | Name of the Strata Logging Service log forwarding profile that forwarded this log entry. |
| output_format | string | Output format in which this log entry was forwarded to the destination. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"title": "TrafficLogPayload",
"description": "Schema for a forwarded PAN-OS traffic log entry. Traffic logs capture session metadata for every network connection processed by the firewall, providing comprehensive network visibility for security operations, compliance, and analytics.\n",
"$id": "https://raw.githubusercontent.com/api-evangelist/palo-alto-networks/refs/heads/main/json-schema/strata-logging-forwarding-traffic-log-payload-schema.json",
"type": "object",
"properties": {
"receive_time": {
"type": "string",
"format": "date-time",
"description": "Timestamp when the log entry was received by Strata Logging Service from the generating firewall device.\n"
},
"serial": {
"type": "string",
"description": "Serial number of the Palo Alto Networks firewall or Prisma Access node that generated this log entry.\n"
},
"type": {
"type": "string",
"enum": [
"TRAFFIC"
],
"description": "Log type identifier, always TRAFFIC for traffic log entries.\n"
},
"subtype": {
"type": "string",
"enum": [
"start",
"end",
"drop",
"deny"
],
"description": "Traffic log subtype indicating what session lifecycle event triggered this log entry.\n"
},
"src": {
"type": "string",
"description": "Source IP address of the network session."
},
"dst": {
"type": "string",
"description": "Destination IP address of the network session."
},
"sport": {
"type": "integer",
"description": "Source port number of the network session."
},
"dport": {
"type": "integer",
"description": "Destination port number of the network session."
},
"proto": {
"type": "string",
"description": "IP protocol name or number for the session (e.g., tcp, udp, icmp).\n"
},
"app": {
"type": "string",
"description": "Application identified by PAN-OS App-ID, such as ssl, web-browsing, dns, or a specific SaaS application name.\n"
},
"action": {
"type": "string",
"enum": [
"allow",
"deny",
"drop",
"reset-client",
"reset-server",
"reset-both"
],
"description": "Enforcement action applied to the session by the matching security policy rule.\n"
},
"bytes_sent": {
"type": "integer",
"description": "Total bytes sent from client to server in this session."
},
"bytes_received": {
"type": "integer",
"description": "Total bytes received by client from server in this session."
},
"session_id": {
"type": "string",
"description": "Unique session identifier assigned by the firewall for this network session.\n"
},
"rule_name": {
"type": "string",
"description": "Name of the security policy rule that matched and processed this session.\n"
},
"src_zone": {
"type": "string",
"description": "Source security zone from which the session originated."
},
"dst_zone": {
"type": "string",
"description": "Destination security zone to which the session is destined.\n"
},
"src_user": {
"type": "string",
"description": "Source user identity associated with the session if User-ID is enabled on the ingress zone.\n"
},
"dst_user": {
"type": "string",
"description": "Destination user identity if available."
},
"nat_src": {
"type": "string",
"description": "Post-NAT source IP address after address translation."
},
"nat_dst": {
"type": "string",
"description": "Post-NAT destination IP address after address translation."
},
"nat_sport": {
"type": "integer",
"description": "Post-NAT source port after port address translation."
},
"nat_dport": {
"type": "integer",
"description": "Post-NAT destination port after port address translation."
},
"packets_sent": {
"type": "integer",
"description": "Total packets sent from client in this session."
},
"packets_received": {
"type": "integer",
"description": "Total packets received by client in this session."
},
"session_duration": {
"type": "integer",
"description": "Total session duration in seconds."
},
"device_name": {
"type": "string",
"description": "Hostname of the firewall that generated this log entry."
},
"vsys": {
"type": "string",
"description": "Virtual system name or identifier on the firewall."
},
"log_forwarding_profile": {
"type": "string",
"description": "Name of the Strata Logging Service log forwarding profile that forwarded this log entry.\n"
},
"output_format": {
"type": "string",
"enum": [
"CSV",
"LEEF",
"CEF",
"JSON",
"PARQUET"
],
"description": "Output format in which this log entry was forwarded to the destination.\n"
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/json-schemas/strata-logging-forwarding-traffic-log-payload"
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.