Configure Vector to send logs, metrics, or traces to Firetiger

Vector can send data to Firetiger using the generic HTTP sink with the /datapoints/ endpoint. Each sink writes to a separate Firetiger table based on the URL path, and Vector’s template syntax lets you route data dynamically.

Configuration Steps

In your Vector configuration file(s) (vector.toml), add a new HTTP sink using the configuration provided below. Within the inputs array, specify your source names (e.g., ["system_logs", "application_logs"]).

Replace YOUR_INGEST_USERNAME and YOUR_INGEST_PASSWORD with your ingest credentials — see Authentication below.

Static table name

Route all events from a sink to a single table:

[sinks.firetiger]
type = "http"
inputs = ["..."] # add your sources here
encoding.codec = "json"
uri = "https://ingest.cloud.firetiger.com/datapoints/vector/logs"
method = "post"
healthcheck = false
compression = "zstd"

[sinks.firetiger.auth]
strategy = "basic"
user = "YOUR_INGEST_USERNAME"
password = "YOUR_INGEST_PASSWORD"

This sends all events to the datapoints/vector/logs table.

Dynamic table name using Vector templates

Use Vector’s template syntax to route events to different tables based on event fields:

[sinks.firetiger]
type = "http"
inputs = ["..."]
encoding.codec = "json"
uri = "https://ingest.cloud.firetiger.com/datapoints/vector/{{ source_type }}"
method = "post"
healthcheck = false
compression = "zstd"

[sinks.firetiger.auth]
strategy = "basic"
user = "YOUR_INGEST_USERNAME"
password = "YOUR_INGEST_PASSWORD"

This creates a separate table per source type (e.g., datapoints/vector/file, datapoints/vector/syslog).

Supported Formats

The /datapoints/ endpoint accepts:

• JSON array: [{"key": "value"}, ...]
• JSONL / NDJSON: One JSON object per line (use Content-Type: application/jsonl)
• Single JSON object: Automatically detected as JSONL

Vector’s encoding.codec = "json" sends events as JSON arrays, which is the recommended format. Compression (gzip, zstd, deflate, snappy) is supported via the Content-Encoding header.

Authentication

Firetiger expects HTTP basic auth for ingestion. Your ingest username and password can be found in the Firetiger UI on the Settings page. These are the same credentials used for OpenTelemetry collectors and other ingest integrations.

Substitute those values for YOUR_INGEST_USERNAME and YOUR_INGEST_PASSWORD in the configuration examples above.