https://kube-network-policies.sigs.k8s.io/docs/user/Recent content in User Guide on Kubernetes Network PoliciesHugoen-ushttps://kube-network-policies.sigs.k8s.io/docs/user/json-logging/Mon, 01 Jan 0001 00:00:00 +0000https://kube-network-policies.sigs.k8s.io/docs/user/json-logging/<p>The controller supports structured JSON logging via klog&rsquo;s <code>--logging-format=json</code> flag. When combined with <code>-v=2</code>, it produces machine-readable log entries for every packet evaluated against network policies, making it straightforward to filter and analyze traffic decisions with tools like <a href="https://jqlang.github.io/jq/"><code>jq</code></a>.</p> <h2 id="enabling-json-logging">Enabling JSON logging</h2> <p>Pass the following flags to the controller binary (or set them in the DaemonSet args):</p> <pre tabindex="0"><code>--logging-format=json -v=2 </code></pre><p>At <code>-v=2</code>, two things happen:</p> <ul> <li>The <code>LoggingPolicy</code> evaluator is activated and emits one log entry per packet with its 5-tuple and the source/destination pod names.</li> <li>The policy engine emits a verdict entry for each packet indicating whether it was accepted or denied.</li> </ul> <p>Without <code>-v=2</code>, the <code>LoggingPolicy</code> evaluator is not added to the pipeline and packet-level logs are not produced.</p>