LoginSign Up
← Back to all sparks
S

SigNoz

INFRA · APIS
Velocity5.0

SigNoz moves log bodies to queryable JSON storage, at a disk cost during migration.

observabilitylog-storagellm-observabilityopentelemetryapi-migration
◆Current state
SigNoz now renders AI traces as a conversation in its Thread view, reading OTel gen_ai attributes and SDK-specific formats. The latest release starts moving log bodies to native JSON storage (body_v2), so any field in a log body can be queried by path with less data scanned. During the transition each log body is written twice, so OSS users need extra disk. The v1 alert rule API is still removed on November 11.
◆Where it's heading
Alongside the LLM-observability work, SigNoz is rebuilding core storage and APIs: alerting moved to v2alpha1 schemas and logs to structured JSON. The cost is a run of migration notices that OSS and API users must act on.
◆Prediction
Expect the double-write phase to end in a later release that makes body_v2 the default, and the v1 rules removal to ship on schedule.

◆Recent moves

  1. 10d ago

    Log bodies move to queryable JSON storage; v1 alert API ends Nov 11

    Log bodies start moving to native JSON storage, making every field queryable by path and log queries cheaper, but OSS users need spare disk while bodies are written twice. The release also repeats the November 11 removal of v1 alert rules.

    View source ↗
  2. 17d ago

    AI traces are now easy to read with the new Thread View

    AI traces now open in a Thread view that lays out a full chain of LLM calls as a conversation, with tool calls and reasoning, across most major providers and frameworks. It turns SigNoz's tracing into a usable LLM debugging tool rather than a JSON dump. The release also repeats the November 11 v1 alert rules deadline.

    View source ↗
  3. 23d ago

    v1 alert rules removed Nov 11; Telegram alerts, GCP logs

    The second phase of the alerting API migration: v1 rule endpoints go on November 11, a month after alert history. Saved views in the sidebar, v2 Notification Channels, Telegram alerts and GCP logs make it one of the denser weekly releases.

    View source ↗
  4. 1mo ago

    Rebuilt panel editor, heatmap panel, Kubernetes status filters

    The last notice before the v1 removal ships with a rebuilt dashboard panel editor, a heatmap panel for latency-style distributions, and Kubernetes status filters with related-resource navigation. New onboarding for Microsoft Agent Framework, Vercel Eve, Bun and SNMP widens ingestion toward agent tooling.

    View source ↗
  5. 1mo ago

    Final notice: v1 alert history API removed Oct 15

    A final reminder that the v1 alert-history endpoints return 404 from 15 October, with v2 using query parameters and cursor pagination. It is the last step in a deprecation SigNoz has repeated since August.

    View source ↗
  6. 1mo ago

    v1 alert history API removal reminder (Oct 15)

    The removal reminder repeats with a fixed date, which signals the security-driven cut-off won't slip. API scripts and dashboards on v1 need to move to v2.

    View source ↗