Shared publicly  - 
 
Developers: get a better log analysis service with Loggly

Here' the founders of Loggly explain their cloud-based logging platform. Loggly collects and centralizes all of your logs and makes them searchable in a simple user interface. http://loggly.com for more info.

Really smart folks, always love seeing companies that help other companies succeed. High-performance log analysis helps small teams have a big impact. This is a good one for the Hacker News crowd. Thanks Kord Campbell for inviting me over.
99
54
Rick Wehrle's profile photoDale McCrory's profile photoVera Wang's profile photoSandy Rowley's profile photo
22 comments
 
Good idea if it was onsite/offline.. Sending my logs off site scares me.
 
I've been using this for a couple of weeks now. Useful tool - good to see people innovating in low level gubbins. More tools like this for developers please.
 
did they talk about why I should prefer this over Google Analytics or Flurry.
 
It isn't a traffic analytics package. It's a tool for capturing all sorts of log files such as audit files etc. Rather than 'grep'ing to analyse what's going on or to find a problem it's got some good search facilities to find problems and cross reference against other logs.
 
Splunk Storm kills loggly hands down. If you can get in on the beta I highly recommend looking at in instead of loggly.
 
I'll try it for sure. I liked this idea, but I hope they have a good security system
 
Yeah that's one of my thoughts. I run a separate linux security service on my server. I wonder how that would get on with log collection. I guess I would have to construct a cron job to pass the logs over to Loggly.
 
Why would anyone want to send their logs across the internet? I see big security problems with this, and I doubt that any customer would agree to something like this.
 
Hmm. Aside from the security issues, isn't sending data across the net going to be slow? How can it be high performance if it has to go on possibly congested networks? 
 
It is still much slower than logging locally + what about network delay, packet loss, packet order, network issues etc. which could make log really wierd or missing completely (I'm not sure how Loggly works and if someone has an insight please explain), so his objections make sense after all, especially in systems that log a lot of important data for analysis. I would rather like to see local Loggly solution (which could be deployed locally), than cloud based one.
 
I admit that I haven't viewed the video - I'm still using my archaic blackberry - so I guess it's a bit of ignorance to not know that this logging solution is strictly aimed at "cloud" based applications. My background in cloud type environments is a bit narrow as my experience is with scale-up rack servers, not scale out. But as for the software that I work on, logging has always been a problem - especially since it can produce many gigabytes of data on an application fault. If, say, comoputationally dense server has, say, 32 cores sharing X gbps total bandwidth to the outside, isn't is possible to saturate that bandwidth with very verbose logging? 
 
And in regards to data security, when my application faults, there is a signal handler that dumps all of the allocated memory blocks to binary files. This could concievably include security credentials so log security is important.

I perhaps should look into logging solutions more since nothing sucks worse than having to grep my way through logs that are gigabytes in size...
 
Ok. So I watched the first 7 min of the video. It kind of makes sense for their target market now.

Thanks for the info Richard!
 
Goran, Loggly supports, among other protocols, syslog over TCP or TLS. That means that you don't have to worry about packet loss and all those network related issues. TLS also takes care of securing your transmission.
 
Hey all, as Raffy mentioned, you can send us data either over TCP with TLS, or over HTTPS as text or JSON. If you send us JSON from your app, you get automatic field extraction for free. Please drop me a line at david@loggly if you need a hand getting set up, or if you have any technical or security questions.
Add a comment...