leeab

I disagree. But we'll see if they do it in a week. :)

Thanks! Send me an email at lee[]logdna.com

Other than the post by their founder above, I'm not really familiar with them. But overall, the 3 points I mentioned in my opening comment is generally similar. But to really find out if you'll like us, you should just try installing us. We have a working live demo on https://logdna.com

We parse JSON and you can search your own fields.

We do not have syslog yet or code libraries. We have an agent that ships logs today via secure web socket.

Everything is encrypted in transit, end-to-end. We haven't not researched into encryption at rest on EC2 yet.

Hi there,

We just built our website this week since we were heads down focused on product. Our documentation is coming soon. We just wanted to get a product into the hands of users and had to make tough decisions on what we needed.

We could be perfect and launch 2 months from now or just launch now with what we have. But you're right, we will be plugging the holes quickly.

Thanks @kordless! I live it in and always have like a dozen open at any given point. I really made this for myself.

Hi there,

I wasn't aware there were several startups every few months in logging. For us, it was an interesting space. Lots of changes happening.

Yes you are somewhat right. It is sending text to a server. But then you send more text and more text and you need to search for all this text in a split second. If you've ever run your own ELK stack for example, you'll realize quickly that you're spending most of your time scaling elastic search to handle the data volume. There is a challenge to doing that.

Having gone through PCI compliance before, technically you cannot send us data that includes card numbers since we're not PCI compliant (yet). But if you don't log that type of data, there is no issue.

Thanks @Rauchg

Yes we do plan to be doing this for S3 archives.

Hmmm, we're using EC2 mainly, not S3. I've seen an option to encrypt disk but haven't researched it fully.

Yes, thanks for the feedback. We'll be adding this and a FAQ section soon. We do encrypt everything in transit, end-to-end, just like most in our industry. We do not encrypt at rest at the moment but will be looking into it.

We automatically detect common formats using regex during ingestion. Many are based on logstash patterns and we have several of our own (including one that just tries to strip out timestamp + log level). If you use a common format, we can usually add it. If you have a custom format that your app defines, we don't have a way for you to add it yet but it'll likely be a regex as you said. (We can always help you create it if you don't want to).

We had a specific audience in mind when we chose 2 days. We were targeting users who just needed to debug their apps, or a low traffic production app. For this, 2 days is plenty. The space is there mainly so they won't have to think about that 5GB/month may equal to 160mb/day or if a bug floods their logs and pushes them over their quota or dealing with overages.

If you care about retention, chances are you're also building a serious product and you want to rely on LogDNA to be around. For that, we hope you'll be on a paid plan.

We want to build the best product we can and by charging appropriately, we can afford better people.

Join us instead!

The main reason we emphasized storage is because we built it with scaling that in mind, that's all. We've also built it with live tail in mind too. It's an okay differentiator since we believe we can handle the volume with our infrastructure. We also followed up with UI/UX which at the end of the day should make us a platform you can goto, get what you need and go back to work.

Give us a try, even if you don't think you'll use the GBs. We have alerting, field parsing and live tail. Analytics is the only piece we don't have today, but we're working towards it.

You're absolutely right...it's important to clarify the vision. Our vision is to do analytics in the future. Today it's aggregate/search/tail/alerting. I think the beauty of this is that our future is still somewhat unknown and we'll listen to our customers on where we ought to be headed.

I think we're targeting different audiences. We're only really for logging.

Mainly in our storage/retention offerings and automatic parsing of fields from common log formats (web logs, mongo/postgres/etc) and json.

We'll parse your JSON if you send it in one line. And you can search on it like this: fieldname:keyword

I think we're pretty good on our UI/UX. Give us a try!

Thanks for the feedback.

Yes, just send us JSON in a line and we'll parse it. You can actually search on that today, we just haven't made a way for you to see the parsed fields yet (coming soon!)

We're fully encrypted end-to-end in transit (but not at rest, currently).

Yeah we need documentation mainly and couldn't get that in time for launch.

I don't think we'll be targeting enterprise users like Splunk...especially since their featureset will take a long time to build out. We might be one day but not today.

Yes, you are correct, more value for your money is our current offer. We want to build a great product and to do that, you have to hire great people, so we came up with a pricing that'll hopefully achieve that.

But it's not set in stone and we'll adjust just like any other company.

Lol sorry! It took us a bit to find a domain that was available. We do like the DNA part though...very logo-able and short!

We actually already do this, but we don't show the results in the log viewer, but we do parse JSON and a whole bunch of various logstash patterns + some of our custom ones. You can even search on them today by doing: fieldname:keyword but it's just hard since you don't know what the fieldnames are...you can guess but we're exposing those soon!

To be honest, we weren't really sure what to pick. We just wanted to have something in place. It's not set in stone and we'll likely change things as we see different use cases.

Many thanks @ebouck!

Yup we will be doing some of the items you mentioned. But you gotta start somewhere and launch something. This is just our mvp. :)

Mainly the 3 items we mentioned above.

Technically, building a scalable infrastructure to ingest an order of magnitude of GBs more than other platforms was a bit challenging (and still is) but I think we're on our way to achieving that.

Ahh yes documentation...we're also working on that as we speak. Sorry about that...we had to pick and choose what we could have for launch. But the instructions on logdna.com should be enough to get you started.

Client libraries are coming soon! We decided on an agent mainly for ease of installation and so we can self-update the agent, so you don't have to manage it (especially for auto-scaling environments).

We will be open sourcing our agent soon, we literally launched this week...some things we couldn't get to for launch.

And yes, it currently streams /var/log/* by default and any other paths your specify to the agent.