Skip to main content
Ent+
This feature is available as an add-on for the Honeycomb Enterprise plan. Please contact your Honeycomb account team for details.

​
Description

Sends logs and traces to Honeycomb Refinery.

​
Prerequisites

This destination requires network access to a Honeycomb Refinery deployment. If Refinery is configured to forward telemetry to Honeycomb.io, an API key is required. The API key should have “Send Events” and “Create Dataset” permissions. See the Honeycomb Refinery and Honeycomb quick start guide for more information.

​
Supported Types

LogsMetricsTracesHTP Agent
✓✓v1.60.0+

​
Configuration

FieldDescription
Choose Telemetry TypeThe kind of telemetry that should be sent to Honeycomb.
HostnameHostname or IP address where the exporter will send OTLP data.
PortTCP port to which the exporter is going to send OTLP data.
API KeyThe API key to use for sending telemetry to Honeycomb. Make sure the key has the “Send Events” permission. If the provided dataset(s) do not exist, use the “Create Dataset” permission as well. See this Honeycomb documentation for more.
CompressionCompression algorithm to use when sending data to Honeycomb. Available options are none or gzip.
Enable TLSWhether or not to use TLS.
Skip TLS Certificate VerificationEnable to skip TLS certificate verification.
TLS Certificate Authority FileCertificate authority used to validate TLS certificates.
Server Name OverrideOptional virtual hostname. Indicates the name of the server requested by the client. This option is generally not required. Read more here.
Mutual TLSWhether or not to use mutual TLS
Mutual TLS Client Certificate FileA TLS certificate used for client authentication.
Mutual TLS Client Private Key FileA TLS private key used for client authentication.
This destination supports the following retry and queuing settings:
Sending QueuePersistent QueueRetry on Failure
✓✓✓

​
Honeycomb Datasets

Your Refinery server can be configured to route telemetry to specific Honeycomb datasets, however, Refinery will respect the service.name resource field when determining which dataset the telemetry should belong to. You can route telemetry to datasets dynamically by using the Add Fields processor to set service.name resource field.

​
Example Configuration

​
Web Interface

Honeycomb Docs - Honeycomb Refinery Destination - image 1

​
Standalone Destination

apiVersion: bindplane.observiq.com/v1
kind: Destination
metadata:
  name: honeycomb-refinery
spec:
  type: honeycomb_refinery_otlp
  parameters:
    - name: telemetry_types
      value: ['Logs', 'Traces']
    - name: hostname
      value: refinery.default.svc.cluster.local
    - grpc_port: 
      value: 4317
    - name: api_key
      value: your_api_key
    - name: compression
      value: gzip