We live in a containerized world, and traditional monitoring and logging are being forever changed. The dynamic and ephemeral nature of containers creates new logging challenges. Docker addresses these in some ways. Docker Engine provides various logging drivers that determine where logs are sent or written to. The default driver for Docker logs is “json-file,” which writes the logs to local files on the Docker host in json format.
In the world of information technology, data has become the fundamental currency that holds the highest value. IT Operations Analytics (ITOA) represents one of the largest and richest sources of fresh and actionable data. Many automated tools can be used to make sense of all the information that comes from day-to-day IT operations, from log to agent to wire data.
Kubernetes has fundamentally changed the way we manage our production environments. The ability to quickly bring up infrastructure on demand is a beautiful thing, but along with it brings some complexity, especially when it comes to logging. Logging is always an important part of maintaining a solid running infrastructure, but even more so with Kubernetes. Because Kubernetes clusters are constantly being spun up, spun down, always in flux, making sure logging functions correctly is critical.
In a recent post, we talked about AWS CloudTrail and saw how CloudTrail can capture histories of every API call made to any resource or service in an AWS account. These event logs can be invaluable for auditing, compliance, and governance. We also saw where CloudTrail logs are saved and how they are structured. Enabling a CloudTrail in your AWS account is only half the task.
Ever heard the expression “A picture is worth a thousand words”, well with Sematext Experience we want you to have a picture of the thousand words your customers want to tell you, but usually don’t. At Sematext, we’ve learned over time that we cannot count on customers or visitors on our website to tell us about issues they encounter while using our product or visiting our webpage.
We’re happy to announce official support for Zeek in Logz.io Security Analytics for easier security monitoring! Logz.io Security Analytics provides a unified platform for security and operations designed for cloud and DevOps environments. It’s built on top of Logz.io’s enterprise-grade ELK Stack and is extremely easy to set up and integrate with.
CHAOSSEARCH is building a new standard (a new category) in data analytics. Beyond the cost and complexity of Warehousing, Hadoop, or even Elasticsearch solutions. CHAOSSEARCH is a new kind of big data platform that delivers both search and analytics at a price and simplicity yet experienced. At CHAOS, we are primarily focused on transforming object storage (such as S3) into the first multi-model database, where the user provides read-only access to their S3 storage and CHAOS provides the rest.
As we’ve rolled out Loki internally at Grafana Labs, we wanted logs beyond just simple applications. Specifically while debugging outages due to config, Kubernetes, or node restarts, we’ve found Kubernetes events to be super useful. The Kubernetes events feature allows you to see all of the changes in a cluster, and you can get a simple overview by just retrieving them: This also captures when nodes go unresponsive and when a pod has been killed along with the reason.
RabbitMQ is an open source message broker that was built to implement AMQP in 2007, and over the past twelve years has grown to include HTTP, STOMP, SMTP and other protocols via an ever growing list of plugins.
If you are reading this article, you’re probably familiar with syslog, a logging tool that has been around since the 1980s. It is a daemon present in most Linux-based operating systems. By default, syslog (and variants like rsyslog) on Linux systems can be used to forward logs to central syslog servers or monitoring platforms where further analysis can be conducted. That’s useful, but to make the very most of syslog, you also want to be able to analyze log data.
