diff --git a/calico-cloud/operations/ebpf/troubleshoot-ebpf.mdx b/calico-cloud/operations/ebpf/troubleshoot-ebpf.mdx index bc2edb715c..bc0b086bf4 100644 --- a/calico-cloud/operations/ebpf/troubleshoot-ebpf.mdx +++ b/calico-cloud/operations/ebpf/troubleshoot-ebpf.mdx @@ -163,7 +163,7 @@ If you notice `$[noderunning]` using high CPU: ## eBPF program debug logs -$[prodname]'s eBPF programs contain optional detailed debug logging. Although th logs can be very verbose (because +$[prodname]'s eBPF programs contain optional detailed debug logging. Although the logs can be very verbose (because the programs will log every packet), they can be invaluable to diagnose eBPF program issues. To enable the log, set the `bpfLogLevel` Felix configuration setting to `Debug`. diff --git a/calico-cloud_versioned_docs/version-21-2/operations/ebpf/troubleshoot-ebpf.mdx b/calico-cloud_versioned_docs/version-21-2/operations/ebpf/troubleshoot-ebpf.mdx index bc2edb715c..bc0b086bf4 100644 --- a/calico-cloud_versioned_docs/version-21-2/operations/ebpf/troubleshoot-ebpf.mdx +++ b/calico-cloud_versioned_docs/version-21-2/operations/ebpf/troubleshoot-ebpf.mdx @@ -163,7 +163,7 @@ If you notice `$[noderunning]` using high CPU: ## eBPF program debug logs -$[prodname]'s eBPF programs contain optional detailed debug logging. Although th logs can be very verbose (because +$[prodname]'s eBPF programs contain optional detailed debug logging. Although the logs can be very verbose (because the programs will log every packet), they can be invaluable to diagnose eBPF program issues. To enable the log, set the `bpfLogLevel` Felix configuration setting to `Debug`. diff --git a/calico-cloud_versioned_docs/version-22-1/operations/ebpf/troubleshoot-ebpf.mdx b/calico-cloud_versioned_docs/version-22-1/operations/ebpf/troubleshoot-ebpf.mdx index bc2edb715c..bc0b086bf4 100644 --- a/calico-cloud_versioned_docs/version-22-1/operations/ebpf/troubleshoot-ebpf.mdx +++ b/calico-cloud_versioned_docs/version-22-1/operations/ebpf/troubleshoot-ebpf.mdx @@ -163,7 +163,7 @@ If you notice `$[noderunning]` using high CPU: ## eBPF program debug logs -$[prodname]'s eBPF programs contain optional detailed debug logging. Although th logs can be very verbose (because +$[prodname]'s eBPF programs contain optional detailed debug logging. Although the logs can be very verbose (because the programs will log every packet), they can be invaluable to diagnose eBPF program issues. To enable the log, set the `bpfLogLevel` Felix configuration setting to `Debug`. diff --git a/calico-enterprise/operations/ebpf/troubleshoot-ebpf.mdx b/calico-enterprise/operations/ebpf/troubleshoot-ebpf.mdx index 34ecc883dc..14e7998227 100644 --- a/calico-enterprise/operations/ebpf/troubleshoot-ebpf.mdx +++ b/calico-enterprise/operations/ebpf/troubleshoot-ebpf.mdx @@ -165,7 +165,7 @@ If you notice `$[noderunning]` using high CPU: ## eBPF program debug logs -$[prodname]'s eBPF programs contain optional detailed debug logging. Although th logs can be very verbose (because +$[prodname]'s eBPF programs contain optional detailed debug logging. Although the logs can be very verbose (because the programs will log every packet), they can be invaluable to diagnose eBPF program issues. To enable the log, set the `bpfLogLevel` Felix configuration setting to `Debug`. diff --git a/calico-enterprise_versioned_docs/version-3.19-2/operations/ebpf/troubleshoot-ebpf.mdx b/calico-enterprise_versioned_docs/version-3.19-2/operations/ebpf/troubleshoot-ebpf.mdx index 34ecc883dc..14e7998227 100644 --- a/calico-enterprise_versioned_docs/version-3.19-2/operations/ebpf/troubleshoot-ebpf.mdx +++ b/calico-enterprise_versioned_docs/version-3.19-2/operations/ebpf/troubleshoot-ebpf.mdx @@ -165,7 +165,7 @@ If you notice `$[noderunning]` using high CPU: ## eBPF program debug logs -$[prodname]'s eBPF programs contain optional detailed debug logging. Although th logs can be very verbose (because +$[prodname]'s eBPF programs contain optional detailed debug logging. Although the logs can be very verbose (because the programs will log every packet), they can be invaluable to diagnose eBPF program issues. To enable the log, set the `bpfLogLevel` Felix configuration setting to `Debug`. diff --git a/calico-enterprise_versioned_docs/version-3.20-2/operations/ebpf/troubleshoot-ebpf.mdx b/calico-enterprise_versioned_docs/version-3.20-2/operations/ebpf/troubleshoot-ebpf.mdx index 34ecc883dc..14e7998227 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/operations/ebpf/troubleshoot-ebpf.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/operations/ebpf/troubleshoot-ebpf.mdx @@ -165,7 +165,7 @@ If you notice `$[noderunning]` using high CPU: ## eBPF program debug logs -$[prodname]'s eBPF programs contain optional detailed debug logging. Although th logs can be very verbose (because +$[prodname]'s eBPF programs contain optional detailed debug logging. Although the logs can be very verbose (because the programs will log every packet), they can be invaluable to diagnose eBPF program issues. To enable the log, set the `bpfLogLevel` Felix configuration setting to `Debug`. diff --git a/calico-enterprise_versioned_docs/version-3.21-2/operations/ebpf/troubleshoot-ebpf.mdx b/calico-enterprise_versioned_docs/version-3.21-2/operations/ebpf/troubleshoot-ebpf.mdx index 34ecc883dc..14e7998227 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/operations/ebpf/troubleshoot-ebpf.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/operations/ebpf/troubleshoot-ebpf.mdx @@ -165,7 +165,7 @@ If you notice `$[noderunning]` using high CPU: ## eBPF program debug logs -$[prodname]'s eBPF programs contain optional detailed debug logging. Although th logs can be very verbose (because +$[prodname]'s eBPF programs contain optional detailed debug logging. Although the logs can be very verbose (because the programs will log every packet), they can be invaluable to diagnose eBPF program issues. To enable the log, set the `bpfLogLevel` Felix configuration setting to `Debug`. diff --git a/calico-enterprise_versioned_docs/version-3.22-1/operations/ebpf/troubleshoot-ebpf.mdx b/calico-enterprise_versioned_docs/version-3.22-1/operations/ebpf/troubleshoot-ebpf.mdx index 34ecc883dc..14e7998227 100644 --- a/calico-enterprise_versioned_docs/version-3.22-1/operations/ebpf/troubleshoot-ebpf.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-1/operations/ebpf/troubleshoot-ebpf.mdx @@ -165,7 +165,7 @@ If you notice `$[noderunning]` using high CPU: ## eBPF program debug logs -$[prodname]'s eBPF programs contain optional detailed debug logging. Although th logs can be very verbose (because +$[prodname]'s eBPF programs contain optional detailed debug logging. Although the logs can be very verbose (because the programs will log every packet), they can be invaluable to diagnose eBPF program issues. To enable the log, set the `bpfLogLevel` Felix configuration setting to `Debug`. diff --git a/calico/operations/ebpf/troubleshoot-ebpf.mdx b/calico/operations/ebpf/troubleshoot-ebpf.mdx index 923759dba7..679fb1a221 100644 --- a/calico/operations/ebpf/troubleshoot-ebpf.mdx +++ b/calico/operations/ebpf/troubleshoot-ebpf.mdx @@ -163,7 +163,7 @@ If you notice `$[noderunning]` using high CPU: ## eBPF program debug logs -$[prodname]'s eBPF programs contain optional detailed debug logging. Although th logs can be very verbose (because +$[prodname]'s eBPF programs contain optional detailed debug logging. Although the logs can be very verbose (because the programs will log every packet), they can be invaluable to diagnose eBPF program issues. To enable the log, set the `bpfLogLevel` Felix configuration setting to `Debug`. diff --git a/calico_versioned_docs/version-3.28/operations/ebpf/troubleshoot-ebpf.mdx b/calico_versioned_docs/version-3.28/operations/ebpf/troubleshoot-ebpf.mdx index 923759dba7..679fb1a221 100644 --- a/calico_versioned_docs/version-3.28/operations/ebpf/troubleshoot-ebpf.mdx +++ b/calico_versioned_docs/version-3.28/operations/ebpf/troubleshoot-ebpf.mdx @@ -163,7 +163,7 @@ If you notice `$[noderunning]` using high CPU: ## eBPF program debug logs -$[prodname]'s eBPF programs contain optional detailed debug logging. Although th logs can be very verbose (because +$[prodname]'s eBPF programs contain optional detailed debug logging. Although the logs can be very verbose (because the programs will log every packet), they can be invaluable to diagnose eBPF program issues. To enable the log, set the `bpfLogLevel` Felix configuration setting to `Debug`. diff --git a/calico_versioned_docs/version-3.29/operations/ebpf/troubleshoot-ebpf.mdx b/calico_versioned_docs/version-3.29/operations/ebpf/troubleshoot-ebpf.mdx index 923759dba7..679fb1a221 100644 --- a/calico_versioned_docs/version-3.29/operations/ebpf/troubleshoot-ebpf.mdx +++ b/calico_versioned_docs/version-3.29/operations/ebpf/troubleshoot-ebpf.mdx @@ -163,7 +163,7 @@ If you notice `$[noderunning]` using high CPU: ## eBPF program debug logs -$[prodname]'s eBPF programs contain optional detailed debug logging. Although th logs can be very verbose (because +$[prodname]'s eBPF programs contain optional detailed debug logging. Although the logs can be very verbose (because the programs will log every packet), they can be invaluable to diagnose eBPF program issues. To enable the log, set the `bpfLogLevel` Felix configuration setting to `Debug`. diff --git a/calico_versioned_docs/version-3.30/operations/ebpf/troubleshoot-ebpf.mdx b/calico_versioned_docs/version-3.30/operations/ebpf/troubleshoot-ebpf.mdx index 923759dba7..679fb1a221 100644 --- a/calico_versioned_docs/version-3.30/operations/ebpf/troubleshoot-ebpf.mdx +++ b/calico_versioned_docs/version-3.30/operations/ebpf/troubleshoot-ebpf.mdx @@ -163,7 +163,7 @@ If you notice `$[noderunning]` using high CPU: ## eBPF program debug logs -$[prodname]'s eBPF programs contain optional detailed debug logging. Although th logs can be very verbose (because +$[prodname]'s eBPF programs contain optional detailed debug logging. Although the logs can be very verbose (because the programs will log every packet), they can be invaluable to diagnose eBPF program issues. To enable the log, set the `bpfLogLevel` Felix configuration setting to `Debug`.