Blair Rampling

Blair Rampling is Principal Product Manager at Dash0, where he owns SignalControl, the telemetry ingestion pipeline that decides what enters the platform and what doesn't. His focus is the economics of observability: the sampling, filtering and aggregation work that cuts ingested volume by up to 95% while preserving the signals teams actually act on.

Blair has spent nearly three decades in infrastructure and has seen observability from every side of it. He began as a systems administrator and systems analyst, running large-scale infrastructure for energy, industrial and media organizations, before moving into solutions architecture and pre-sales engineering. Those eighteen years still shape how he builds products: he spent them operating the systems observability tools get pointed at. During the same period he wrote three technical books for Wiley, including DNS For Dummies.

He moved into product management at Infoblox, owning DNS security SaaS and cloud platform appliances, then led core API platform teams at Contentful. At Red Hat he owned the observability stack for OpenShift, including Prometheus, Thanos, Grafana, alerting and remote telemetry, coordinating roadmap across the upstream open-source communities behind them. As the first product hire at Checkly he built the product function from nothing and shipped containerized private monitoring agents for on-premises customers. At Kubeshop he took Botkube, an open-source conversational interface for Kubernetes operations, from concept to enterprise customers; its AI Assistant was among the first LLM-powered troubleshooting agents for Kubernetes. He then served as Vice President of Product Management at Percona, leading product and design for an open-source database platform serving 750+ enterprise customers. He has written for The New Stack on ChatOps and conversational Kubernetes troubleshooting.

Outside his product work, Blair is a practicing coach who works one-to-one with neurodivergent adults, and is autistic himself. That work shapes how he builds and leads teams. He is interested in the engineering organizations that lose their strongest people not to competitors but to environments that ask them to mask in order to belong, and he takes the view that the tools we build and the teams we build them in are the same design problem. Both get better when the people involved aren't required to pretend.