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 JavaScript is a vendor-neutral instrumentation framework with a large community of contributors. Read our guide to get started using OpenTelemetry for JavaScript.
Need help choosing between the Beeline SDK and OpenTelemetry for instrumenting your code? Read our guide: Beelines and OpenTelemetry.
If you’re not using OpenTelemetry, you can use the Node.js Beeline to automatically instrument your Node.js applications.
Beelines understand a wide range of standard packages in various ecosystems, and instrument them to send useful events to Honeycomb.
You can start with a Beeline, which will create traces automatically, and then later, optionally add custom traces and context to events to capture your unique needs.
View setup and usage instructions for the Beeline for JavaScript.
We have a number of best practices and example instrumentation snippets available for instrumenting Browser JavaScript Apps.
Libhoney is a low-level library for sending structured events to Honeycomb’s API.
The Node.js Beeline package uses libhoney under the hood.
View setup and usage instructions for Libhoney for JavaScript.
All Honeycomb integrations are open source, Apache 2.0 licensed, and can be found on GitHub.
