Bindplane

Overview

Bindplane is a unified observability pipeline platform that collects, processes, and routes telemetry data (logs, metrics, and traces) from a wide range of sources. Configure the Bindplane webhook destination to stream log data directly into Hydrolix through the HTTP Streaming API.

This guide covers the Bindplane-to-Hydrolix data path using a webhook destination. For general Bindplane setup, source configuration, and agent deployment, refer to the Bindplane documentation.

This guide covers how to:

1. Set up the prerequisites for integrating Bindplane with Hydrolix.
2. Configure the Bindplane webhook destination to send data to Hydrolix.
3. Verify the integration.

Before you begin

Make sure you have the following:

Item	Description	Example value
Hydrolix cluster	A running Hydrolix cluster with an accessible hostname.	hostname.hydrolix.live
Hydrolix project and table	The destination for incoming Bindplane data. See Projects and Tables to create these.	my_project.my_table
Hydrolix transform	Create a transform which defines the schema that maps incoming data from Bindplane onto a Hydrolix table.	my_transform
Auth token	Bindplane's Webhook destination sends data to the Hydrolix HTTP Streaming API with an Authorization header using an auth token for authenticating against the Hydrolix HTTP Streaming API. See Generate tokens to issue a service account token or Acquiring auth tokens to issue a user account token.	eyJhbGciOi...
Bindplane deployment	A running Bindplane OpenTelemetry deployment (v1.79.0 or later) with at least one configured source.
Bindplane agent type	Your Bindplane configuration builder must use the BDOT 2.0 agent type. The Webhook destination is only available with this agent type.	BDOT 2.0

BDOT 2.0 required

The Webhook destination requires agent type BDOT 2.0. If your Bindplane configuration builder is set to a different agent type, you won't see the Webhook destination option. Switch to BDOT 2.0 before proceeding.

Configure the Bindplane webhook destination

Configure the Bindplane webhook destination to point to your Hydrolix cluster.

1. Open the destination configuration: In the Bindplane UI, navigate to your pipeline configuration and add a new Webhook destination (or edit an existing one).

   Check your agent type

   Make sure your configuration builder is set to agent type BDOT 2.0. The Webhook destination is only available with this agent type.

2. Configure connection settings: Fill in the connection parameters:

   Parameter	Value
   Scheme	https
   Hostname	hostname.hydrolix.live
   Port	443
   Path	/ingest/event
   HTTP Method	POST
   Content Type	application/json

3. Configure additional headers: Add the following HTTP headers in the Additional Headers section. These headers authenticate and route data to the correct Hydrolix table and transform.

   Header	Value	Description
   Authorization	Bearer {token}	Your Hydrolix API auth token. See Auth token in Before you begin for auth token types and resources on creating auth tokens.
   Accept	application/json	Specifies the accepted response format.
   x-hdx-table	{project_name}.{table_name}	The fully qualified Hydrolix table. For example, my_project.bindplane_logs. See Before you begin to create a table.
   x-hdx-transform	{transform_name}	The name of the Hydrolix transform to apply to the incoming data. See Before you begin to create a transform.

   Here's an example of this configuration in the Bindplane user interface:

   

4. Save and apply: Save the destination configuration and apply it to your pipeline. Bindplane begins routing telemetry data from the configured sources through the webhook destination to your Hydrolix cluster.

Test the integration

Once the pipeline is active:

1. Verify data flow in Bindplane: Check the Bindplane UI for successful delivery indicators and confirm there are no errors on the webhook destination.

2. Query data in Hydrolix: Use the Hydrolix query interface to run a query against your table:

   SELECT column1, column2, column3 FROM my_project.bindplane_logs LIMIT 10
   

   Data should begin appearing within a few seconds of the pipeline becoming active.

3. Check Hydrolix ingest logs: Review your Hydrolix cluster's intake-head container logs, located on the intake-head pod, to confirm the cluster is receiving data as expected.

   2026-03-12T17:50:57.115898558Z {"file":"http_event.go:353","level":"info","message":"Processing event for table bindplane_logs","timestamp":"2026-03-12T17:50:57.115+00:00"}
   

Troubleshooting

No data appearing in Hydrolix

• Verify the webhook URL: Ensure the scheme, hostname, port, and path are correctly configured and the endpoint is reachable from your Bindplane agent.
• Check the Authorization header: Confirm the auth token is valid and hasn't expired. See View token issue and expiration dates and Verification steps if you used a service account token.
• Verify the x-hdx-table header: Ensure the value follows the {project_name}.{table_name} format and the table exists in your Hydrolix cluster.
• Verify the x-hdx-transform header: Ensure the transform name matches an existing transform associated with the target table.
• Check agent type: Confirm your Bindplane configuration builder is set to BDOT 2.0.

HTTP errors

Note any of the following errors in the Bindplane agent logs and follow their mitigation steps.

• 401 Unauthorized: The auth token is invalid or missing. Regenerate the token and update the Authorization header. See Auth token in Before you begin to regenerate an auth token.
• 404 Not Found: The path or table/transform combination is incorrect. Double-check the Path, x-hdx-table, and x-hdx-transform values.
• Connection Refused / Timeout: The Hydrolix endpoint isn't reachable from the Bindplane agent. Check network connectivity, firewall rules, and TLS settings.

Test authentication with curl

Validate your credentials by sending a test request. Replace hostname.hydrolix.live with the hostname of the Hydrolix cluster, {token} with your auth token, {project_name}.{table_name} with the Hydrolix project and table names, and {transform_name} with the Hydrolix transform name.

curl -X POST "https://hostname.hydrolix.live/ingest/event" \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json" \
  -H "x-hdx-table: {project_name}.{table_name}" \
  -H "x-hdx-transform: {transform_name}" \
  -d '{"timestamp": "2026-01-01T00:00:00Z", "message": "test event"}'

A successful response (HTTP 200) confirms that your credentials and endpoint configuration are correct.

Learn more

• Bindplane Webhook Destination Documentation
• Bindplane Configuration Guide
• Hydrolix HTTP Streaming API
• Hydrolix Write Transforms