Operations | Monitoring | ITSM | DevOps | Cloud

Logs are an important part of your application and logging shouldn’t be one of the last things you think of. You should configure your log system, formatter, and style as soon as you start the development of your app. Also, do your best to document the process and share how it works with the rest of your team. In this article, we’re going to demonstrate how logs work in Elixir. We’ll jump into Elixir’s Logger module, which brings a lot of power to logging features.

If you’re reading this article, you’re most likely looking for a simple one-stop-shop way to understand logs. I’m sorry to be the one to tell you this, but logs are not simple enough to deal with easily. In fact, as you start approaching this topic on a practical level you’ll quickly realize how complex and annoying it truly is.

Log scaling is something that should be top of mind for organizations seeking to future-proof their logging solutions. Logging requirements will grow through use, particularly if not maintained or utilized effectively. There are barriers to successful log scaling, and in this post we’ll be discussing storage volume problems; increased load on the ELK stack, the amount of ‘noise’ generated by a growing ELK stack, and the pains of managing burgeoning clusters of nodes.

Monitoring Jenkins is a serious challenge. Logging is often overlooked, but it provides a wealth of information about the health of your Jenkins instance. The following are some approaches to generating informative logging to these issues, that can help to monitor and provide suitable explanations of where the problems lie; even identifying what the possible solutions are.

Last month, MongoDB released v4.4 of their database; the new release contains several changes and improvements, but the introduction of structured JSON logging caught our eye, which makes it easier to extract valuable insights from the logs using products like SolarWinds® Loggly®. In this post, we’ll review how to get started sending your MongoDB logs to Loggly and some of the insights you can easily get from your server logs when you upgrade to the latest version.

When it comes to your network and server processes, one of the key ways your IT team will collect data and insight is through event logging. Collecting the right event data will help inform both essential processes and services, as well as your network security measures, which is why having the proper collection plan in place is key. At Pandora FMS, we offer a host of comprehensive log collection and network monitoring solutions designed to be easily customized.

One of the most common questions that businesses operating under GDPR, LGPD or other similar data regulations have is how long should you keep data? As answers to this question typically seem to vary widely to clear up confusion, we’ve gathered insights from business leaders & specialists across a variety of industries to try and answer this question and shed light on what are reasonable timeframes to keep hold of data, whether that may be financial, employee or other potentially sensitive data.

In a recent post by the Splunk Threat Research team, we addressed permanent and temporary token/credential abuse in AWS and how to mitigate credential exposure. With 94% of Enterprises using a cloud service, and some using at least five different cloud platforms, it’s imperative to stay ahead of threats across multicloud environments. Let’s now turn our attention to Google Cloud Platform (GCP) and how to detect and mitigate OAuth Token Abuse.

Making sense out of logs is not an easy task. Log management solutions, such as Sematext Cloud, gather and accept data from multiple sources. Those sources can have different log events structures, providing a different granularity. They may not follow common, logging good practices and be hard to get some meaning from. Because of that, it is important that the application we develop and follow best practices. One of those is keeping meaningful log levels.