@timolins Thanks for the feedback about the sign up process. That's an interesting idea to have a responsive dashboard and be able to run searches on the go! I'll pass this along to the team, thanks for the product idea!
This looks great. The storage sold me. So many times I was forced to stop using a logging product because they offer a measly amount of storage.
Do you guys have plans for application specific logging integration down the line, e.g logging for NodeJS or Python applications?
@riyadhalnur Thanks for the kind words Riyadh. Yes, we'll have a full code library soon supporting many languages. We figured an agent would be sufficient for now. :) NodeJS would likely be first since we're also on Node.
We recently signed up for Loggly, but many of their features we just don't use. And the ONE I really want (centralized 'tail -f' is on their enterprise plan). It looks like this does everything we need and nothing we don't.
One quick onboarding suggestion: The magic moment happened when I got to just just run 'logdna tail' on my machine and it "Just Worked". Magic! However, asking me to sudo install a bunch of stuff was a barrier. I would have gotten to the "magic moment" faster if I could have seen it in action first. A demo log source perhaps? Just anything I could tail without needing sudo install code fetched from various untrusted sources. Of course, after a little digging on you guys I found you were pretty legit ; )
I'll probably be upgrading shortly! (Sorry Loggly!)
@rsweetland I know exactly what you're talking about (the magic moment) and that's why we made the live demo. We debated about this...whether to have a demo source or not. But we ended up with what we have now because we had a couple goals and one was to get you to be a user with your own data (some people don't believe things work unless they see it with their own data). So yes, i totally hear you but it's hard line to draw in the sand. We may still do what you said though. The debates not over yet. :) And thanks for the feedback!
@nxbuzz No problem. I can totally see the other side as well. Either way, my story with LogDNA had a happy ending – and it was magical to see my own familiar log data suddenly streaming : )
@devankoshal thanks for the kind words. Glad you enjoyed the easy onboarding experience. Feel free to message us anytime with any questions or comments! Happy to help out.
Nice! Using papertrail now and considering switch to loggly. About 20 hosts. Some questions:
1. do you have chef packages available to install the daemon ?
2. why are you not using rsyslogd ?
3. the instructions on how to join only allow you to specifiy one log path. Is there any way to define your log files in a config file ?
@digitalbase Hi Gijs,
1 & 2. Not yet. We had to choose which features would make it for the launch and these had to be pushed. But rsyslogd is on our list.
3. Yup, you can add paths one or many at a time or you can modify the config file directly at /etc/logdna.conf
Huge amount of storage compared to something like Papertrail. Any plans to work with Heroku and make this available via an add-on through their platform?
@hopkinschris Yup Heroku is available now but not thru their platform yet. We have a CLI program that'll generate a: "heroku drains:add" command. Let me know if you have trouble setting this up.
Replies
Feedback Fish
LogDNA
Uplette
dialex
LogDNA
followupthen
LogDNA
followupthen
An American Road Trip
LogDNA
LogDNA
Commerce.js by Chec
LogDNA
PR Stack
LogDNA
ThatCleanLife
LogDNA