Managing a large application or service can be difficult if all of your nodes are only logging locally. In order to troubleshoot an issue, you would have to visit each node individually to determine what may be going wrong with a service. This is not a scalable way to manage your application as your infrastructure grows beyond a handful of servers. There are many better options for log aggregation services. Some of these include:
Here at Jungle Disk, we use log aggregation services so we have only one location to visit and review logs. Meaning, when an error occurs, we only have to go to one place to find it. Another added benefit of log aggregation is that it allows us to notify an engineer immediately, if we determine something is not within an acceptable range. In this case, we specify the ranges and we also determine who gets the call. For example, if an application responds back to users with an http error code of 500(internal server error) we can create a rule to address that. Our rule would say “if the log aggregation services sees a 500 error code, then “notify an engineer via pager, web hook and push notification.” We can create similar rules to address any issue, which allows us to be notified the minute an issue is occurring.
In conclusion, using log aggregation services helps us manage our applications and quickly notify us in the event of an issue. This helps us stay on top of any problem which keeps our customers happy. Reach out if you have any questions!