Have you ever looked at your website logs and realized they don’t make sense to you? Maybe your log levels have been abused, and now every log categorizes as “Error.” Or your logs fail to give clear information on what went wrong, or they reveal sensitive information that hackers may harvest. Fixing these problems is possible! Let’s explore how you can write meaningful log messages and use log levels correctly.
We're happy to announce that we've just launched our newly designed dashboard for our logs & metrics platform, allowing DevOps & security professionals to see their vital metrics quicker than ever before. Our team has been keen to respond to the needs of our users through undertaking dedicated research which informed the creation of this latest update to the platform's design. This new design provides improved real-time feedback to users managing & creating new ELK stacks.
We are continuing our blog series about implementing real-time log aggregation with the help of Flink. In the first part of the series we reviewed why it is important to gather and analyze logs from long-running distributed jobs in real-time. We also looked at a fairly simple solution for storing logs in Kafka using configurable appenders only. As a reminder let’s review our pipeline again
Making sure that your ElastAlert yaml file is formatted and configured correctly. All of the below points will prevent alerts from being fired but there may not be an error message associated with the problem. It is possible you may need to contact support to investigate this issue for you. Make sure to proof read the rule you have written to ensure that it is what you expect to see as most of the issues regarding ElastAlert not working correctly is related to the points above.
Writing tests is an underappreciated part of software development. It usually distracts us from our primary goal and makes us feel we aren’t being productive. However, these tests are a great way to ensure our code works as expected, and they can save us plenty of headaches when we don’t have full control of certain parts of a project (for example, when we are working on the client app and another colleague is working on the server).
Logging is an essential part of just about any PHP-based application; whether in a script or a larger application. However, how little is too little and how much is too much to log? If we don't log enough information, when something goes wrong, as it invariably does, then we won't have enough information available to determine what went wrong so that we can fix the problem. However, if we have too much information, then we'll be unable to filter out the white noise.
Many of us have experienced the feeling of hopelessly digging through log files on multiple servers to fix a critical production issue. We can probably all agree that this is far from ideal. Locating and searching log files is even more challenging when dealing with real-time processing applications where the debugging process itself can be extremely time-sensitive.
Welcome to the winter Bugfender newsletter. We hope you’re feeling refreshed after the holidays. We’ve had a fair few updates in the last quarter that we’d love to share with you to kick start the New Year!
