Logtide 0.7.0: Completing the Observability Stack with OTLP Metrics and Service Maps

Logtide 0.7.0: Full Observability Stack, Service Maps, and Audit Logs

Logtide 0.7.0 marks the platform’s largest release since going open-source, introducing OTLP metrics ingestion and service dependency graphs. The update bridges logs, traces, and metrics into a unified, privacy-first stack built on TimescaleDB.

Why This Matters

Many observability platforms require complex Elastic clusters or opaque pricing, but Logtide provides a GDPR-compliant, self-hostable alternative for European SMBs. By integrating OTLP metrics with exemplar support, it allows engineers to navigate directly from latency spikes to specific traces, reducing friction between siloed tools.

Key Insights

• Logtide 0.7.0 supports all five OpenTelemetry metric types including gauge, sum, and histograms via standard OTLP protocol.
• Service Maps utilize a force-directed graph built from span parent-child relationships and log co-occurrence via trace_id self-joins.
• Metrics storage utilizes TimescaleDB hypertables with 7-day chunk compression and 90-day retention policies for efficiency.
• Automated audit trails now cover log access, configuration changes, user management, and data modifications for compliance.
• The @logtide/reservoir abstraction allows switching between TimescaleDB and ClickHouse storage backends.

Working Examples

The new Metrics Query API supporting seven aggregation intervals and six functions.

GET /api/v1/metrics/names
GET /api/v1/metrics/labels/keys
GET /api/v1/metrics/labels/values
GET /api/v1/metrics/data
GET /api/v1/metrics/aggregate

Upgrade process for Logtide 0.7.0 requiring no manual schema migrations.

docker compose pull
docker compose up -d

Practical Applications

• Identifying microservice bottlenecks: Use the Service Map to visualize call chains and health states based on error rates (Red > 10%).
• Compliance reporting: Export up to 10,000 rows of audit logs as CSV for regulatory reviews of admin actions and log access.
• Data Ingestion: Use the expanded /api/v1/ingest endpoint to accept direct JSON arrays from Vector or Fluent Bit without custom transformations.

References:

• https://dev.to/polliog/logtide-070-full-observability-stack-service-maps-and-audit-logs-2ibo
• https://logtide.dev
• https://logtide.dev/docs