Blogs
Taming Log Noise With the OpenTelemetry Collector's Drain Processor
Do you receive 50 million log lines per day and struggle to see what actually matters? Health checks, heartbeat pings, connection pool messages—they all drown out the errors and anomalies you're trying to find.
BlogsHappy Birthday to Us: Honeycomb 10 Year Manifesto, Part 1Honeycomb
BlogsObservability with AI? Honeycomb with AI!Honeycomb
BlogsHoneycomb Releases Second Edition of Bestseller Observability Engineering to Redefine the PracticeHoneycomb
BlogsHow I Support Humans in the AI EraHoneycomb
BlogsHow We Export Metrics to Third-Party Services - NeonNeon
ResourcesAudit log – Linear DocsLinear
ResourcesLogin methodsLinear
BlogsTaming AI costs: Leaner models for smarter agentic useCohere
NewsCloud Native Computing Foundation Announces OpenTelemetry’s Graduation, Solidifying Status as the DeCncf
LearnProject SetupVercel
BlogsOpenTelemetry Collector vs agent: How to choose the right telemetry approachCncf
BlogsHow Honeycomb Supercharges OpenTelemetry for AIHoneycomb
BlogsSpan or Attribute in OpenTelemetry Custom InstrumentationHoneycomb
BlogsManaging OpenTelemetry Semantic Convention Migrations With the CollectorHoneycomb
BlogsRunning the OpenTelemetry Collector as a LambdaHoneycomb
BlogsBuilding a Simple Synthetic Monitor With OpenTelemetryHoneycomb
BlogsHow Adaptive Tail Sampling Works in the OTel CollectorHoneycomb
BlogsOpenTelemetry vs OpenTracingHoneycomb
