Subscribe
Sign in
64
Replies
@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.
This looks pretty awesome - other than the pricing, what're the main differences between other products in this space, like papertrail
@_bsiddiqui storage search retention is a main differentiator for us. We want you to have the ability to log everything without the need to worry about how much gigs you consuming. We took a fresh approach with the user experience as well regarding our backend system. I'd love to hear your thoughts about our product, feel free to try the free demo.
@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.
@alexmorse thanks! We'd love to have you try LogDNA and open to hear your thoughts on how we can make this the best logging platform you ever used. Feel free to message us anytime via the admin system.
@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!
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 : )
Looks great! fellow hoser here btw ;) question: a lot of people are using docker, do you have a syslog sink to make it easy to push my logs there?
@hexsprite Hey Jordan, thanks for the feedback! Docker...not yet. Syslog/docker is up next on our list of todo's. We did have one company during our beta who logged the syslog to a file and used that with our agent for shipping. Now I wasn't sure how easy that was to set up.
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
@maephisto Interesting...I guess this would be useful while having the viewer running in the background or when its closed. Thanks!
This product is so very badly needed. This space was prime for disruption! Solid app and great UI. THANK YOU!!!!
It's hard to count the number of times I thought my life would be better if the logs weren't so hard to look through. I like the simple and clean look! Powerful too.
@art_chang thanks for the compliments! Let us know how we can improve our product, happy to hear your team's feedback on how we can make this better.
I set this up on 4 servers in literally 3 minutes (yes, I was counting!)
So much needed! Solved one of my biggest pain point!
There is one thing I would absolutely love - Seeing these live tailed results inside a slack channel :)
@mrdhat Thanks for the feedback Akshay!
As for the live slack tail, that is definitely possible, though Slack may not like it very much. We have considered this but they do have limits on their API for incoming data like this and they recommend a logging provider. On the other hand, you can setup an alert with a 30-second window to slack and that'll work but it'll be delayed by 30s.
@nxbuzz
> Slack may not like it very much
Makes perfect sense. I think other way can be to add a slash command/bot which does the same thing but only when user wants it. That way Slack might allow it. Not sure though.
Also, I see big potential for a slack like plugin system in LogDNA, I can think of 10 plugins that would be useful after using it just for one day! Do you have any plans to add something like that in the future?
Our team at Pantelligent has been happily using the LogDNA beta for the last few months. The product is well designed and easy to use for many members across engineering, devops, and marketing roles. Very impressed so far, and this is only the beginning of where this product can go! Setup takes about 2 minutes -- give it a try today.
@compumike thanks Mike. We're lucky to have your team on board and you helped guide the direction to where the product is today. We're looking forward to growing with your team at Pantelligent!
@compumike Thanks so much to your team Mike for helping us shape our product to what it is today.
Awesome product and the really like how clean this looks. Wish it was out time ago when I was messing in rails and having to look at a horrid console with tail -f trying to debug stuff.
Wow talk about timing! Just last week we had a bug and it created a ton of log data. We were faced with either paying the absurd overage or stop logging. This would have saved me.
@brunowong it's problem we hear about all the time. Looking forward to having your team use LogDNA!
ThatCleanLife