Operations | Monitoring | ITSM | DevOps | Cloud

This is a follow-up to Sergiy’s post Errors, traces, logs, metrics: when to reach for what. Modern observability platforms, like Sentry, give developers a lot of choice. For a given problem, should you use traces, profiles, metrics, logs? If you take away one thing from this post, I hope it’s this: when in doubt, start by adding a few targeted log lines.

Chelsea and I recently wrote a guide on how we monitor Claude Code usage internally with Bindplane. TLDR; We remotely manage a Bindplane Distribution of the OpenTelemetry Collector (BDOT) that runs on every engineer's laptop. This setup is great, but it has one downside. Sending to Google Cloud Monitoring, Swarmia, and any other destination directly from an engineer’s laptop is limited to local processing. You can’t get the benefit of centralized routing and processing on a gateway.

How to build governance into autonomous security agents from the architecture up The industry has moved fast on capabilities. Agents now triage alerts, investigate endpoints, create detection rules, and enrich indicators, and they are even capable of performing most actions we as security operators can perform. The architecture patterns are maturing, as are the models, but governance is not keeping pace.

Splunk Enterprise customers want access to the latest Splunk capabilities as quickly as possible. Occasionally, new experiences arrive first for Splunk Cloud, leaving self-managed customers without a clear timeline. Cloud Connect is a creative way Splunk is solving that problem. Cloud Connect gives Splunk Enterprise customers a standard admin path to access curated Splunk-managed services.