Vector GreptimeDB Sink – greptime_timestamp used instead of my custom timestamp column

[Anietov]

Hi everyone,

I'm running into an issue using Vector to send logs to GreptimeDB. Even though my payloads include a properly formatted timestamp field called ts_event, and my tables in GreptimeDB are defined using TIME INDEX (ts_event), Vector still inserts data using a new column called greptime_timestamp instead.

Here’s what I’ve confirmed:

My Vector remap transform correctly sets .ts_event as an RFC 3339/ISO 8601 timestamp.

I manually created the tables in GreptimeDB with this structure:

. = {
  "ts_event": parse_timestamp!(.ts_event, format: "%+"),
  "node": .node,
  "event_type": .event_type,
  "message": .message
}

[sinks.greptimedb_room_closed]
type = "greptimedb_logs"
inputs = ["room_closed"]
endpoint = "http://localhost:4000"
table = "room_closed_logs"
dbname = "public"
compression = "gzip"

CREATE TABLE room_closed_logs (
  ts_event TIMESTAMP,
  node STRING,
  event_type STRING,
  message STRING,
  TIME INDEX (ts_event)
) ENGINE = mito
WITH(ttl = '7d');

[pront]

Hi @Anietov, the greptime_timestamp is used by the greptimedb_metrics sink but you are clearly using greptimedb_logs. What does your pipeline look like?