News for hackers. Stuff that matters.

sprager

Logs fill in a lot of the blanks. You can see bigger trends like what IPs are connecting to your website, are the exception counts rising, how many users are logged on using VPN. They don’t replace numeric metrics, but they add another layer to your monitoring strategy. We use Loggly, which makes it really easy to do both.
We’ve found that the best way to avoid a whole pile of management tools is to centralize your data, both logs and metrics. Tools like Loggly do this well. You can centralize all your logs so that everyone can see across the whole stack, then add monitoring on top so you get a single source of truth. It saves DevOps from having to switch back and forth all the time - makes a big difference to how much we can get done.
Re:What makes combining monitoring and log analysis powerful? on Thursday October 12, 2017 @10:10AM (#15458017)
It’s helpful to be able to correlate the metrics that you’re monitoring with your logs. Once you can connect them, you can really see where the issues are and drill down into the logs to figure out what’s going on. We use Loggly and we’ve found that it saves us significant time.
One definitely doesn’t replace the other. We use Loggly for log analysis as well as our error monitoring tools and it definitely adds distinct value. The traceability and reusability are great, and it lowers overhead as well.

https://www.loggly.com/blog/does-error-monitoring-spell-the-...

Re:GitHub and Source Code on Thursday October 05, 2017 @12:39PM (#15410539)
One way to do it is with a log management tool that integrates directly with GitHub. We use Loggly, it lets us view the code while we’re figuring out what’s going on with the error logs.