LoginSign Up
← Back to all sparks
P

Parseable

ANALYTICS
Velocity6.3

Log analytics platform built for high-volume observability data

www.parseable.com ↗

Parseable's 3.0 turns a log store into a logs, metrics, traces and APM console.

observabilitypromqlopentelemetrymulti-tenancyapmalerting
◆Current state
Parseable has spent the 2.9 line hardening a multi-tenant ingestion engine — API keys, OAuth sync, tenant quotas, credential masking, and a run of injection and path-traversal fixes contributed from outside the core team. Version 3.0.0 collects that groundwork into a platform release: PromQL-based alerts, dashboard templates, dataset tagging, trace and ingestion endpoints, service maps and APM in the Prism UI, and a custom-provider option in the LLM flow. The ingestion story also changed shape, with fluent-bit dropped from the scripts in favour of an OpenTelemetry collector.
◆Where it's heading
The direction is consolidation: rather than being the cheap object-store log backend that something else queries, Parseable is absorbing the query, alerting and dashboard layers that normally sit above it. PromQL support is the clearest tell — it targets teams whose alert rules are already written for a Prometheus-shaped world. Performance work is tracking that ambition too, with zstd manifests, configurable concurrent object-store calls and faster field-stats sitting alongside the feature list.
◆Prediction
The next releases most likely fill in the metrics side to match the logs side — deeper PromQL coverage and more dashboard and alert templates — while the 3.0 UI migrations settle through point releases. Whether the LLM provider hook grows into anything beyond configuration isn't visible from these entries.

◆Recent moves

  1. 8d ago

    Parseable 3.0 adds PromQL alerts, APM and dashboard templates

    ⚡ SPARK

    The release where the 2.9 line's plumbing work becomes a product story: alerting, dashboards, tracing and APM ship together, and ingestion moves onto an OpenTelemetry collector. It marks the point where Parseable stops being only the storage tier.

    View source ↗
  2. 27d ago

    Release v2.9.5

    Kafka ingestion gains AWS MSK IAM authentication over SASL/OAUTHBEARER plus a configurable OAuth provider, broadening where Parseable can sit in a managed-streaming pipeline. Two externally reported security fixes — an SSRF in alert targets and path traversal in the filters API — land alongside.

    View source ↗
  3. 1mo ago

    Bugfix release v2.9.4

    A security-weighted bugfix release: SQL injection sanitisation in list conditions, an API key exposure, OAuth sync and redirect fixes, and multi-tenant middleware corrections. The concentration of auth and tenancy fixes matches a product being pushed toward shared deployments.

    View source ↗
  4. 1mo ago

    Feature release v2.9.3

    Introduces API keys and top-k grouping in the counts API, two prerequisites for programmatic access and for the dashboard work that lands in 3.0. Small release, but it opens the surface later features build on.

    View source ↗
  5. 1mo ago

    Feature release v2.9.2

    Adds a log context API, optional per-tenant ingestion quotas and eviction keyed on insertion time rather than data time. These are the operator-facing controls a multi-tenant deployment needs before it can be sold as one.

    View source ↗
  6. 2mo ago

    Bug fix release v2.9.1

    A single performance change making field statistics viable at high ingestion volume, with minor UI fixes in Prism. It reads as a direct response to load that the 2.9 feature work created.

    View source ↗