Skip to content

Upgrading to 2.0.0

This page covers what you need to know when upgrading to Quine 2.0.0.

What's New

  • Redesigned Exploration UI with a new Dashboard and Streams page
  • API v2 is now the default — API v1 endpoints remain available but are planned for removal
  • Recipe schema v2 with API v2 entities
  • Docker base image updated to eclipse-temurin:21.0.10_7-jre-noble (Ubuntu 24.04 LTS)
  • All-node scan queries now filter server-side for better performance
  • Content Security Policy headers added by default
  • Credential redaction in API responses

Breaking Changes

Metrics Prefix Changes

All graph-scoped metrics (shard, node, standing query, and ingest) are now prefixed with quine.. For example, node.property-counts becomes quine.node.property-counts and ingest.my-stream.count becomes quine.ingest.my-stream.count.

Update your monitoring infrastructure (Grafana dashboards, InfluxDB queries, alerting rules) to include the quine. prefix for all graph-scoped metrics. Global metrics (persistor, shared valve) remain unchanged.

Updating Grafana Queries

The exact syntax depends on your metrics reporter.

InfluxDB example:

-- Previous query
SELECT mean("value") FROM "node_property_counts" WHERE $timeFilter

-- 2.0.0+ query
SELECT mean("value") FROM "quine_node_property_counts" WHERE $timeFilter

Prometheus example:

# Previous query
rate(node_property_counts[5m])

# 2.0.0+ query
rate(quine_node_property_counts[5m])

API v1 Deprecation

API v2 is now the default for all installations. API v1 remains available but is planned for deprecation and will be removed in a future release.

See Migrating from API v1 for the complete migration guide, including endpoint mappings, design changes, and a migration checklist.

Recipe Schema v1 Deprecation

Recipes now support schema version 2, which uses API v2 entities. Version 1 recipes continue to work but should be migrated.

See Migrating from v1 Recipes for migration steps and a before/after example.