v0.9.0

[Polliog]

🌊 Logtide 0.9.0

This release brings three long-requested pillars to Logtide: a fully customizable dashboard system, proactive infrastructure monitoring with public status pages, and a structured log parsing pipeline.

✨ What's New

📊 Custom Dashboards (#151)

• Your layout, your rules: replace the previous fixed dashboard with as many team-specific dashboards as you need, each composed of freely arranged and resized panels.
• 9 panel types: time series, single stat, top-N table, live log stream, alert status, metric chart, metric stat (OTLP with avg/sum/min/max/count/last/p50/p95/p99), trace latency (p50/p95/p99), detection events, and monitor status - every data source in Logtide is now representable.
• Drag-to-reorder and drag-to-resize: panels snap to a responsive 12-column grid, collapsing gracefully to 6 columns on tablet and 1 column on mobile.
• Inline edit mode: toggle editing directly on the dashboard - no separate page, no lost context. Changes are held in a local snapshot and discarded on Cancel.
• Dashboard switcher: a header dropdown lets you switch, create, delete, import, and export dashboards. The default dashboard is protected from deletion.
• YAML import/export: round-trip your dashboards through version-controlled YAML files alongside your infrastructure code.
• Versioned schema with migrations: schema_version: 1 ships with a migration framework in @logtide/shared so future schema changes are applied automatically on read.
• Zero visual regression for existing users: the auto-created Default dashboard replicates the previous fixed layout (4 stat cards + log volume + top services + top error messages) exactly.
• Cross-org isolation: every panel data fetch verifies that config.projectId belongs to the requesting org, blocking data leaks via crafted YAML imports or stale references.

🖥️ Service Health Monitoring and Status Pages (#152)

• 3 monitor types: HTTP/HTTPS (configurable method, expected status, custom headers, body assertion via contains or regex), TCP ping, and heartbeat (alert when no ping arrives within the grace window).
• Uptime Kuma-inspired status page (/status/:projectSlug): 45-day heartbeat bar grid, per-monitor uptime badge, overall status banner, light/dark mode toggle. Visibility is configurable per project - disabled (default), public, password-protected, or org-members-only.
• Auto-incident creation: when the consecutive failure threshold is crossed, a SIEM incident is created with source: 'monitor', linked via monitor_id, and dispatched through existing email/webhook notification channels.
• Scheduled maintenances: define maintenance windows with start/end times; active windows suppress incident creation and display a banner on the status page.
• Manual status incidents: publish incident communications (Investigating → Identified → Monitoring → Resolved) with a full update timeline, independent from SIEM incidents.
• Heartbeat endpoint: POST /api/v1/monitors/:id/heartbeat accepts both API key and session auth, rate-limited to 600 req/min.
• TimescaleDB storage: monitor_results hypertable with 7-day compression, 30-day retention, and a monitor_uptime_daily continuous aggregate refreshed hourly.
• Monitoring dashboard (/dashboard/monitoring): monitor list with project selector, create/edit/delete forms, detail page with uptime chart and recent checks, and a one-click heartbeat URL copy.

🔩 Log Parsing and Enrichment Pipelines (#153)

• 5 built-in parsers: nginx (combined log format), apache, syslog (RFC 3164 and RFC 5424), logfmt, and JSON message body.
• Custom grok patterns: %{PATTERN:field} and %{PATTERN:field:type} syntax with 22 built-in named patterns and optional type coercion (:int, :float).
• GeoIP enrichment: extract country, city, coordinates, timezone, and ISP data from any IP field using the embedded MaxMind GeoLite2 database.
• Zero ingestion latency impact: pipelines run as BullMQ background jobs after ingestion acknowledgment.
• Project-scoped vs org-wide: pipelines can target a specific project or apply across the entire organization; project-specific pipelines take priority.
• Pipeline preview: test any combination of steps against a sample log message and inspect per-step extracted fields and the final merged result before saving.
• YAML import/export: import pipeline definitions from YAML; re-importing the same pipeline for the same scope performs an upsert.
• In-memory cache: getForProject caches the resolved pipeline per project for 5 minutes, automatically invalidated on create/update/delete.
• Settings UI (/dashboard/settings/pipelines): list, enable/disable toggle, create, edit, delete, and a live step builder for adding, reordering, and configuring parser, grok, and geoip steps.

🔧 Improvements

🧭 Navigation

• Monitoring section: added to the sidebar under "Detect", alongside Alerts and Security.
• Dashboard switcher: replaces the previous single fixed entry point with a full dropdown for managing multiple dashboards.

⚡ Performance and Correctness

• Batch panel data endpoint (POST /:id/panels/data): single round-trip fetches all panel data via Promise.allSettled - individual panel errors do not fail the dashboard.
• BullMQ monitor polling: worker checks all due monitors every 30 seconds in batches of 20 concurrent checks via Promise.allSettled.
• Atomic incident dedup: consecutive-failure state machine uses a WHERE incident_id IS NULL guard to prevent duplicate incidents under concurrent checks.

🐛 Bug Fixes

• Status page slug collision: getPublicStatus now filters by status_page_public flag instead of returning the first project matching the slug, preventing cross-org data leaks.
• createMonitor atomicity: monitor and monitor_status inserts are now wrapped in db.transaction() to prevent orphaned rows on partial failure.
• Redundant DB read eliminated: processCheckResult now receives status data from the already-fetched monitor object instead of issuing a second SELECT.
• Target validation on update: the PUT endpoint validates target format against monitor type (HTTP must start with http:///https://, TCP must contain :).
• $derived.by fix: monitor detail page uptime calculation now uses $derived.by() instead of $derived(() => ...) for correct Svelte 5 reactivity.
• @const placement: replaced invalid {@const} inside <div> elements with {#if}/{:else} blocks for Svelte 5 compatibility.
• uptimePct type coercion: Postgres ROUND() returns numeric as string - status page now coerces to number before calling .toFixed().
• Default failureThreshold aligned: frontend form default corrected from 3 to 2 to match the backend default.
• Pipeline edit page redirect: navigates back to the pipeline list when the active organization is switched, preventing stale-ID errors.
• mapMonitor typed: replaced any parameter with a proper MonitorWithStatusRow interface for compile-time safety.
• Org membership check optimized: monitoring routes now use a single SELECT WHERE user_id AND organization_id query instead of fetching all user orgs and filtering in JS.

Full Changelog: v0.8.7...v0.9.0

---

This discussion was created from the release v0.9.0.