leeab

7 ms·

31.
by leeab 11y ago
No, sorry, I just didn't have time to set this up. We'll get this before the updates are made.
32.
by leeab 11y ago
We do automatically parse most common log formats and you can query on those. You can also send us JSON and query on that too.
33.
by leeab 11y ago
I'd love to see what you have worked on. :)
34.
by leeab 11y ago
I disagree. But we'll see if they do it in a week. :)
35.
by leeab 11y ago
Thanks! Send me an email at lee[]logdna.com
36.
by leeab 11y ago
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 install
37.
by leeab 11y ago
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
38.
by leeab 11y ago
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
39.
by leeab 11y ago
Thanks @kordless! I live it in and always have like a dozen open at any given point. I really made this for myself.
40.
by leeab 11y ago
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 a
41.
by leeab 11y ago
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.
42.
by leeab 11y ago
Thanks @Rauchg
43.
by leeab 11y ago
Yes we do plan to be doing this for S3 archives.
44.
by leeab 11y ago
Hmmm, we're using EC2 mainly, not S3. I've seen an option to encrypt disk but haven't researched it fully.
45.
by leeab 11y ago
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.
46.
by leeab 11y ago
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 u
47.
by leeab 11y ago
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 ab
48.
by leeab 11y ago
Join us instead!
49.
by leeab 11y ago
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 ou
50.
by leeab 11y ago
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 so
51.
by leeab 11y ago
I think we're targeting different audiences. We're only really for logging.
52.
by leeab 11y ago
Mainly in our storage/retention offerings and automatic parsing of fields from common log formats (web logs, mongo/postgres/etc) and json.
53.
by leeab 11y ago
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!
54.
by leeab 11y ago
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-
55.
by leeab 11y ago
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 curren
56.
by leeab 11y ago
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!
57.
by leeab 11y ago
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
58.
by leeab 11y ago
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.
59.
by leeab 11y ago
Many thanks @ebouck!
60.
by leeab 11y ago
Yup we will be doing some of the items you mentioned. But you gotta start somewhere and launch something. This is just our mvp. :)

More ›