Re:Show HN: LogDNA – Set up Kubernetes logging with 2 kubect...
by weitzj on Wednesday March 15, 2017 @03:58PM
(#13879249)
Also interesting:
I have used the docker integration of logdna beforehand, before moving to Kubernetes.
The integration was done using docker compose per docker compose environment.
The logs which contained `err` were marked red as errors in logdna and I could trigger an alarm.
The same containers in Kubernetes with the same logs seem to marked as `info` now.
I am not sure, why this is and how I can get the same behavior as before.
Is there a way to tell Kubernetes about stderr/stdout? Or how would I trigger logdna to treat a log as error instead of info?
I have used the docker integration of logdna beforehand, before moving to Kubernetes.
The integration was done using docker compose per docker compose environment.
The logs which contained `err` were marked red as errors in logdna and I could trigger an alarm.
The same containers in Kubernetes with the same logs seem to marked as `info` now. I am not sure, why this is and how I can get the same behavior as before. Is there a way to tell Kubernetes about stderr/stdout? Or how would I trigger logdna to treat a log as error instead of info?