3 ms·
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!
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!
- nodesocket 11y agoSo we currently ship around 10GB a month, and it costs us $75 a month from Papertrail. Cost is really a non factor, wouldn't matter if is cost us $200. The ability to search and grep older documents is a bit slow on Papertrail though. Additionally, sending deeply nested JSON, and being able to search on props would be huge. Does LogDNA have a shipper from syslog? Do you have a node.js client lib? Finally can you talk about security? Is traffic encrypted over the wire? Do you encrypted disks at rest?
- leeab 11y agoWe 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.
- lobster_johnson 11y agoI'd like to use LogDNA, but we'd require syslog support, I think. We use Rsyslog to spool logs off to a central server, and we're not about to trust a third-party vendor to keep our data (ie., we want our own copy). Rsyslog can forward to any other syslog server and supports TLS. Edit: Rsyslog can pipe data to a command-line program via the "omprog" plugin, which might be an easier option for you.
- sratner 11y agoIs there a specific syntax for nested fields, such as `res.status:403`, or do you flatten the json structure for indexing purposes?