Operations | Monitoring | ITSM | DevOps | Cloud

OpenTelemetry is the recommended path today for instrumenting applications with tracing in a standard, vendor-agnostic and future-proof way. In fact, OpenTelemetry (nicknamed OTEL) encompasses all three pillars of observability: tracing, metrics, and logs. The tracing element of the specification is now stable with the rest following. This is innovative stuff! You can read more on OpenTelemetry and the current release state on this guide.

When you’re planning an application performance monitoring (APM) strategy, collecting metrics from storage services like Amazon S3 may not seem like a priority. After all, part of the point of object storage is that applications can read and write from storage buckets seamlessly, with minimal configuration and overhead. Unlike databases or file systems, storage buckets don’t require complex configurations that could lead to performance issues.

Not every organization is - or even wants to be - a Fortune 500. Unfortunately, cybercriminals don’t care how big your company is. In fact, they often look to target small and midsize businesses (SMBs) knowing that they might have fewer security resources. You have the same problems that the big companies have, but you also have less money and people. Using centralized log management can give you the security solution you need, at a price you can afford.

Image via Pixabay As any developer or IT professional will tell you, when systems experience issues, logs are often invaluable. When implemented and leveraged effectively, the data produced by logging can assist DevOps teams in more quickly identifying occurrences of problems within a system. Moreover, they can prove helpful in enabling incident responders to isolate the root cause of the problem efficiently. With that being the case, maximizing the value of log data is vital.

Log management software gives the primary diagnostic data in your applications’ development, deployment, and maintenance. However, choosing the log sources to log and monitor could often be a daunting task. The primary cause of concern in monitoring all sources is the high price tag that many SIEM tools in the market charge based on the number of users and sources ingesting logs. At observIQ, we offer unlimited users and sources.

We just announced the creation of a new RemoteWrite SDK to support custom metrics from applications using several different languages. This tutorial will give a quick rundown of how to use the Java SDK. This SDK – like the others – is completely free and open source, and is meant to apply to any output destination, not just Logz.io.

We’re excited to announce the general availability of the LogDNA Agent 3.3, which introduces Linux and ARM64 support to our Rust Agent. This new support in our Rust Agent provides improved performance and enables a few features previously only available for our Kubernetes customers, such as various configurations within the Agent and the ability to run as a non-root user. Additionally, we have added in Prometheus Metrics that help provide insights into your Agent.

In today’s highly interconnected worlds, CISOs face a dual challenge: protecting data and reporting to the Board of Directors. Log management has long been a tool in the CISO’s back pocket, helping gain insight into potential security issues. However, the rise of cloud-based infrastructures changes this, making log management increasingly difficult.

Consider the following question: Why do most teams face pressure to rethink traditional logging and observability approaches? Asking this question to most engineers would likely result in answers centered on the challenges posed by microservices apps. Because microservices are more complex than monoliths and involve more moving parts, they require more sophisticated, granular log collection, correlation, and analysis.