Free audit

View Audit Scope
Time-Series Upgrades & Cutoversv1/v2 to 3.0 IOx · Flux-to-SQL Rewrites · TimescaleDB & ClickHouse

InfluxDB Migration & 3.0 IOx / Cross-Engine Cutover Services

JusDB plans and executes production InfluxDB migrations with verified time-bucket parity and reversible Telegraf dual-write cutovers. We migrate InfluxDB 1.x and 2.x (TSM/TSI) deployments onto InfluxDB 3.0 IOx (Apache Arrow, DataFusion SQL, and S3 Parquet), translate deprecated Flux dashboards and tasks into InfluxQL and SQL, and execute cross-engine migrations between InfluxDB, TimescaleDB, and ClickHouse.

The first 30-minute call covers your databases, current ownership, and required coverage. No production access is needed. Or request a free audit of one database instance.

  • NDA before access
  • Read-only by default
  • Verified time-bucket parity & rollback gates

InfluxDB migration & upgrade paths

Select a migration path

TSM/TSI to InfluxDB 3.0 IOx (Apache Arrow / Parquet)

Columnar engine jump

InfluxDB 3.0 replaces TSM shard files and TSI indexes with Apache Arrow in-memory buffers, DataFusion SQL/InfluxQL, and S3/GCS Parquet persistence.

Line Protocol writes remain backwards-compatible, while historical `.tsm` files are exported and bulk-converted into partitioned IOx Parquet tables.

Inspect InfluxDB cutover simulator

TSM export utilities, DBRP mappings, and IOx SQL verified against InfluxData Upgrade & Migration documentation.

Migration paths covered
InfluxDB 1.x/2.x to 3.0 IOx, OSS to Enterprise/Cloud, and InfluxDB to TimescaleDB or ClickHouse
Backfill & query translation
Offline influx_inspect export, Telegraf dual-write, and Flux-to-InfluxQL/SQL rewrites
Initial-response targets
15 minutes for a critical (P1) incident under a 24x7 support agreement; 2 to 4 hours in business hours. See details
Coverage hours
Business hours (03:30–12:30 UTC) by default; 24x7 cutover support available under your service agreement

Selected clients

  • Innoviti
  • Blitz
  • Freecharge
  • Nango
  • Recochain
  • Screen Facts
  • Nexora
  • WeCredit

Migration failure modes

Common InfluxDB upgrade and cross-engine migration blockers we solve

Time-series migrations stall when deprecated Flux scripts fail on v3 IOx, live HTTP exports crash `influxd`, or dynamic field type conflicts break SQL table loads.

InfluxDB migration blockers, root causes, and engineering remediation
Upgrade / migration signalWhat is usually happeningWhere we start
Flux Engine RemovedGrafana dashboards and v2 tasks break when moving to InfluxDB 3.0InfluxDB 3.0 (IOx) standardizes on Apache DataFusion SQL and InfluxQL; Flux queries and built-in `option task = { ... }` downsampling scripts have no native v3 runtime.Export all Grafana dashboard JSONs and v2 task definitions, translate Flux pipelines into FlightSQL or InfluxQL, and move scheduled roll-ups to Telegraf, FlightSQL scripts, or Kubernetes CronJobs.
TSM Export OOM / I/OExporting terabytes of historical TSM shards crashes live influxdRunning unthrottled `SELECT *` queries against a live InfluxDB 1.x/2.x node to extract historical data exhausts Go heap and disk read IOPS.Run `influx_inspect export` (or `influxd inspect export-lp`) directly against cold TSM shard files or a snapshot clone, streaming compressed Line Protocol or Parquet in time-bounded chunks.
Tag-to-Column SchemaMigrating schemaless Line Protocol into TimescaleDB or ClickHouse fails on typesInfluxDB allows dynamic field additions and mixed float/integer field types across shards, whereas TimescaleDB hypertables and ClickHouse MergeTree require explicit column types.Audit field type conflicts across all TSM shards (`SHOW FIELD KEYS`), design normalized or wide-table DDL with ZSTD/Gorilla compression, and sanitize types in Telegraf before dual-writing.
v1 DBRP Mapping MissingLegacy InfluxQL 1.x clients receive 404 Not Found after upgrading to 2.x/3.0InfluxDB 1.x queries address `database` + `retention_policy`, while InfluxDB 2.x maps data into `bucket` IDs unless explicit DBRP (Database Retention Policy) mappings exist.Create explicit `influx v1 dbrp create` mappings and v1 compatibility auth tokens so legacy Telegraf agents and Grafana InfluxQL data sources work without code changes.
IOx Partition BloatMigrated InfluxDB 3.0 table scans slowly despite moving to ParquetHistorical data was bulk-loaded into InfluxDB 3.0 using default daily partitions without aligning partition templates to primary query filter tags.Define custom IOx table partition templates (e.g., `tenant_id` + `YYYY-MM-DD`) before historical backfill so Apache DataFusion prunes Parquet files at query time.
Downsampling DriftHistorical roll-up buckets show different averages after cutoverWindow boundary alignment (`aggregateWindow` vs `GROUP BY time()` vs `time_bucket()`) or empty-bucket fill semantics (`fill(none)` vs `fill(previous)`) differ between engines.Align UTC window boundaries and NULL/fill handling across source and target roll-up queries, and verify hourly aggregate checksums before retiring the source.

Technical scope

What our InfluxDB migration engagement includes

From Flux-to-SQL query translation and tag cardinality cleanup to offline TSM shard extraction, Telegraf dual-writing, and automated time-bucket parity verification.

  • Pre-migration cardinality, Flux & schema inventory

    We audit your measurements, tag/field schemas, shard sizes, Flux scripts, Continuous Queries, and Grafana dashboards before moving any data.

    • Inventory all Flux queries, v2 Tasks, and v1 Continuous Queries across your estate
    • Detect cross-shard field type conflicts and runaway tag cardinality via reporttsi

    influx_inspect reporttsi · SHOW FIELD KEYS · Grafana JSON audit · DBRP check

    InfluxDB consulting
  • InfluxDB 1.x / 2.x to InfluxDB 3.0 IOx migration

    Upgrade from legacy TSM/TSI storage to InfluxDB 3.0 (Cloud Dedicated, Serverless, Clustered, or Core/Enterprise) backed by Apache Arrow and Parquet.

    • Design IOx Parquet partition templates and sort keys matched to your queries
    • Configure v1/v2 Line Protocol write compatibility and FlightSQL/InfluxQL endpoints

    InfluxDB 3.0 IOx · Apache Arrow FlightSQL · Parquet partition templates

  • Flux-to-InfluxQL & SQL query and task translation

    Eliminate the biggest blocker to InfluxDB 3.0 and cross-engine migrations by systematically translating Flux pipelines into SQL or InfluxQL.

    • Rewrite Flux pivot(), join(), and aggregateWindow() into DataFusion SQL or InfluxQL
    • Replace v2 Flux tasks with SQL downsampling jobs, Telegraf aggregators, or CronJobs

    Apache DataFusion SQL · InfluxQL ·Timescale continuous aggregates · Grafana

    InfluxDB performance tuning
  • Cross-engine migrations (TimescaleDB & ClickHouse)

    When relational SQL joins, open-source clustering, or petabyte analytical compression is required, we migrate InfluxDB workloads to TimescaleDB or ClickHouse.

    • Map measurements and tags into TimescaleDB hypertables or ClickHouse MergeTree
    • Configure Telegraf `outputs.postgresql` / `outputs.clickhouse` or Vector pipelines

    TimescaleDB Hypertables · ClickHouse MergeTree · Telegraf / Vector dual-sink

  • Offline TSM shard export & bulk historical backfill

    Extract terabytes of historical TSM data without impacting your live production InfluxDB instance.

    • Run `influx_inspect export` / `export-lp` on filesystem snapshots in time chunks
    • Convert Line Protocol dumps to Parquet or bulk-load into v3 IOx / Timescale / ClickHouse

    influx_inspect export · influxd inspect export-lp · gzip Line Protocol · Parquet

  • Telegraf dual-writing & time-bucket parity gates

    Stream live metrics to both source and target clusters simultaneously and verify exact aggregate parity before flipping Grafana and API readers.

    • Dual-sink Telegraf or Kafka buffer pipelines with independent retry queues
    • Automated hourly COUNT, MIN, MAX, and MEAN parity checks across measurements

    Telegraf dual outputs · Kafka replay buffer · SQL/InfluxQL parity runner

Shared responsibility & response targets

How JusDB InfluxDB migration engineering compares with basic export scripts

Simple Line Protocol dumps carry over cardinality bloat, fail on cross-shard field type conflicts, and leave Flux dashboards broken.

Comparison between basic Line Protocol dumps and JusDB InfluxDB migration engineering
Migration phaseBasic dump / lift-and-shiftWhat JusDB engineers & verifies
Historical TSM data extractionQueries the live production HTTP API for months of raw points, triggering OOM kills on `influxd`.Extracts compressed Line Protocol directly from snapshot `.tsm` and `.wal` files using offline `influx_inspect export`.
Deprecated Flux dashboards & tasksAutomated data copy tools move raw points but leave hundreds of broken Flux dashboards and v2 tasks behind.Rewrites Flux queries into verified InfluxQL or SQL (FlightSQL / PostgreSQL / ClickHouse) and migrates roll-up tasks.
Cardinality & tag debtCopies years of polluted high-cardinality tags verbatim into the new database.Sanitizes tag vs field schemas during the migration and designs optimal IOx Parquet partitions or hypertable indexes.
Field type conflicts across shardsBulk loads fail mid-way when an older shard stored a field as integer and a newer shard stored it as float.Audits `SHOW FIELD KEYS` across all shards up front and normalizes numeric/string casts in the export pipeline.
Live ingestion continuityStops Telegraf writers during a multi-hour dump-and-restore window, creating gaps in operational charts.Configures Telegraf or Kafka dual-writing before starting the historical backfill so zero time windows are missed.
Cutover verification & rollbackSwitches Grafana data sources after visual spot checks with no automated metric validation.Verifies hourly min/max/mean/count parity across source and target and keeps dual-writes active for instant rollback.

Published initial-response targets by severity

Standard business hours: 03:30–12:30 UTC

Initial-response targets are 2 to 4 hours during covered business hours, Mon–Fri 09:00–18:00 IST (UTC+5:30). Where your service agreement includes 24x7 on-call, the initial-response target for P1 incidents is 15 minutes. Targets are not resolution guarantees.

SeverityInitial responseDefinitionChannel & coverage
P1 · Critical15 minutesProduction database down, primary unreachable, data corruption risk, or active failover event.24x7 on-call (under your service agreement) · Direct PagerDuty, Opsgenie, or phone page plus incident bridge
P2 · High30 minutesSevere latency spike, replication lag climbing rapidly, connection exhaustion, or degraded HA node.24x7 on-call (under your service agreement) · On-call alert plus shared Slack or Teams channel
P3 · Medium60 minutesNon-critical slow query regression, staging issue, backup warning, or replication check alert.24x7 on-call (under your service agreement) · Shared Slack or Teams channel or support ticket
P4 · Low90 minutesConfiguration question, index advisory, planned schema review, or general operational request.24x7 on-call (under your service agreement) · Shared Slack or Teams channel or support ticket

Our engineering team is in India; business-hours coverage is Mon–Fri 09:00–18:00 IST (UTC+5:30), and 24x7 on-call is available under your service agreement.

Initial-response targets, not resolution guarantees. The target for your engagement is set in your service agreement.

Interactive migration simulator

How Telegraf dual-writing and snapshot exports cut over cleanly

Step through Telegraf dual-writing with offline TSM snapshot extraction, Flux-to-SQL parity validation, and reversible Grafana cutover.

InfluxDB Blue/Green migration & cutover simulator

Select a migration stage to inspect Telegraf dual-write routing, offline TSM backfill, and dashboard validation.

Telegraf Collectors, Backfill Pipeline & Grafana Readers

Grafana and alerting stay on the source InfluxDB 1.x/2.x instance; Telegraf dual-writes live Line Protocol to both clusters while `influx_inspect export` streams historical snapshots.

Source serving dashboards · Target dual-ingesting + backfilling
  • Blue Source (InfluxDB 1.x / 2.x TSM)

    Serving active Grafana dashboards & alerts

    ONLINE · Zero extra query load (export runs on snapshot)

  • Telegraf Aggregator / Edge Fleet

    Dual-writing sanitized Line Protocol to Blue & Green

    DUAL-WRITING · Independent disk/Kafka retry buffers

  • Green Target (InfluxDB 3.0 IOx / Timescale / CH)

    Ingesting live stream + historical chunk backfill

    BACKFILLING · Parquet / Hypertable partitions building

By starting Telegraf dual-writing at timestamp `T0` and running `influx_inspect export -end T0` against an EBS/ZFS disk snapshot of the source data directory, we backfill terabytes of history with zero read impact on production.

Representative production deliverable

How an InfluxDB 2.x to 3.0 IOx cutover and Flux-to-SQL rewrite is executed

Every migration runbook includes offline `export-lp` commands, Telegraf dual-write configs, and verified Flux-to-SQL query translations.

Sample deliverable · InfluxDB 2.7 TSM to InfluxDB 3.0 IOx with Flux-to-SQL rewrite9.4 TB TSM → 2.1 TB S3 Parquet · 140 Dashboards

Migration outcome

Migrated 9.4 TB of high-cardinality IoT telemetry to InfluxDB 3.0 IOx and rewrote 140 Flux dashboards to SQL

An energy telemetry platform hit TSI series cardinality ceilings at 11M series on InfluxDB 2.7. We enabled Telegraf dual-writing to InfluxDB 3.0 IOx, exported historical TSM shards from an EBS snapshot via influxd inspect export-lp, and translated 140 Grafana Flux panels into Apache DataFusion SQL over FlightSQL.

Compressed storage size9.4 TB → 2.1 TB
30-day Dashboard p996,400ms → 95ms

1. Offline TSM snapshot export bounded to Dual-Write cutover timestamp T0

cli · offline influxd inspect export-lp & telegraf dual-write

# 1. Export compressed Line Protocol from mounted EBS snapshot up to T0
influxd inspect export-lp \
  --bucket-id 8a91f02b4c109e33 \
  --engine-path /mnt/snapshot/influxdb2/engine \
  --end 2026-11-01T00:00:00Z \
  --compress \
  --output-path /mnt/export/grid_telemetry_pre_t0.lp.gz

# 2. Telegraf dual-write configuration to InfluxDB 2.x (Blue) & InfluxDB 3.0 IOx (Green)
[[outputs.influxdb_v2]]
  urls = ["https://influx2-blue.internal:8086"]
  token = "${INFLUX_BLUE_TOKEN}"
  bucket = "grid_telemetry"
  content_encoding = "gzip"

[[outputs.influxdb_v2]]
  urls = ["https://influx3-green.internal:8086"]
  token = "${INFLUX_GREEN_TOKEN}"
  bucket = "grid_telemetry"
  content_encoding = "gzip"

2. Flux window + pivot query translated to InfluxDB 3.0 DataFusion SQL

influxdb 3.0 sql (flightsql) · dashboard query translation

SELECT
  DATE_BIN(INTERVAL '5 minutes', time, TIMESTAMP '1970-01-01T00:00:00Z') AS window_5m,
  substation_id,
  AVG(voltage_kv) AS avg_voltage_kv,
  MAX(current_amps) AS peak_current_amps
FROM grid_telemetry
WHERE time >= now() - INTERVAL '30 days'
  AND region = 'ercot-north'
GROUP BY 1, 2
ORDER BY window_5m ASC;

Ways to work together

How to engage JusDB for an InfluxDB migration

Start with a read-only migration and Flux query assessment, commission a turnkey v3 IOx or TimescaleDB/ClickHouse cutover, or retain post-migration SRE support.

Turnkey migration projectThis page

Rehearsed cutover with parity verification.

Fixed-scope execution covering target cluster buildout, Flux-to-SQL rewrites, Telegraf dual-writing, offline TSM backfill, and time-bucket parity checks.

Migration paths we execute end-to-end

  • InfluxDB 1.x/2.x to 3.0 IOx
  • Flux to InfluxQL & FlightSQL
  • InfluxDB to TimescaleDB
  • InfluxDB to ClickHouse
  • OSS to / from Enterprise / Cloud
Free migration assessment

Cardinality, Flux & target fit audited.

We inspect your TSI cardinality, shard volume, field type conflicts, and Flux dashboard count, returning a written v3 IOx vs TimescaleDB vs ClickHouse comparison.

What we check before you migrate

  • Flux query & v2 Task count for SQL/InfluxQL translation
  • Cross-shard field type conflicts & tag cardinality debt
  • Offline TSM export size & Telegraf dual-write readiness
Post-cutover SRE & support

Keep the new time-series store fast.

Ongoing Prometheus monitoring, partition and retention care, backup drills, and incident response under a 24x7 support agreement or in covered business hours.

  1. Burn-in watchavailable where your service agreement includes it
  2. 15 minP1 initial-response target
  3. Rollback gateTelegraf dual-write active
Evaluation Vector
JusDB DBRE
In-House DBALegacy AgencyDeveloper Generalist
Generational Migration Architecture (1.x/2.x to 3.x)Architects modern InfluxDB 3.x environments, mapping legacy buckets, retention policies, and continuous queries to Apache Arrow tables, partitions, and scheduled SQL jobs.Attempts in-place binary upgrades without accounting for complete storage-engine replacement (TSM to Parquet), resulting in unbootable clusters.Advises abandoning InfluxDB entirely due to 3.x architectural changes rather than leveraging Arrow/DataFusion performance gains.Treats 3.x as a minor patch release, ignoring the removal of Flux and breaking production dashboard integrations.
Flux to SQL / InfluxQL Query TranspilationAudits production Flux pipelines, converts windowing and math transformations into optimized SQL / InfluxQL equivalents, and provides external Flink pipelines for complex streaming logic.Attempts line-by-line manual query rewrites, struggling with Flux pipe syntax differences and producing unindexed SQL table scans.Delays migration indefinitely because existing BI dashboards rely heavily on deprecated Flux scripts.Replaces Flux transformations with client-side Python scripts, degrading dashboard load times from 200ms to 15 seconds.
Streaming Dual-Writing & Telegraf Dual-Output RoutingConfigures dual-output routing in Telegraf with local disk buffering, enabling simultaneous ingestion into legacy and target clusters without dropping metrics during target maintenance.Configures applications to dual-write via raw HTTP without backpressure buffering, dropping writes during target cluster maintenance.Demands multi-hour planned downtime maintenance windows to stop all ingestion during historical migration.Switches DNS records immediately before historical data backfill is complete, creating fractured time-series gaps.
Historical TSM to Parquet Columnar ConversionOrchestrates high-throughput parallel TSM extraction, converting multi-terabyte historical shards into partitioned Parquet files for direct ingestion into cloud object stores.Uses single-threaded influx backup tools that saturate production disk IOPS and take weeks to export historical datasets.Dumps raw CSV line protocol files onto local drives, exhausting disk space and dropping precision on 64-bit nanosecond timestamps.Attempts bulk INSERT statements over client HTTP connections, hitting 413 payload limits and timing out repeatedly.
Time-Bucket Aggregation Parity ChecksummingExecutes automated time-bucket checksum reconciliation, verifying numerical sum, count, and quantile parity across legacy and target clusters before cutover.Performs surface-level row count checks that overlook timestamp drift, floating-point rounding errors, and null value coercion.Spot-checks single Grafana graphs visually without auditing underlying raw metric aggregates.Deploys target cluster without reconciliation testing, discovering missing historical metrics only after user complaints.
Rehearsed Cutover & Rollback SafetiesExecutes rehearsed cutover sequence with live shadow traffic, automated health gates, and a rehearsed DNS rollback to protect data and keep dashboards available through the switch.Executes live cutover during business hours without rollback procedures, causing multi-hour alerting outages when target configs fail.Lacks formal cutover staging runbooks, improvising routing changes during live operational incidents.Decommissions legacy cluster immediately following cutover, leaving no recourse if target InfluxDB 3.x cluster encounters query errors.

Source and target time-series platforms we migrate between

For procurement and platform security teams

Mutual NDA first, offline snapshot safety, and written cutover gates

We execute InfluxDB migrations inside your VPC and security boundary. Historical exports run on isolated disk snapshots so live production writers and readers are never impacted.Raguraman, Engineering Manager · Allen D, Lead Database SRE
  • Mutual NDA
  • Written migration plan
  • Named engineers
  • Least-privilege access
  • NDA before access

    Signed before any schema or dashboard review. The initial scoping call requires no credentials.

  • Written cutover runbook

    Snapshot export steps, dual-write config, parity gates, and rollback triggers agreed in writing.

  • Least-privilege access

    Read-only source audit access; scoped export and target write tokens via your bastion or VPN.

  • Queries & scripts you keep

    All translated SQL/InfluxQL dashboards, Telegraf configs, and parity scripts stay in your repository. Meet the JusDB team.

JusDB's security practices are aligned with ISO 27001 and SOC 2 Type II, and JusDB is pursuing both certifications (see Terms, section 12). Read the stated status.

Technical FAQ

InfluxDB migration & 3.0 IOx common questions

Answers on InfluxDB 1.x/2.x to 3.0 IOx upgrades, Flux-to-SQL translation, InfluxDB vs TimescaleDB vs ClickHouse, offline TSM snapshot exports, and field type conflicts.

Still have a question?

Ask it on a scoping call. No production access needed.

Book a 30-min scoping call (opens Google Calendar in a new tab)

How do you migrate from InfluxDB 1.x or 2.x to InfluxDB 3.0 (IOx) without data loss?

Because InfluxDB 3.0 IOx supports the v1 and v2 Line Protocol write APIs natively, we first configure your Telegraf agents (or Kafka consumers) to dual-write live metrics to both your existing InfluxDB 1.x/2.x instance and the new InfluxDB 3.0 cluster from timestamp `T0`. Next, we take a disk snapshot of the source `/engine/data` directory and run `influx_inspect export` (or `influxd inspect export-lp`) up to `T0`, bulk-loading the historical data into InfluxDB 3.0 with custom Parquet partition templates.

What happens to our Flux queries and v2 Tasks when we upgrade to InfluxDB 3.0?

InfluxDB 3.0 (IOx) removes the Flux query engine in favor of Apache DataFusion SQL and native InfluxQL. Before cutting over, we audit all your Grafana dashboard JSONs, application queries, and v2 Flux tasks. We translate your queries into fast InfluxQL or SQL (via FlightSQL / HTTP API) and migrate scheduled downsampling tasks to SQL-based roll-up scripts, Telegraf aggregators, or Kubernetes CronJobs.

Should we migrate from InfluxDB 2.x to InfluxDB 3.0, TimescaleDB, or ClickHouse?

Each target has clear strengths: **InfluxDB 3.0 IOx** keeps full Line Protocol and InfluxQL compatibility while eliminating TSI series cardinality limits via Apache Arrow/Parquet. **TimescaleDB** gives you full relational PostgreSQL SQL, foreign-key joins with metadata tables, continuous aggregates, and open-source self-hosting. **ClickHouse** delivers unmatched columnar compression (often 10x-20x) and sub-second analytical scans across hundreds of billions of wide observability events. We help you benchmark your actual queries on each before choosing.

How do you extract terabytes of historical data from InfluxDB without crashing the live server?

Never run large `SELECT *` HTTP queries against a live production InfluxDB node to export history - that saturates Go heap and disk I/O. Instead, we take an EBS/PD snapshot or portable backup, mount it on an isolated worker node, and run `influx_inspect export -compress` (v1) or `influxd inspect export-lp` (v2) directly against the underlying `.tsm` and `.wal` files in time-bounded windows.

How do you handle InfluxDB field type conflicts when migrating to SQL databases?

InfluxDB allows a field to be stored as a float in one shard and an integer or string in another shard (`field type conflict`), whereas SQL engines like InfluxDB 3.0 IOx, TimescaleDB, and ClickHouse enforce a single column type across the table. We run a pre-migration schema audit (`SHOW FIELD KEYS` across shards) and normalize conflicting numeric or string types during the export and Telegraf dual-write stages.

Can you migrate between InfluxDB OSS, InfluxDB Enterprise, and InfluxDB Cloud?

Yes. We migrate single-node InfluxDB OSS instances into 3-meta + N-data InfluxDB Enterprise HA clusters or InfluxDB Cloud (Serverless / Dedicated), and we also repatriate high-cost cloud deployments back onto self-managed NVMe instances or Kubernetes.

How do you verify that historical and live metrics match after the migration?

We run automated time-bucket parity checks comparing hourly and daily `COUNT`, `MIN`, `MAX`, and `MEAN` values per measurement and tag group between the source and target databases. Only after historical backfills, downsampled roll-ups, and live dual-written buckets match do we switch Grafana and application readers.

What are your initial-response targets during an InfluxDB migration cutover?

Initial-response targets are 2 to 4 hours during covered business hours, Mon–Fri 09:00–18:00 IST (UTC+5:30). Where your service agreement includes 24x7 on-call, the initial-response target for P1 incidents is 15 minutes. Targets are not resolution guarantees.

Next step

Talk to an engineer about your InfluxDB migration or 3.0 upgrade

Tell us your current InfluxDB version, data volume, Flux dashboard count, and target engine. The first 30-minute call covers your databases, current ownership, and required coverage. No production access is needed. Or request a free audit of one database instance, subject to availability: mutual NDA before read-only access, a prioritized report within one week after access is ready, and no obligation.

NDA before access · read-only by default · written scope first