Configure a logging service

[danielballan]

As noted by @Mr0grog, an online logging service serves two purposes:

• making it easy to check the logs without ssh
• collecting them from disparate servers into centralized location

[Mr0grog]

A small menu of commodity services:

• Logentries - have used, good variety of features and has notifications, only really works well in Chrome.
• Papertrail - have used, really straightforward, no frills.
• Loggly - has charting and integrations, e.g. Slack.
• Datadog - recommended by a friend, “it’s the kitchen sink.”
• Logz.io
• Sumo Logic
• LogDNA - Looks a lot like a simplified, prettified Papertrail. No free plan.
• Coralogix - no free plan.
• AWS CloudWatch Logs - built into AWS, no frills

For our situation, we should probably bias towards whatever is easiest/lowest effort to install and log to.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in seven days if no further activity occurs. If it should not be closed, please comment! Thank you for your contributions.

[Mr0grog]

@danielballan how does this fit in (is it obsoleted by?) your metrics/monitoring plans from today’s dev meeting?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in seven days if no further activity occurs. If it should not be closed, please comment! Thank you for your contributions.