Instrument Ruby applications | Honeycomb

We use cookies or similar technologies to personalize your online experience & tailor marketing to you. Many of our product features require cookies to function properly.

Read our privacy policy I accept cookies from this site

Instrument Ruby applications

Custom code—the logic that most directly impacts your business—is often the most interesting code to observe.

Below, you can find different ways to instrument your application: automatic options, with more ready to go out of the box; and a more direct, customizable option. Either will help you capture data on how your code behaves in production and offer some interesting queries to explore.

OpenTelemetry for Ruby  🔗

OpenTelemetry is a vendor-neutral instrumentation framework with a large community of contributors.

Honeycomb prefers OpenTelemetry and recommends instrumenting your applications using it.

Read our guide to get started using OpenTelemetry for Ruby.

Existing Instrumentation  🔗

If you have existing instrumentation with OpenTelemetry, Zipkin, or Jaeger, use our OpenTelemetry support to send your data to Honeycomb.

Beeline for Ruby  🔗

The Honeycomb Beelines were written before OpenTelemetry. They use a format and API that can only be used with Honeycomb.

Honeycomb embraces OpenTelemetry as the effective way to instrument applications. For any new observability efforts, we recommend instrumenting with OpenTelemetry.

If you already use Beelines, you can continue to use them. However, we do recommend migrating to OpenTelemetry. View setup and usage instructions for the Beeline for Ruby.

View information about migrating to OpenTelemetry.

Use Libhoney Directly  🔗

Libhoney is a low-level library for sending structured events to Honeycomb’s API. The Ruby Beeline package uses libhoney under the hood.

View setup and usage instructions for Libhoney for Ruby.

Open Source  🔗

All Honeycomb integrations are open source, Apache 2.0 licensed, and can be found on GitHub.