How to access logs

tigera · Nov 19, 2024 · 6587755 · 6587755
1 parent 8fe7fe2
commit 6587755
Showing 1 changed file with 14 additions and 3 deletions.
diff --git a/calico/network-policy/policy-rules/log-rules.mdx b/calico/network-policy/policy-rules/log-rules.mdx
@@ -60,8 +60,10 @@ In the iptables dataplane, the Log action logs the traffic at the point of evalu
 
 <Tabs groupId='log-rules'>
 <TabItem label="eBPF" value="eBPF">
-eBPF logs are sent to the 
-
+eBPF policy logs are sent to the trace pipe and can be viewed by using the following command:
+```bash
+kubectl exec -n calico-system -it ds/calico-node -- bpftool prog tracelog
+```
 
 An eBPF log starts with the pid name and ID 
 
@@ -78,7 +80,13 @@ curl-5288    [000] ..s2.  3055.982021: bpf_trace_printk: cali527b0801ecb-E: poli
 
 </TabItem>
 <TabItem label="iptables/ipvs" value="iptables">
-iptables/ipvs logs are sent to the syslog, this requires your host installation to have the rsyslog package.
+Policy logs are sent to the syslog, this requires your host installation to have the rsyslog package.
+
+Use the following command to access your policy logs
+```bash
+journalctl | egrep calico-packet
+```
+
 Example of iptable logs:
 ```bash
 2024-11-19T12:15:03.023805-08:00 c1-control kernel: calico-packet: IN=cali527b0801ecb OUT=eth0 MAC=ee:ee:ee:ee:ee:ee:1e:0a:36:33:f5:09:08:00 SRC=172.16.193.134 DST=69.147.80.15 LEN=60 TOS=0x00 PREC=0x00 TTL=63 ID=58406 DF PROTO=TCP SPT=45588 DPT=80 WINDOW=64860 RES=0x00 SYN URGP=0
@@ -171,3 +179,6 @@ kubectl patch kubecontrollersconfiguration default --type=merge --patch='{"spec"
 
 For more on the match criteria and policy actions, see:
 
+- [Global network policy](../../reference/resources/globalnetworkpolicy.mdx)
+- [Network policy](../../reference/resources/networkpolicy.mdx)
+- [Host protection](../hosts/index.mdx)