LogDNA
Infrastructure
logging
SHOW HN2017
How HN took it
5 positive, 3 neutral or asking, 0 mixed, 3 critical, out of 11 comments about the project. Thread score +0.15.
Idea: 1 for, 2 againstExecution: 0 for, 1 againstPrivacy: 1 for, 0 against
The thread, comment by comment
Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.
positive neutral or mixed critical about another commenter or something else the maker
What HN said
What people liked
Easy setup compared with fluentd and ELK configs
From 3 comments
Hi everyone, I'm a co-founder / CTO of LogDNA. We were in Y Combinator's W15 batch and launched our cloud logging platform last year…
leeab on HNThanks 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…
HorizonXP on HNCongrats! LogDNA is one of my favorite products. We're likely moving to Kubernetes shortly and were actually worried about logging, so this makes my life a lot easier
jdotjdot on HN
Existing LogDNA users find it a good experience
From 2 comments
I've used LogDNA for a while now. It has been a good experience.
jazoom on HNCongrats! LogDNA is one of my favorite products. We're likely moving to Kubernetes shortly and were actually worried about logging, so this makes my life a lot easier
jdotjdot on HN
Objections
Built-in Kubernetes features and self-managed ELK/Fluentd stacks already cover this
From 2 comments
Seems odd that this is getting upvotes. Most stuff is 2 (actually 1) commands away in Kubernetes ONCE you have the necessary manifests.
manojlds on HNI 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…
andrewstuart2 on HN
Stderr messages were marked info instead of err on Kubernetes
From 1 comment
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…
weitzj on HN
Requests
Better documentation for multi-namespace installs
From 1 comment
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…
weitzj on HN
Multi-line log entry support
From 1 comment
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…
HorizonXP on HN
Questions
How are multi-line log entries handled
From 2 comments
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…
HorizonXP on HNWe currently treat each line separately and we can maintain line ordering okay. We have thought about this before and doing something like: if a line starts with tab or a fixed…
leeab on HN
Why stderr logs show as info on Kubernetes
From 2 comments
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…
weitzj on HNHmmm this may have been a bug. It should show stderr as err. Let me look into this.
leeab on HN
Alternatives named
ELK with Fluentd
From 2 comments
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…
andrewstuart2 on HNYes 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…
leeab on HN