Blogs

How we tracked down a Go 1.24 memory regression across hundreds of pods

Datadoghq

We rolled out Go 1.24 and saw a memory regression. Here’s how we dug into system metrics, uncovered a bug in the runtime allocator, and worked with the Go team to help fix it.

Visit Site

MCP security risks: How to build SIEM detection rulesDatadoghq Kubernetes pod pending failures: How to debugDatadoghq Automate workflows with Datadog’s Amazon EventBridge integrationDatadoghq How to implement log management policies with your teamsDatadoghq Making agentic token costs visible in productionDatadoghq LLM guardrails: Best practices for deploying LLM apps securelyDatadoghq Breaking down common documentation mistakesMintlify 10 best AI observability tools for monitoring and evaluating agents in 2026Mintlify The 8 Best HubSpot Alternatives in 2026Zapier How We Eliminated Long-Lived CI Secrets Across 70+ ReposPulumi Pushing Pulumi ESC Secrets into External PlatformsPulumi The Go Memory Model - The Go Programming LanguageGo What is a Load/Store Unit?Modal How Hunch supercharged AI workflows with Modal SandboxesModal Cerebras Announces Six New AI Datacenters Across North America and Europe to Deliver Industry’sCerebras Memo-ry: Simplifying Daily Tasks for People with Memory Loss - CerebrasCerebras New Docker and JFrog Partnership Designed to Improve the Speed and Quality of App DevelopmentDocker How Mondelez Accelerates Supply Chain Training Across 150+ Global Manufacturing PlantsSynthesia Announcing dependency caching for Pulumi DeploymentsPulumi What is Global Memory?Modal