1. Proposed title of this feature request
Debug logging on heapster
3. What is the nature and description of the request?
Debugging heapster is difficult without debug logging, currently requires a special workaround
I think this is a metrics issue (configuring heapster for debugging/logging), not a logging issue (i.e. related to fluentd/elasticsearch/kibana).
Can you please explain this more and what the special work around is?
"Debugging heapster is difficult without debug logging, currently requires a special workaround"
We had to deploy a modified container with the logging enabled, but I do not know well enough the details of how that worked. Solly are you able to provide help on that?
I think this is what Solly was working on with increasing the logging level outputs for certain situations. I will reassign this back to him as he has the patches.
@sross any news on this?
PR posted: https://github.com/kubernetes/heapster/pull/1555
this has been fixed since Heapster 1.3.0, which went into 3.6.