<p>We're using Kubernetes 1.1.3 with its default fluentd-elasticsearch logging.</p>

<p>We also use LivenessProbes on our containers to make sure they operate as expected.</p>

<p>Our problem is that lines we send out to the STDOUT from the LivenessProbe does not appear to reach Elastic Search.</p>

<p>Is there a way to make fluentd ship LivenessProbes output like it does to regular containers in a pod?</p>

<p>The output from the probe is swallowed by the Kubelet component on the node, which is responsible for running the probes (<a href="https://github.com/kubernetes/kubernetes/blob/5828836e7c4abb4666a845adb607f1b2a65a1a76/pkg/kubelet/prober/prober.go#L89" rel="noreferrer">source code, if you're interested</a>). If a probe fails, its output will be recorded as an event associated with the pod, which should be accessible through the API.</p>

<p>The output of successful probes isn't recorded anywhere <a href="https://github.com/kubernetes/kubernetes/blob/5828836e7c4abb4666a845adb607f1b2a65a1a76/pkg/probe/exec/exec.go#L38" rel="noreferrer">unless your Kubelet has a log level of at least --v=4, in which case it'll be in the Kubelet's logs</a>.</p>

<p>Feel free to file a feature request in a Github issue if you have ideas of what you'd like to be done with the output :)</p>
