Logging as a service
One of my many summer projects is an API that allows colleges and universities to create virtual tours of their campuses. In developing the API, I wanted an easy way to log errors and usage in a decoupled fashion. I didn’t want to have to worry about the details of where the logs would reside or how to rotate them. I found myself in search of LAAS - logging as a service. My search soon ended with Loggly, an API-based logging service that allows, among other things, for web apps to log arbitrary information over HTTP. Since I’m currently writing the backend in Node.js, this seemed a convenient way to integrate some powerful logging without having to worry about the details of the infrastructure. Their free plan was more than generous for my needs, and allowed me to get up and running quickly.
