sql_setup.txt

SEARCHAPI POSTGRES SETUP

The service runs its own idempotent migrations on startup. A site only needs a
database and a user with table/index creation rights.

Example:

  CREATE DATABASE telemetry WITH ENCODING 'UTF8';
  CREATE USER searchapi WITH PASSWORD 'replace-me';
  GRANT ALL PRIVILEGES ON DATABASE telemetry TO searchapi;

Core tables created by the service:

  assets
  procedures
  test_runs
  channels
  telemetry_samples
  alarms
  operator_annotations
  audit_events

Eventing model:

  Every create/ingest action writes an audit_events row.
  The service publishes the audit event id on the telemetry_events channel.
  If Elasticsearch is configured, the listener indexes the audit event.
  If Elasticsearch is not configured, the API searches audit_events directly.

Replay model:

  telemetry_samples.replay_key is unique when provided.
  Gateways should generate stable replay keys per source message.
  Replayed messages with the same key are rejected as duplicates.