Operations | Monitoring | ITSM | DevOps | Cloud

Ever spent a week wrangling log pipelines just to get your SIEM to stop screaming about missing fields? Wasted way too much time stripping out noisy events and reformatting data for analytics? You’re not the only one. If you work in Security or ITOps, you know the pain: every new data source means another round of schema headaches, more manual mapping, endless field transformations, and a quick prayer that you didn’t break something critical (or let in a flood of junk events).

Join the live stream at 11 am ET, here. Platform teams tend to start with just one, or in some cases a handful of OpenTelemetry (OTel) Collectors usually running in gateway mode. They then embrace the benefit of a vendor-neutral, standardized, telemetry collector for unified logs, metrics, and traces.

Splunk recently announced exciting updates and significant modernizations for the upcoming releases of Splunk Enterprise and Splunk Cloud Platform. This blog is the first in a series to help prepare your organization for these changes by exploring upgrade readiness best practices. This first installment will highlight the Splunk Health Assistant Add-On, a vital tool that supplements the Splunk Enterprise Monitoring Console, designed to streamline your transition to the next version of Splunk Enterprise.

When managing and troubleshooting IIS (Internet Information Services) web server performance, logs are a critical resource. They capture detailed information about every request and response so your team can detect issues quickly. Let’s walk through the main IIS log formats, explore a sample log file, and break down five key types of IIS metrics you should monitor.

Your app logs start simple—maybe a few print() or logging.info() calls. But in production, things get noisy. Thousands of log lines per minute, scattered across services, and it’s hard to know what matters. This is when tools like Graylog and the ELK stack help. They let you collect, search, and make sense of logs, but they do it in different ways. This guide breaks down how each one handles setup, scale, and day-to-day use.

If you’re a Splunk user relying on Dynamic Data Self Storage (DDSS) or Active Archive (DDAA), you’re likely familiar with this frustrating loop.

Join the live stream at 11 am ET, here. OpenTelemetry’s super-power has always been: Choice. Yet, most observability vendors still insist you run their collector. Today we’re removing that last point of friction. With Bring Your Own Collector (BYOC), Bindplane now accepts any upstream-compatible build, recognizes exactly which receivers, processors, and exporters it contains, and adapts the UI and configuration workflow on the fly.