You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/cloudflare-one/insights/logs/logpush.mdx
+18-51Lines changed: 18 additions & 51 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,63 +48,30 @@ Refer to the Logpush documentation for a list of available fields.
48
48
|[Device Posture](/logs/reference/log-fields/account/device_posture_results/)| Device posture status from the WARP client |
49
49
|[Session Logs](/logs/reference/log-fields/account/zero_trust_network_sessions/)| Network session logs for traffic proxied by Cloudflare Gateway |
50
50
51
-
## Parse Logpush logs
51
+
## Parse DNS logs
52
52
53
-
Cloudflare Gateway logs DNS query information in [resource record format](https://datatracker.ietf.org/doc/html/rfc1035#section-4.1.3), a Base64-encoded binary format. The following resource record fields are available for each query:
53
+
Logpush logs the following fields for each DNS query:
54
54
55
55
- Query name
56
56
- Query type
57
57
- Query class
58
58
- Response TTL
59
59
- Response data
60
60
61
-
To parse resource record logs from Logpush, run the following Python script with your desired samples:
DNS query resource records are available in [Base64-encoded binary format](https://datatracker.ietf.org/doc/html/rfc1035#section-4.1.3) and JSON. For example:
0 commit comments