Setup on | 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

Setup on

Secure Tenancy is planned to be End-of-Life at the end of 2022 in favor of built-in security enhancements. Existing customers using Secure Tenancy will continue to be supported on Honeycomb Classic until this time.

Set up Secure Tenancy on 

Complete Configuration in the UI 

You must provide your authentication token to Honeycomb before sending traffic through the secure proxy. Honeycomb will refuse all traffic when the token is missing or does not match the token provided to the web application.

Go to the Secure Tenancy settings page for the relevant team by selecting the lower left avatar menu, selecting “Team Settings”, and then selecting “Secure Tenancy” in the left navigation area.

Look for the Secure Proxy Auth Token field. Enter the auth token you generated earlier, then click outside the text field. Once you see “OK” appear below the text field, you can send data through your Secure Tenancy installation. These new settings may take a minute or so to propagate through our backend.

In the Secure Proxy Address field, enter the URL for your proxy.

Note: No one will be able to connect to the secure proxy directly and decrypt the data. There is a built in security layer that prevents this from happening.

Send an Event to Initialize Secure Tenancy for the Team 

You must send at least one event to Honeycomb using an API key listed for your team. If you do not do this, Honeycomb will not recognize your Secure Tenancy proxy and the UI will show an error.

For versions of Secure Tenancy prior to 1.11, you must use the first API key listed for your team.

You can use a curl command to send the event:

curl -X POST -H "Content-Type: application/json" --header "X-Honeycomb-Team: <api key>" \
--data '{"test":0}' "<Secure Proxy URL:port>/1/events/test_dataset"

Point Integrations at Your Proxy 

All integrations should point to the proxy instead of directly to the Honeycomb API. For example, if you are using honeytail, add the --api_host flag for initial testing, such as in the command below:


For language SDKs and Beelines, all configuration objects have an APIHost property, which can be set with the same effect.

Once data is sent, you should see the dataset appear and be able to query the dataset in the Honeycomb UI.

OpenTelemetry, Tracing, and Metrics 

If you are using OpenTelemetry for metrics or tracing, use the Secure Tenancy proxy’s address and gRPC port for your OpenTelemetry endpoint. Note that Honeycomb requires use of OpenTelemetry for metrics, and strongly encourages it for tracing. The default port is 8081, but it can be overridden using the grpc_listen_addr value in the configuration file.

After Sending Data 

After sending some data to a dataset provisioned under Secure Tenancy, you can specify the fields you want Honeycomb to use to display trace waterfall diagrams. For more information about tracing in Honeycomb, review the Tracing documentation.

If you are a team owner, you can specify the fields from the Definitions tab for that dataset’s settings:

Image of dataset configuration tracing tab

Configure Definitions 

The Secure Tenancy model means that Honeycomb does not know the columns to use for different features, so you have to explicitly designate the columns. Once you have sent some data to a dataset provisioned under Secure Tenancy, navigate to the Definitions tab in that dataset’s details. For more information about configuring dataset definitions, review the Tracing and Home documentation.

Did you find what you were looking for?