Java based application log monitoring
Discover how to monitor logs and errors for Java based applications. Improve the process using Rollbar's Java SDK.
Operations | Monitoring | ITSM | DevOps | Cloud
The Place Where Modern Operations & Technology Come Together
The latest News and Information on Log Management, Log Analytics and related technologies.
Understanding the Apache access log: how to view, locate, and analyze
Log files are invaluable tools for developers and system administrators when it comes to debugging issues within web applications. They often serve as the primary source of information when troubleshooting website malfunctions. Among these logs, the Apache HTTP server’s access log stands out as a key resource for debugging applications and gaining insights into visitor activity.
Logging vs. Metrics
When discussing observability, the “big 3” - logs, metrics, and traces, always get mentioned. But for some, more data doesn’t always mean better. Our lead engineer, JJ, had some advice to share about how logs may not be necessary for everyone. Simplifying your observability stack isn’t difficult - you just need to be intentional with implementation. Check out more MetricFire blog posts below, and our hosted Graphite service! Get a free trial and start using MetricFire now!
The Event Breaker Explained! Split and Unroll Logs with Bindplane Processor Bundles #observability
View the Bindplane Community Call in February for more guidance.
New Bindplane Destinations for Dash0 and Axiom #observability #opentelemetry #otlp
View the Bindplane Community Call in February for more guidance.
Debugging a .NET Application with Loggly
As modern applications grow more complex, debugging becomes increasingly challenging. Applications consist of multiple parts which can generate enormous amounts of log data, making debugging difficult. SolarWinds Loggly can help store, manage, and sift through this data. To demonstrate, we’ll set up an application built on.NET Core 9.0 and MongoDB; then, we’ll walk through how to export its logs to Loggly.
KubeCon 2024 | Interviews with Observability Experts | Observability Insights with Aunsh Chaudhari
In this interview from KubeCon 2024, I sit down with Aunsh Chaudhari, a Product Manager at Splunk, to discuss the biggest trends shaping observability today. With a background in software development and hands-on experience with observability tools, Aunsh shares insights on OpenTelemetry adoption, cost optimization strategies, and the shift toward unified observability. We also touch on emerging topics like AI in observability and the challenges of scaling observability in modern environments.
Finding Root Cause Quickly with Logz.io AI Agent
In the video, Jade Lassery discusses how to effectively manage complex environments, especially when faced with unexpected spikes in errors. She introduces a Logz.io AI agent prompt that assists users in quickly identifying the root cause of these issues. By simply asking the right questions, users can streamline their troubleshooting process and enhance their operational efficiency.
Diagnosing and resolving the 500 internal server error with Apache and Tomcat logs
The dreaded 500 internal server error is a common challenge for web administrators, often signaling a disruption in server operations. Diagnosing the root cause requires in-depth visibility into both web server and application behavior. In this blog, we’ll explore how log management tools simplify the diagnosis and resolution of 500 errors by leveraging insights from both Apache and Tomcat logs.
Diagnosing ActiveMQ broker performance issues with log analysis
Apache ActiveMQ is a widely used message broker that enables seamless communication between distributed applications. However, as the volume of messages increases, performance bottlenecks can arise, leading to slow message processing, high latency, broker crashes, and out of memory (OOM) errors. One of the most critical issues affecting ActiveMQ is OOM errors, which occur when the broker exceeds its allocated heap memory. This can result in service failures, message loss, and prolonged downtime.