InfluxDB time series database services for production teams.
JusDB provides InfluxDB database services for scoped projects, ongoing remote DBA coverage, and production support. Our engineers handle schema and series cardinality, Telegraf ingestion, moves off Flux, and upgrades to InfluxDB 3. We work on InfluxDB 3 Core and Enterprise, 1.x and 2.x, InfluxDB Cloud, and Kubernetes. 24x7 on-call is available under your service agreement.
Or request a free audit of one database instance. Already in an incident? See how incidents are handled.
- NDA before access
- Read-only by default
- Changes measured against your baseline
InfluxDB version status
Pick the line you run
InfluxDB 3 Core and Enterprise 3.12
NewestReleased in October 2026. InfluxData supports the current and previous minor release for Enterprise customers, now 3.12 and 3.11.
3.12 adds a catalog record that 3.11 cannot read, so rolling back needs a catalog backup from before the upgrade.
Plan an InfluxDB 3 upgradeInfluxDB OSS 2.10
Maintenance2.10.0 shipped in October 2026. InfluxData says 1.x and 2.x are in maintenance: improvements, but no InfluxDB 3 features.
2.x tasks run Flux, and no InfluxDB 3 product officially supports Flux, so tasks are rewritten before a move.
Plan the move off FluxInfluxDB 1.13, OSS and Enterprise
MaintenanceOSS 1.13.0 shipped in July 2026, and 1.13.1 is the newest InfluxDB Enterprise release. Both are in maintenance.
InfluxDB 3 accepts 1.x writes and InfluxQL through the 1.x APIs, so most writers and queries carry over.
Plan a move from 1.xInfluxDB Cloud (TSM)
Still runningIt serves organizations created before 31 January 2023 and Google Cloud or Azure marketplace sign-ups. Newer ones run Cloud Serverless.
InfluxData's end-of-life procedure gives at least six months of notice before a product or Cloud region is removed.
Compare the InfluxDB 3 productsVersion status from the InfluxDB 3 release notes, InfluxData's product guide, The future of Flux, the end-of-life procedure, and the support policy, checked 28 October 2026.
- Platforms
- InfluxDB 3 Core and Enterprise, InfluxDB Cloud, InfluxDB Clustered on Kubernetes, and 1.x and 2.x on your own servers
- High availability
- InfluxDB 3 Enterprise clusters with read replicas, InfluxDB Enterprise 1.x clusters, and InfluxDB Clustered
- Incidents
- Initial-response targets are set in your service agreement. See the targets
Symptoms
Eight InfluxDB problems we are asked to fix
Each one has a cause we can measure. The scoping call starts from your symptom, version, and platform.
Memory climbs and writes slow after a release adds a tag because a tag holding request or user IDs creates a series per value, and 1.x and 2.x index every series.
Writes fail with max series per database exceeded once a 1.x database on the in-memory index passes one million series, the default limit. InfluxDB Cloud (TSM) returns HTTP 429 at your plan's quota.
Flux tasks and dashboards block the move to InfluxDB 3 because no InfluxDB 3 product officially supports Flux, so each one is rewritten in SQL or InfluxQL.
A week-long query fails on InfluxDB 3 Core because Core reads at most 432 Parquet files per query by default, up to 72 hours of data, and raising the limit risks running out of memory.
Backfilling old data lowers write throughput on 2.x because InfluxDB creates shards for past time ranges on demand and un-compacts cold shards to write to them.
Telegraf loses metrics while InfluxDB is down because each output buffers 10,000 metrics in memory by default, then overwrites the oldest, unless buffer_strategy is set to disk.
The operator token cannot be read back after the 2.9 upgrade because 2.9.0 hashes API tokens on first start, yet a full restore of a 2.9 backup needs that token.
A 0d retention period copied from 1.x or 2.x expires everything because InfluxDB 3 marks all data for deletion at query time, where 1.x and 2.x read 0d as infinite.
If one of these is costing your team time, a scoping call is the place to start.
Book a 30-min scoping call (opens Google Calendar in a new tab)Cardinality
How one unbounded tag stalls InfluxDB writes
On 1.x, 2.x, and InfluxDB Cloud (TSM), each unique set of measurement and tag values is a series, and the index holds every series key. A tag that changes on every point adds a series per write, until memory runs short or a limit rejects writes.
One measurement, three tag designs
Choose a state to see what happens to the series count.
What the writers send
Telegraf sends cpu metrics tagged by host and region.
Tags
host and region, with known values
Bounded
Series index
Grows with new hosts, not with traffic
Stable
Writes and queries
Filters use the index
Normal
Each unique set of measurement and tag values is one series. With bounded tags, the series count tracks your hardware, not your traffic.
What the writers send
A release adds request_id as a tag, so every point carries a new tag value.
Tags
request_id takes a new value on every point
Unbounded
Series index
Adds one series key per request
Growing
Writes and queries
Slow down, then meet a tag or series limit
Rejected
On 1.x with the default in-memory index, writes fail once request_id holds 100,000 values (max-values-per-tag) or the database holds one million series (max-series-per-database). InfluxDB Cloud (TSM) returns HTTP 429 at your plan's series quota. On 2.x OSS, memory climbs and reads and writes slow down.
What the writers send
request_id is written as a field, so new points add field values, not series.
Tags
Bounded again; IDs live in fields
Bounded
Series index
Old series stay until their data expires or is deleted
Stops growing
Alerts
Series count against the limit
Watched
Field values are not indexed, so a filter on request_id scans its time range. Existing series still count until their data expires or is deleted.
We design the schema first: tags only for bounded sets of values, and IDs, messages, and timestamps as fields. We measure with SHOW SERIES CARDINALITY or influxdb.cardinality().
We alert on series and tag value counts before they reach a limit: max-series-per-database and max-values-per-tag on the 1.x in-memory index, or your plan's series quota on InfluxDB Cloud (TSM). Where the series count grows by design, we plan a move to InfluxDB 3, whose storage engine is not limited by series cardinality.
What we cover
Full-spectrum InfluxDB engineering
From one runaway tag to a move off Flux: series counts, write errors, and EXPLAIN plans drive every change, measured against your baseline.
Schema and series cardinality
Tags and fields chosen so the series count tracks your sources, not your traffic.
- Per-tag value counts to find the tag that grows
- IDs, messages, and timestamps moved from tags to fields
- Series alerts against max-series-per-database or your Cloud quota
Telegraf-driven ingestion
Collection agents set up so a slow or unavailable database does not cost you metrics.
- metric_batch_size and metric_buffer_limit sized per output
- Disk buffering through buffer_strategy where losing metrics is not acceptable
- Agent health from the Telegraf internal input plugin
SQL + InfluxQL
Flux tasks, alerts, and dashboards rewritten before a move to InfluxDB 3, which does not support Flux.
- Inventory of Flux tasks, checks, dashboards, and client code
- Rewrites in SQL or InfluxQL, checked against the old results
- Downsampling moved to Processing Engine plugins where still needed
InfluxDB 3 Core and Enterprise
Object storage, the write-ahead log (WAL), caches, and node roles set up for your load.
- Object store, WAL flush interval, and memory pool settings
- Last value and distinct value caches for dashboards
- Ingest, query, compact, and process nodes on Enterprise
Retention and backups
Retention that deletes what you expect, and restores tested before you need one.
- Bucket retention and shard group duration on 2.x
- influx backup, influxd backup -portable, or Enterprise backups
- Restores rehearsed on a copy, operator token on record
InfluxDB Cloud and Clustered
Cloud Serverless, Cloud Dedicated, or Clustered, matched to your workload.
- Cloud Dedicated administered with the influxctl CLI
- Clustered on Kubernetes with its PostgreSQL catalog
- Moves from InfluxDB Cloud (TSM) to InfluxDB 3
Incident support
A critical (P1) page, answered within your agreement's target
JusDB keeps your recovery procedures (runbooks) written down, so an incident starts from a known plan instead of a blank page.
Initial-response targets
2 to 4 hours
Business hours
During covered business hours
15 minutes
24x7 on-call
P1 incidents
Production database down, primary unreachable, data corruption risk, or active failover event.
Severe latency spike, replication lag climbing rapidly, connection exhaustion, or degraded HA node.
Non-critical slow query regression, staging issue, backup warning, or replication check alert.
Configuration question, index advisory, planned schema review, or general operational request.
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.
What happens on a P1 page
Page
You page the on-call engineer
Through the escalation path your service agreement names.
Triage
Root cause from series counts, metrics, and the query log
Rejected writes, memory growth, slow dashboards, and Telegraf drops traced to the tag, query, or writer behind them.
Mitigate
Stabilize first, from the runbook
Stop or roll back the writer that adds series, pause heavy tasks, or shed query load, then fix the cause once production is steady.
After
A review after every P1
What happened, why, and the change that stops it happening again.
Before and between incidents
- Your setup, written down firstDuring onboarding we record your products, versions, retention, Telegraf agents, and backups, so an incident starts with context.
- One escalation path, in writingYour service agreement names how to reach the on-call engineer, in which hours, and who approves stopping a writer.
- Reviews between incidentsWe review series counts, write errors, query load, storage use, and backups, and report open risks.
- Version dates trackedWe track InfluxDB 3 releases and InfluxDB Cloud end-of-life notices for what you run, and plan upgrades early.
Process
How an InfluxDB engagement runs, step by step
Written findings come before any change. Your team approves production changes, except routine actions you have pre-approved.
Scoping call
Your InfluxDB products, versions, data volumes, Telegraf agents, and what you need covered.
Read-only review under NDA
Our engineers use read-only users or tokens where your version offers them, then read your configuration, series counts, retention, Flux tasks, and Telegraf setup.
A written report before any change
Each finding comes with the change we propose, how we will measure it, and a way to undo it (a rollback plan).
Changes, then handover
We rehearse risky changes on a copy, apply them in the windows you approve, measure them against the baseline, and hand over updated operating instructions (runbooks).
Step one is a 30-minute scoping call.
Book a 30-min scoping call (opens Google Calendar in a new tab)Ways to work
Choose the InfluxDB service your team needs
Start with the responsibility you need covered. Each engagement has its own scope, deliverables, access requirements, and acceptance criteria.
Projects
Scoped InfluxDB projects
A defined piece of work with written findings, hands-on changes, and validation against your baseline.
- InfluxDB consultingProduct choice, schema, and cardinality decisions, scoped as one project.
- Performance tuningSeries cardinality, ingestion, slow queries, and retention, measured before and after.
- Migration and upgradesMoves to InfluxDB 3 from 1.x, 2.x, or Cloud (TSM), with a rollback plan.
- Backup and recoveryBackups for each InfluxDB version, with restores tested on a copy.
Ongoing
Ongoing coverage and support
JusDB monitors the databases, carries out the agreed maintenance, and responds to incidents during the coverage the proposal names. The team keeps a change record, recovery procedures, and a review after every P1.
Where your InfluxDB runs, and the tools around it
Your team and ours
What a managed InfluxDB service still leaves to your team
Managed cloud databases automate much of the infrastructure layer, but your team still owns query performance, capacity, cost, and incident decisions.
| Question | InfluxDB Cloud | Your own servers or Kubernetes |
|---|---|---|
| Servers, storage, and upgrades | InfluxData runs them. | Your team, or JusDB under your agreement. |
| Backups and restores | InfluxData runs them on Cloud Serverless and Cloud Dedicated; Dedicated keeps a daily catalog backup for at least 30 days. | Your team runs the backup procedure for its version and tests restores. |
| Schema and series cardinality | Yours. On InfluxDB Cloud (TSM), writes past your plan's series quota get HTTP 429. | Yours. On the 1.x in-memory index, writes past max-series-per-database fail. |
| Query languages | SQL and InfluxQL on Cloud Serverless and Cloud Dedicated. Flux is not officially supported there. | SQL and InfluxQL on InfluxDB 3, and Flux and InfluxQL on 1.x and 2.x. |
| Versions and end of life | InfluxData's calendar, with at least six months of notice before a product or region is removed. | Your calendar. 1.x and 2.x are in maintenance; InfluxDB 3 shipped four minor releases in 2026. |
Your team keeps control
- Set business priorities, application requirements, and release plans
- Approve production changes, except routine actions you have pre-approved
- Own your cloud accounts, access policies, and vendor relationships
- Decide when maintenance can happen and how quickly service must recover
- Move the work in-house or to another provider after your agreement's notice period, with your data returned or deleted and the transition help your agreement sets out (Terms, section 8)
JusDB handles the agreed database work
- Monitor database health, investigate alerts, and involve the right people
- Review query performance, replication, capacity, and backup health
- Carry out approved changes and update the operating instructions they affect
- Report completed work, open risks, and recommended next steps
Weighing InfluxDB Cloud against running InfluxDB yourself? We compare both against your workload on a scoping call.
Book a 30-min scoping call (opens Google Calendar in a new tab)Further reading
Monitoring guides and a comparison
Our TimescaleDB and InfluxDB comparison, and two guides on collecting and alerting on database metrics.
Comparison
TimescaleDB vs InfluxDB
A PostgreSQL extension against a database built only for time series, and when each fits.
Guide
Database observability: metrics, logs, and traces
Counters, rates, and resets, secure exporters, traces, and alerts built around symptoms.
Guide
Database monitoring with Prometheus, Grafana, and PMM
Exporters, Grafana dashboards, Percona Monitoring and Management (PMM), and the alerts to set first.
FAQ
Common InfluxDB questions
What buyers ask about fit, TimescaleDB, InfluxDB 3, Telegraf, Cloud tiers, and licensing.
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)What is InfluxDB and what workloads does it fit?
JusDB works with InfluxDB for time series and event data that arrives continuously and is queried by time. Typical uses are server, application, sensor, and network monitoring, where dashboards and alerts need fast answers about recent data.
InfluxDB vs TimescaleDB: when does InfluxDB win?
JusDB recommends InfluxDB when data arrives through Telegraf or line protocol at high volume, and the team wants a database built only for time series. TimescaleDB, a PostgreSQL extension, fits better when time series must join relational tables.
What changed in InfluxDB 3.x?
JusDB treats InfluxDB 3 as a new database: a rewrite in Rust on Apache Arrow and DataFusion that keeps data in object storage instead of TSM files. It answers SQL and InfluxQL, has no official Flux support, and accepts 1.x and 2.x writes. Core is the free, single-node release; Enterprise adds compaction, high availability, read replicas, and multi-node clusters.
Telegraf: what role does it play?
JusDB uses Telegraf, InfluxData's collection agent, in front of InfluxDB. Each output buffers up to 10,000 unwritten metrics in memory by default and overwrites the oldest once full, so we size that buffer and turn on disk buffering where losing metrics is not acceptable.
InfluxDB Cloud Serverless vs Dedicated: which fits?
JusDB matches the tier to the workload. Cloud Serverless is multi-tenant and billed by usage, runs on AWS in US East and EU Frankfurt, and has no Processing Engine. Cloud Dedicated is a single-tenant cluster that InfluxData runs for you, and it supports AWS PrivateLink and Azure Private Link. For self-managed production, InfluxData recommends InfluxDB 3 Enterprise.
What licensing applies to InfluxDB?
JusDB checks the license of each InfluxDB product before planning a deployment. InfluxDB 3 Core is open source under the MIT or Apache 2.0 license, at your choice, and OSS 1.x and 2.x use MIT. InfluxDB 3 Enterprise needs a license per cluster: trial, at-home, or commercial, each with a CPU core limit.
Next step
Talk to an InfluxDB engineer about your databases
Tell us what is slow, fragile, or due to change. 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, and written scope first
Compare with other databases
If you are weighing alternatives, these are the databases most often compared with this one.
TimescaleDB
A PostgreSQL extension for time series. Teams compare it with InfluxDB when time-stamped data must join relational tables in PostgreSQL.
ClickHouse
A columnar database used for metrics, logs, and events at high ingest rates, compared with InfluxDB for large-scale time-series analytics.
Apache Druid
A real-time analytics database for streaming event data, compared with InfluxDB when many users run aggregations over the same streams.
PostgreSQL
Plain PostgreSQL tables with time-based partitions and BRIN indexes handle modest time-series volumes before a dedicated engine is needed.