Skip to main content

​
Supported Telemetry Types

​
Prerequisites

  • A Honeycomb account with a Management API key and secret (must have enhance:write scope)
  • An AWS S3 bucket with appropriate write permissions
  • AWS credentials configured on the collector host
  • Network connectivity from the collector to both S3 and the Honeycomb API endpoint

​
Configuration

​
Basic Configuration

The minimum configuration requires Honeycomb API credentials, an S3 bucket, and an AWS region.

​
Advanced Configuration

Data Format and Compression S3 Connection Options Indexing
To minimize Collector processing compute and time, Honeycomb recommends indexing no more than 5 custom fields.
General Settings Retry and Queuing This destination supports the retry settings, the sending queue settings, and the persistent queue settings.

​
Configuration Tips

​
S3 Bucket and Credentials

  • AWS credentials must be available to the collector via IAM role, environment variables, or shared credentials file. The destination does not accept inline AWS credentials.
  • Make sure the S3 bucket policy grants s3:PutObject permission to the collector’s identity.
  • Use the Folder Prefix to isolate telemetry data within a shared bucket.

​
Custom Indexed Fields

  • Fields like user.id or environment can be added to Custom Indexed Fields for faster rehydration queries in Honeycomb.
  • Each additional indexed field increases S3 storage usage due to extra index files written alongside data files.

​
Honeycomb API Endpoint

  • Use https://api.honeycomb.io for US-based Honeycomb accounts.
  • Use https://api.eu1.honeycomb.io for EU-based Honeycomb accounts.

​
Troubleshooting

​
S3 Upload Failures

Errors referencing AccessDenied, NoSuchBucket, or InvalidAccessKeyId in collector logs.
  1. Verify the S3 bucket exists in the configured region and the collector host has valid AWS credentials with s3:PutObject permission.
  2. If using a custom Endpoint for S3-compatible storage, make sure Force Path Style is enabled.

​
Honeycomb API Authentication Errors

Errors referencing 401 Unauthorized or 403 Forbidden from the Honeycomb API endpoint.
  1. Confirm the API Key and API Secret are for a Management API key with the enhance:write scope. Standard ingest keys will not work.
  2. Verify the API Endpoint matches your Honeycomb account region (US vs EU).

​
Missing or Incomplete Index Files

Data appears in S3 but index files are missing or incomplete. Rehydration queries in Honeycomb return fewer results than expected.
  1. Check that the partition format contains all required placeholders (%Y, %m, %d, %H, %M). Missing placeholders will cause validation failures.
  2. Verify that custom indexed field names match the exact attribute keys present in your telemetry data.

​
See also