Hosted beta

sigiro reads OpenTelemetry (traces, logs, metrics, profiles). You query the data back with SQL. During the beta, we set up each tenant by hand. Replace <your-sigiro-host> below with the host that your operator gives you.

1. Get your API key

Your operator sends you a key with the form sk_<yourtenant>_<random>. Treat the key like a password. sigiro shows the key one time only. You cannot recover the key, but you can rotate it. The key authenticates both ingest and queries.

2. Point your OpenTelemetry exporter at sigiro

Use standard OTLP over HTTP or gRPC. For authentication, use the standard Authorization: Bearer header.

OTLP/HTTP (port 4318, recommended):

export OTEL_EXPORTER_OTLP_ENDPOINT="https://<your-sigiro-host>:4318"
export OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer sk_<yourtenant>_<random>"
export OTEL_EXPORTER_OTLP_PROTOCOL="http/protobuf"

OTLP/gRPC (port 4317):

export OTEL_EXPORTER_OTLP_ENDPOINT="https://<your-sigiro-host>:4317"
export OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer sk_<yourtenant>_<random>"
export OTEL_EXPORTER_OTLP_PROTOCOL="grpc"

Your SDK posts each signal to its standard OTLP path (/v1/traces, /v1/logs, /v1/metrics, /v1/profiles). HTTP supports gzip. Both ports use TLS (https://). One request must be 8 MB or smaller after decompression. Default SDK batch sizes stay well below this limit.

3. Confirm that the data arrives

Send some telemetry. Wait a few seconds, because the flush interval is about 1 s. Then run this query:

curl -s "https://<your-sigiro-host>/v1/query" \
  -H "Authorization: Bearer sk_<yourtenant>_<random>" \
  --data 'SELECT count(*) AS n FROM sigiro_spans'

A non-zero n means that traces arrive. Query only after your first batch. A new tenant that never sent data has no storage.

4. Query your data (SQL API)

• Endpoint: POST /v1/query on the main HTTPS port.
• Auth: Authorization: Bearer sk_<yourtenant>_<random>.
• Body: the raw SQL string, not JSON.
• Response: a JSON array of row objects. The header x-sigiro-truncated: true|false reports whether sigiro capped the results.

You see your own data only, because each tenant has an isolated catalog.

Tables: sigiro_spans, sigiro_logs, sigiro_log_templates, sigiro_metrics_gauge, sigiro_metrics_sum, sigiro_metrics_histogram, sigiro_metrics_exp_histogram, sigiro_profiles, and the sigiro_anomalies table. The sigiro_anomalies table holds precomputed regime shifts. The anomaly pass writes these shifts continuously. GET /v1/anomalies serves the same shifts as typed JSON. Attribute columns (*_attributes, events_json, and similar) hold JSON text. Read a field with json_extract(col, '$.key') or col ->> 'key'.

Allowed SQL: SELECT only, against the sigiro_* tables. sigiro rejects writes and DDL. sigiro also blocks the file, URL and S3 readers (read_csv, read_parquet, glob and similar). Joins, window functions, aggregates and json_extract all work.

CTEs are rejected. A WITH clause fails validation, whatever the clause contains. Rewrite it as a derived-table subquery: SELECT ... FROM (SELECT ...) t. The hosted service blocks information_schema too, because one shared catalog holds every tenant.

Examples:

-- Slowest operations, last hour
SELECT service_name, span_name,
       approx_quantile(duration, 0.95) / 1000.0 AS p95_ms, count(*) AS n
FROM sigiro_spans
WHERE timestamp > now() - INTERVAL '1 hour'
GROUP BY 1, 2 ORDER BY p95_ms DESC LIMIT 10;

-- Error-log rate per route, last 15 min
SELECT service_name, log_attributes ->> 'http.route' AS route, count(*) AS errors
FROM sigiro_logs
WHERE timestamp > now() - INTERVAL '15 minutes' AND severity_number >= 17
GROUP BY 1, 2 ORDER BY errors DESC;

5. Limits

sigiro has no secondary indexes. Therefore bound every query by timestamp. A bound gives you speed. A bound also prevents timeouts and truncation.

6. Data retention

During the beta, treat sigiro as a live query service, not as a system of record. Ask your operator for the current retention window. Export any data that you must keep for a long time.