Blogs

What Is Auto-Instrumentation?

Honeycomb

Instrument code, even if it is written by someone else, by using Honeycomb and OpenTelemetry, mixed with automatic and manual instrumentation.

Visit Site

Blogs Honeycomb

BlogsImplementing High-Cardinality Instrumentation in Frontend AppsHoneycomb BlogsStop Logging the Request Body!Honeycomb BlogsSlicing Up—and Iterating on—SLOsHoneycomb BlogsData Strategy for SREs and Observability TeamsHoneycomb BlogsAI Amplifies Your Existing Practices: Lessons from Our Shift to an AI-First StrategyHoneycomb BlogsOptimizing the OpenTelemetry Python SDK for LLM WorkloadsHoneycomb Products & ServicesNew in GitBook: Global reusable content, auto-updating API docs, and much moreGitbook Products & ServicesHow to auto-generate API documentation from an OpenAPI spec with GitBookGitbook BlogsGuide to Perfecting AI Video Captioning for YouTubeHeygen BlogsThere Is Only One Key Difference Between Observability 1.0 and 2.0Honeycomb BlogsBehind Modem.dev’s Product Velocity - NeonNeon BlogsAugust Changelog: What’s New at NetlifyNetlify BlogsMeasure What MattersHoneycomb BlogsAuto Job Cancellation for Vercel for GitHubVercel BlogsSpan or Attribute in OpenTelemetry Custom InstrumentationHoneycomb BlogsCode-level telemetry instrumentation: From “oh hell no” to “worth it”Cncf BlogsTry the new Essential Next.js plugin, now with auto-install!Netlify BlogsSecure more apps with External Access Tokens andReplit ResourcesInstrumentationVercel BlogsOpenWebUI + Model Runner: Zero-Config Local AIDocker