4 ms·
I put together a similar logging setup for our servers recently; except I'm using CouchDB for my store and NLog (said servers are C#) for the library. Reasons I
by ConstantineXVI 15y ago
I put together a similar logging setup for our servers recently; except I'm using CouchDB for my store and NLog (said servers are C#) for the library. Reasons I'm using Couch instead of SimpleDB:
1) REST+JSON API made integrating it super-simple (had to add a single line to NLog to set MIME types to make Couch happy)
2) We use SDB in our service; so if SDB blows up, not only would things break, we couldn't easily get at our logs to see why.
Biggest drawback I've found to Couch in this context is that it loves to devour disk space; you quickly learn to cron some compaction jobs.
- maratd 15y agoWhy not use something like rsyslog and have it transfer the logs via udp to a centralized rsyslog server? Very easy to setup.
- ConstantineXVI 15y agoThe first motivation for this setup was to make our logs easily parseable to extract stats from them; Couch seemed like a natural fit to store them. Plus, Couch's sane API essentially means we're able to grab the logs from any tool/language with minimal effort. I'm well aware that this isn't necessarily the best/proper way to handle logs, but we're all fairly pleased here with how it's worked out.