Show HN: LogDNA – Set up Kubernetes logging with 2 kubectl commands (opens in new tab)

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?

It would be nice to improve the documentation a bit, and mention that only one agent is needed per node and that this agent will collect the logs across namespaces.

As I have understood,you do not set any namespace for the secret/daemonset, which is fine with me.

But this way, I could install multiple agents (for each namespace).

So a better documentation about the best practice installation for multiple namespaces would be nice.

Great work with this - definitely a pain point. Getting set up and trying it out now.

Thanks for putting this out there Lee! This is huge!

How do you guys handle multi-line log entries? This is the hardest part with existing setups, and would really help us trace exceptions as they occur in real-time.

I love that you appear to have been built from the ground up to be HIPAA-compliant. I have emailed your sales team :)

kubernetes integration FTW! Thank you, thank you!!

I don't think it's odd that it's getting upvotes, but centralized logging is already a feature (as an addon) of k8s. I have a helm chart that's a one-shot for setting up ELK and FluentD as a system service that aggregates all docker stdout logs and tags each stream with k8s metadata, so you can very easily slice/dice your logs even at scale. It includes a cronjob running es-curator so that logs older than some configurable threshold are automatically deleted.

e.g. output from my dev cluster:

      ~CK/elk/templates git:(master)  kc cluster-info 
    Kubernetes master is running at https://192.168.16.16:8443
    Elasticsearch is running at https://192.168.16.16:8443/api/v1/proxy/namespaces/kube-system/services/elasticsearch-logging
    Heapster is running at https://192.168.16.16:8443/api/v1/proxy/namespaces/kube-system/services/heapster
    KubeDNS is running at https://192.168.16.16:8443/api/v1/proxy/namespaces/kube-system/services/kube-dns
    monitoring-grafana is running at https://192.168.16.16:8443/api/v1/proxy/namespaces/kube-system/services/monitoring-grafana

I think people want easy management of this, but I do wonder how successful this particular integration will be with such low-hanging self-managed alternatives. Where I think LogDNA will have a win is that you probably also have things running outside k8s that LogDNA helps integrate. So if you want all your k8s and non-k8s logs aggregated, and don't want to mess with it, then you might go with LogDNA.

Yes that's true for many things in Kubernetes but not as frequent in the logging space for Kubernetes. Many still rely on Fluentd as a parsing filter first to extract metadata like pod name or container name. And most of the logging ones require you to edit your yaml in some way first. Ours is almost copy-pasteable, provided you have a LogDNA API key. :)

Thanks JJ! Yeah, we hope to earn your Kubernetes business :)

Awesome! And definitely let us know if we can improve in any way.