So you want to use Honeycomb. Maybe this is because you want high cardinality or faster querying times. Maybe you are at the beginning of a project to onboard to tracing or OpenTelemetry. Maybe you are ready to start correlating your log data to trace data, or want to add data from technologies that emit structured logs.
Regardless of why you want to send your structured logs to Honeycomb, you are in the right place.
Honeycomb refers to structured data as information that follows a predefined, standardized data model. Often this information takes the form of logs emitted by applications to log files other log handlers. For example, you may use a logging library that generates JSON-structured logs.
If you’re ready to send your structured logs to Honeycomb, you can use any of the following options:
Honeycomb Telemetry Pipeline: Use the Honeycomb Telemetry Pipeline, which lets you standardize the entirety of telemetry operations on OpenTelemetry, whatever the format of existing logs, traces, and metrics.
OpenTelemetry Collector: Use the OpenTelemetry Collector as a logging agent to send structured logs to Honeycomb.
Libhoney: Use Honeycomb’s suite of structured logging libraries to create and send structured logs to Honeycomb’s Events API.
Once your data is in Honeycomb, you will want to enhance it. For structured logs, you may want to:
For structured logs, Honeycomb lets you easily query on your data using fields, like status or timestamp. To learn how to analyze your data in Honeycomb, visit Investigate Log Data in Honeycomb.
