Click to zoom
Signals
Tilde has a viewer for logs and traces. It stores metrics, and has no metrics viewer.
Agent logs
The Tilde SDK exports your agent’s logs for you. It authenticates each upload, and the gateway then sets the identifying attributes itself, so an agent cannot forge them.
Deployment-scoped logs cover startup and background work, when no invocation is active.
Read logs in the agent’s Logs tab. Filter by session, run, invocation, trace, scope, and severity. A log line’s trace link opens that trace in the native viewer.
Forward telemetry to your collector
Point Tilde at your collector’s OTLP/HTTP endpoint for each signal, with any headers it needs for authentication. Tilde then sends it a copy of every agent log, trace, or metric batch. Forwarding runs independently of Tilde’s own history. If your collector is unavailable, the Logs and Tracing tabs are unaffected.Reliable delivery
The gateway writes each accepted batch to object storage before it acknowledges the upload. Any gateway replica then delivers it, and retries until it succeeds. An outage in ClickHouse or your collector does not drop telemetry, and never slows your agents. Give each telemetry queue bucket an expiry rule of at least one day. Tilde never deletes a queued batch itself.Retention
Tilde keeps log, trace, and metric history for the retention period you configure, or indefinitely if you set none.Use your own OpenTelemetry provider in an agent
If your agent already configures OpenTelemetry, add Tilde’s processors to your provider.
See Traces for an example.