Operations | Monitoring | ITSM | DevOps | Cloud

A recent LinkedIn poll by Peter Zaitsev asked: “What is the most common preventable cause of downtime in your environment?” Guess what most respondents said it was? Surprise, surprise – the top answer is Deploying Broken Code, with 57% of respondents selecting it. This reinforces how critical it is to catch issues before they hit production.

First of all, by frontend memory usage I mean the amount of memory that a user’s browser needs when using your website or webapp. Secondly, do you have any idea how much browser memory your website or webapp requires? Or do you know if or how much the memory footprint of your website/webapp has changed over the last few months? Or after the recent changes or releases you made? I’m guessing you don’t. Yet, this is important to monitor to avoid a bad user experience.

Picture this: a crime scene where the evidence is scattered across five different rooms. There’s a footprint in one, a shattered window in another, a stray shoe on the stairs, and a witness across the street, who only saw part of what happened. Each clue matters in solving the case, but none of them tells the full story on their own.

I’m genuinely excited about what we're rolling out with Copilot Editor, an update to our AI that’s truly packed with new capabilities designed to help you automate pipeline development. You can read about these capabilities here. I wanted to take a moment to share our thinking on a core principle that guides how we build, especially regarding the impactful, and sometimes daunting, world of generative AI.

When you run critical IT or Security systems, you are still on the hook if an alert is missed or a pipeline drops data. That is why Cribl Copilot never tries to replace you. Instead, it works as a partner you can question, guide, and overrule.

We’ve noticed a lot of our customers spend countless hours building and configuring processors. Either parsing JSON, standardizing log formats, normalizing timestamps, masking PII, de-duplicating logs, the list never ends. Most work revolves around recreating the same processor bundles in multiple processor nodes. Bindplane’s new Blueprints solves that boring, repetitive work by providing pre-built processor bundles you can drop into any pipeline with a single click.

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.