Notes from an April 2026 release: the logs page redrawn with a collapsible filter sidebar and resizable columns, Lighthouse split onto its own tab in URL monitoring, an AI dashboard agent that reads its own rendered output and revises itself, and an observability agent that now records packet drops, DNS query shape, TCP round-trip time, and syslog alongside the application-protocol view.
Notes from a March 2026 release: more context around a slow query in the platform — concurrent HTTP requests matched by interval overlap, an offline SQL Explain analyzer, and a cross-pod comparison toggle — plus log deduplication, request profiling on the OTLP pipeline, and resilient handling of malformed spans in the agent.
Notes from a March 2026 release: AI-generated dashboards with a visualization linter and cross-provider model fallback, three hand-built dashboards for APM, pod restarts and deployments, and a hybrid full-text log search powered by Manticore.
Notes from a February 2026 release: a tree-search investigation mode, dedicated ingress-controller dashboards with throttling and scheduling delay, and synthetic URL monitoring from outside the cluster.
Notes from a recent release of our observability agent. Lower GC, network, eBPF, and memory cost on the host, plus visibility into Unix sockets, PostgreSQL schemas, Redis over TLS, and same-node container connections.
Notes from a Tel Aviv meetup talk on AI-first coding in 2026: why developer skepticism is mostly outdated, where the real concerns sit (trust, security, fun), and how to share adoption inside a team without mandating it.
Design notes from building an investigation agent for production incidents: tree of hypotheses, specialised subagents, evidence-scored evaluation, bounded search, and configurable models.
Claude Code Workshop & Best Practices Speaker: Evgeny Potapov, ApexData co-founder & CEO
Once the layers from Part 1 are in place and the code from Part 2 has been written, the on-call experience changes. Part 3 of a series on observability strategy: the practices that reduce the rate of escalations from on-call rotations to the developers who built the system.
Observability is not a tool you buy; it is code you write, and a meaningful fraction of the code in a working production system. Part 2 of a series on observability strategy: how much code is instrumentation, what that means for how a team works, and what it costs in development time.
An observability strategy designed from the people the system serves, not the boxes it runs on. A top-down tour of the layers — user experience, business signals, tracing, service monitoring, infrastructure, user feedback — and what each one answers.
