arc-tsdb-client
Python SDK for Arc time-series database.
Installation
pip install arc-tsdb-client
# With pandas support
pip install arc-tsdb-client[pandas]
# With polars support
pip install arc-tsdb-client[polars]
# With all optional dependencies
pip install arc-tsdb-client[all]
Or with uv:
uv add arc-tsdb-client
uv add arc-tsdb-client --extra pandas
uv add arc-tsdb-client --extra all
This README documents arc-tsdb-client 0.2.0. Earlier releases lack many of the
APIs below.
Quick Start
from arc_client import ArcClient
with ArcClient(host="localhost", token="your-token") as client:
# Write data (columnar format - fastest)
client.write.write_columnar(
measurement="cpu",
columns={
"time": [1633024800000000, 1633024801000000],
"host": ["server01", "server01"],
"usage_idle": [95.0, 94.5],
},
)
# Query to pandas DataFrame
df = client.query.query_pandas("SELECT * FROM cpu WHERE host = 'server01'")
print(df)
Features
- High-performance ingestion: MessagePack columnar format (9M+ records/sec)
- Multiple formats: MessagePack columnar/row, InfluxDB Line Protocol, TLE
- Compression: gzip and zstd (zstd is the default and recommended codec)
- DataFrame integration: Pandas, Polars, PyArrow
- Sync and async APIs: Full async support with httpx
- Buffered writes: Automatic batching with a background flush timer
- Automatic retries: Exponential backoff for connection errors, 429, and 503
- Query support: SQL queries with JSON, Arrow IPC streaming, or MessagePack
- Bulk import: CSV, Parquet, line-protocol files, and TLE files
- Databases: List, create, delete databases and list measurements
- Management: Retention policies, continuous queries, delete operations
- Enterprise: RBAC, query governance, audit logs, query management, cluster, compaction, scheduler controls, storage tiering, backup/restore, and MQTT ingestion
- Authentication: Token management (create, rotate, revoke)
Data Ingestion
Columnar Format (Recommended)
The fastest way to write data. Uses MessagePack with zstd compression by default (the server recommends zstd; gzip and no compression are also supported — see Configuration):
client.write.write_columnar(
measurement="cpu",
columns={
"time": [1633024800000000, 1633024801000000], # microseconds
"host": ["server01", "server02"],
"region": ["us-east", "us-west"],
"usage_idle": [95.0, 87.3],
"usage_system": [3.2, 8.1],
},
database="default", # optional
)
DataFrame Ingestion
Write directly from pandas or polars DataFrames:
import pandas as pd
df = pd.DataFrame({
"time": pd.to_datetime(["2024-01-01", "2024-01-02"]),
"host": ["server01", "server02"],
"value": [42.0, 43.5],
})
client.write.write_dataframe(
df,
measurement="metrics",
time_column="time",
tag_columns=["host"],
)
Buffered Writes
For high-throughput scenarios, use buffered writes with automatic batching:
with client.write.buffered(batch_size=10000, flush_interval=5.0) as buffer:
for record in records:
buffer.write(
measurement="events",
tags={"source": record.source},
fields={"value": record.value},
timestamp=record.timestamp,
)
# Auto-flushes on exit or when batch_size/flush_interval reached
That flush sends rows the client holds. Arc buffers accepted rows in turn and
writes them to Parquet every ingest.max_buffer_age_ms (5 s by default). To
make them queryable at once, for example in tests, flush the server's buffers
(admin token; flushes every protocol and database on that node):
client.write.flush_server_buffers()
Line Protocol
For compatibility with InfluxDB tooling:
# Single line
client.write.write_line_protocol("cpu,host=server01 usage=45.2 1633024800000000000")
# Multiple lines
lines = [
"cpu,host=server01 usage=45.2",
"cpu,host=server02 usage=67.8",
]
client.write.write_line_protocol(lines)
TLE (Two-Line Element) Streaming
Stream satellite TLE text; the server parses it into orbital-element fields:
tle = """ISS (ZARYA)
1 25544U 98067A 24001.50000000 .00016717 00000-0 10270-3 0 9994
2 25544 51.6416 247.4627 0006703 130.5360 325.0288 15.49309239432416"""
client.write.write_tle(tle, measurement="satellite_tle")
Precision, Tags and Partial Writes
client.write.write_line_protocol("cpu,host=a v=1 1700000000", precision="s")
client.write.write_columnar("cpu", cols, tag_columns=["host", "region"])
client.write.write_dataframe(df, "cpu", tag_columns=["host"])
from arc_client import ArcPartialWriteError, ArcIngestRefusedError
try:
client.write.write_line_protocol(lines)
except ArcPartialWriteError as e: # never resend: the rest was stored
print(e.dropped, e.others_written)
except ArcIngestRefusedError as e: # retries exhausted, or unsafe to resend
print(e.reason, e.retry_safe)
Arc refuses writes with a 503 during failover or under disk pressure. The SDK
resends single-measurement writes that Arc reports as "nothing was written".
It never resends a partial write, a wal_not_durable refusal, or a refusal
of a line-protocol body spanning several measurements: Arc may already have
stored part of those.
Bulk Import
Import files directly (admin token required). Each returns a typed result with the number of rows imported. Files may be gzip-compressed for LP/TLE.
# CSV
result = client.import_.import_csv("metrics.csv", measurement="cpu",
time_column="time", time_format="epoch_ms")
print(result.rows_imported)
# Parquet
client.import_.import_parquet("data.parquet", measurement="cpu")
# InfluxDB line-protocol file
client.import_.import_lp("dump.lp", precision="ns")
# TLE file
client.import_.import_tle("catalog.tle", measurement="satellite_tle")
import_csv/import_parquet/import_lp/import_tle accept a path, a binary
file-like object, or raw bytes.
Databases
client.databases.create("metrics")
for db in client.databases.list().databases:
print(db.name, db.measurement_count)
info = client.databases.get("metrics")
measurements = client.databases.list_measurements("metrics")
# Destructive — requires confirm=True and server-side delete enabled
client.databases.delete("metrics", confirm=True)
The three read methods need a token with read permission. On a server that
restricts reads per database they also need a grant for the database in
question, and list() needs one covering every database — Arc refuses rather
than returning a filtered list, the same way SHOW DATABASES does:
from arc_client.exceptions import ArcScopedAccessError
try:
databases = client.databases.list().databases
except ArcScopedAccessError:
# Expected for a tenant-scoped token: it cannot enumerate every database,
# so ask for the one it is granted instead of retrying.
measurements = client.databases.list_measurements("metrics")
ArcScopedAccessError.database carries the database the call was refused for
(empty or "*" when the call asked for every database). A token with no read
permission at all raises ArcPermissionError instead; Arc failing to load the
token's grants raises ArcPermissionDataUnavailableError, a server-side fault
rather than a statement about the token; and a database that does not exist
still raises ArcNotFoundError — "you may not read it" and "it is not there"
stay apart.
Querying Data
JSON Response
result = client.query.query("SELECT * FROM cpu WHERE time > now() - INTERVAL '1 hour'")
print(result.columns) # ['time', 'host', 'usage']
print(result.data) # [[1633024800000000, 'server01', 45.2], ...]
print(result.row_count)
pandas DataFrame
df = client.query.query_pandas("SELECT * FROM cpu LIMIT 1000")
Polars DataFrame
pl_df = client.query.query_polars("SELECT * FROM cpu LIMIT 1000")
PyArrow Table (Zero-Copy)
table = client.query.query_arrow("SELECT * FROM cpu LIMIT 1000")
metadata = table.schema.metadata or {}
if metadata.get(b"arc.rows_capped") == b"true":
print("Policy capped the result at", int(metadata[b"arc.row_cap"]))
query_arrow() still returns a pyarrow.Table, with authoritative completion
metadata under reserved schema keys arc.rows_capped, arc.row_cap and
arc.execution_time_ms (byte keys and values). A missing cap flag means unknown;
false means the supported server completed its uncapped trailer contract.
Timing promoted into initial headers cannot prove uncapped completion after
final trailers disappear.
Native column types and unrelated schema metadata are preserved. Truncated,
malformed, conflicting or unobservable announced metadata raises ArcQueryError.
DataFrame conversions can drop schema metadata; inspect the Arrow table first
when completeness matters.
Trailer capture is tested with HTTPX 0.27/0.28, httpcore 1.0.9 and h11 0.16.
httpcore is bounded >=1.0.9,<1.1, because the internals the adapter reads are
unchanged across 1.0.x. If a release changes them, Arrow responses that
announce trailers fail with ArcQueryError rather than return unverified
metadata.
MessagePack Response
A compact columnar MessagePack response with native timestamp decoding. Returns
the same QueryResponse shape as query() (row-major data), plus per-column
Arrow types in .types:
result = client.query.query_msgpack("SELECT * FROM cpu LIMIT 1000")
print(result.columns, result.types)
This uses /api/v1/query/msgpack, stable since Arc 2026.09.1. Older servers
built without the duckdb_arrow tag answer 501, which raises
ArcNotSupportedError.
Query Estimation
Preview query cost before execution:
estimate = client.query.estimate("SELECT * FROM cpu")
print(f"Estimated rows: {estimate.estimated_rows}")
print(f"Warning level: {estimate.warning_level}") # none, low, medium, high
List Measurements
measurements = client.query.list_measurements(database="default")
for m in measurements:
print(f"{m.measurement}: {m.file_count} files, {m.total_size_mb:.1f} MB")
Profiling, Query IDs and Measurement Reads
r = client.query.query("SELECT * FROM cpu", profile=True)
print(r.profile.total_ms, r.profile.rows_scanned, r.query_id)
client.queries.kill(r.query_id)
# Arrow wire encodings; the query ID is in the schema metadata
t = client.query.query_arrow("SELECT * FROM cpu", dictionary=True, compression="zstd")
t.schema.metadata[b"arc.query_id"]
# Rows of one measurement without free-form SQL
client.query.query_measurement("cpu", "metrics", limit=100, order_by="time ASC", where="host = 'a'")
# Stable measurement schema (admin rebuild is queued, 202)
s = client.databases.get_measurement_schema("metrics", "cpu")
client.databases.rebuild_measurement_schema("metrics", "cpu")
Async Support
All operations have async equivalents:
import asyncio
from arc_client import AsyncArcClient
async def main():
async with AsyncArcClient(host="localhost", token="your-token") as client:
# Write
await client.write.write_columnar(
measurement="cpu",
columns={"time": [...], "host": [...], "usage": [...]},
)
# Query
df = await client.query.query_pandas("SELECT * FROM cpu")
# Buffered writes
async with client.write.buffered(batch_size=5000) as buffer:
for record in records:
await buffer.write(measurement="events", fields={"v": record.v})
asyncio.run(main())
Management Operations
Retention Policies
Manage retention policies (automatic execution requires an enabled, licensed scheduler):
# Create policy
policy = client.retention.create(
name="30-day-retention",
database="default",
retention_days=30,
measurement="logs", # optional, applies to all if not specified
)
# List policies
policies = client.retention.list()
# Execute (with dry_run first)
result = client.retention.execute(policy.id, dry_run=True)
print(f"Would delete {result.deleted_count} rows")
# Execute for real
result = client.retention.execute(policy.id, dry_run=False, confirm=True)
Scheduler inspection and controls
Scheduler status is available to authenticated tokens. Reloading continuous-query schedules and manually triggering retention require an administrator token and the corresponding enterprise scheduler feature.
status = client.schedulers.status()
client.schedulers.reload_continuous_queries()
# Runs all active retention policies immediately and may permanently delete data.
client.schedulers.trigger_retention(confirm=True)
The retention operation refuses to send a request unless confirm=True is
supplied. The async client exposes the same methods:
async with AsyncArcClient(host="localhost", token="your-token") as client:
status = await client.schedulers.status()
Continuous Queries
Manage continuous queries (automatic execution requires an enabled, licensed scheduler):
# Create a CQ to downsample CPU metrics to 1-hour averages
cq = client.continuous_queries.create(
name="cpu-hourly",
database="default",
source_measurement="cpu",
destination_measurement="cpu_1h",
query="SELECT time_bucket('1 hour', time) as time, host, avg(usage) as usage FROM default.cpu WHERE time >= {start_time} AND time < {end_time} GROUP BY 1, 2",
interval="1h",
)
# Manual execution with time range
result = client.continuous_queries.execute(
cq.id,
start_time="2024-01-01T00:00:00Z",
end_time="2024-01-02T00:00:00Z",
dry_run=True,
)
# List CQs
cqs = client.continuous_queries.list(database="default")
Delete Operations
Delete data with WHERE clause:
# Always dry_run first
result = client.delete.delete(
database="default",
measurement="logs",
where="time < '2024-01-01'",
dry_run=True,
)
print(f"Would delete {result.deleted_count} rows from {result.affected_files} files")
# Execute deletion
result = client.delete.delete(
database="default",
measurement="logs",
where="time < '2024-01-01'",
dry_run=False,
confirm=True, # Required for large deletes
)
Authentication
# Verify current token
verify = client.auth.verify()
if verify.valid:
print(f"Token: {verify.token_info.name}")
print(f"Permissions: {verify.permissions}")
# Create new token
result = client.auth.create_token(
name="my-app-token",
description="Token for my application",
permissions=["read", "write"],
)
print(f"New token: {result.token}") # Save this - shown only once!
# List tokens
tokens = client.auth.list_tokens()
# Rotate token
rotated = client.auth.rotate_token(token_id=123)
print(f"New token: {rotated.new_token}")
# Revoke token
client.auth.revoke_token(token_id=123)
Enterprise Operations
These require an Arc server with the corresponding enterprise license feature.
Without it, calls raise ArcLicenseError (a subclass of ArcAuthenticationError).
Each sub-client is a thin wrapper that returns the server's JSON.
# RBAC: organizations -> teams -> roles -> measurement permissions
org = client.rbac.create_organization("acme")
client.rbac.add_token_to_team(token_id=123, team_id=1)
# Query governance (per-token rate limits & quotas)
client.governance.create_policy(token_id=123, rate_limit_per_minute=600)
print(client.governance.usage(123))
# Audit logs
client.audit.logs(event_type="query", since="2024-01-01T00:00:00Z", limit=100)
# Query management
client.queries.active()
client.queries.kill("query-id")
# Cluster / compaction / tiering / backup / MQTT (admin)
client.cluster.status()
client.cluster.converge_voters() # plan only
client.cluster.converge_voters(dry_run=False, confirm=True)
client.cluster.demote_writer("writer-1", confirm=True)
client.cluster.policies(kind="retention") # on the Raft leader
client.compaction.trigger(database="metrics", measurement="cpu")
client.compaction.cycles(limit=5)
client.compaction.too_wide()
# Scheduler inspection and explicit operator controls
client.schedulers.status() # requires an authenticated token
client.schedulers.reload_continuous_queries() # administrator + licensed feature
# Retention may permanently delete data; explicit confirmation is required.
client.schedulers.trigger_retention(confirm=True)
client.tiering.set_policy("metrics", hot_only=True, hot_max_age_days=7)
client.backup.create(databases=["metrics"]) # scoped backup
client.backup.list(include_foreign=True)
client.backup.restore("backup-id", confirm=True, mode="merge")
client.mqtt.list_subscriptions()
Operations and Diagnostics
# Readiness: should this node get traffic / writes, and if not, why?
r = client.readiness(); print(r.ready, r.reason, r.tier)
client.write_readiness().status # "ready" | "not_ready" | "not_write_target"
# Metrics (public) and logs (admin)
client.diagnostics.metrics()
client.diagnostics.timeseries("api", duration_minutes=15)
client.diagnostics.logs(level="warn", since_minutes=30, limit=200)
client.auth.cache_stats()
# Write-protocol counters on this node (any token)
client.diagnostics.line_protocol_stats()["stats"]["total_errors"]
client.diagnostics.msgpack_stats() # MessagePack decoder and Arrow buffer
client.diagnostics.msgpack_spec() # the MessagePack write format Arc accepts
# Reconciliation (enterprise clustering): dry run first, then act
run = client.reconciliation.trigger() # dry run
client.reconciliation.trigger(dry_run=False, confirm=True)
# Edge sync, on the hub
secret = client.edge_sync.register_spoke("rocket-01", name="Rocket")
print(secret.secret) # shown only once
client.edge_sync.import_bundle("/mnt/drive/bundle-1")
# Edge sync, on the spoke
client.edge_sync.spoke_status()
client.edge_sync.run_sync() # long-running: use a large client timeout
client.edge_sync.requeue_failed(all_failed=True)
Destructive or disruptive calls (reconciliation.trigger(dry_run=False),
diagnostics.free_os_memory, edge_sync.rotate_spoke_secret,
edge_sync.delete_spoke, edge_sync.dismiss_failed) require confirm=True.
Configuration
from arc_client import ArcClient, Compression
client = ArcClient(
host="localhost", # Arc server hostname
port=8000, # Arc server port (default: 8000)
token="your-token", # API token
database="default", # Default database
timeout=30.0, # Request timeout in seconds
compression=Compression.ZSTD, # "zstd" (default), "gzip", "none", or a bool
ssl=False, # Use HTTPS
verify_ssl=True, # Verify SSL certificates
max_retries=3, # Retries for connection errors / 429 / 503
retry_backoff=0.5, # Base backoff (seconds) for exponential retry
)
compression accepts a Compression enum, a string ("zstd"/"gzip"/"none"),
or a bool for backward compatibility (True → gzip, False → none). Arc detects
the codec from the payload's magic bytes, so no Content-Encoding header is sent.
Error Handling
from arc_client.exceptions import (
ArcError, # Base exception
ArcConnectionError, # Connection failures
ArcAuthenticationError,# Token missing, invalid or expired (401)
ArcPermissionError, # Token lacks the required permission (403)
ArcScopedAccessError, # Token may read, but not this database (403)
ArcPermissionDataUnavailableError, # Arc could not load the grants (403)
ArcLicenseError, # Enterprise feature not licensed (403)
ArcQueryError, # Query execution errors
ArcIngestionError, # Write failures
ArcPartialWriteError, # Some points dropped, others stored (400); never resend
ArcIngestRefusedError, # Write refused (503); .reason, .retry_safe
ArcValidationError, # Invalid input
ArcNotFoundError, # Resource not found (404)
ArcRateLimitError, # Rate limited (429)
ArcNotSupportedError, # Operation unsupported by server (501)
ArcServerError, # Server errors (5xx)
)
try:
client.query.query("INVALID SQL")
except ArcQueryError as e:
print(f"Query failed: {e}")
except ArcConnectionError as e:
print(f"Connection failed: {e}")
Privacy
The SDK connects only to the Arc server you configure. It never contacts Basekick or any other service on its own.
Requests identify the SDK version, the Python version and the OS/architecture
in User-Agent. They also carry a random installation ID
(Arc-Client-Installation-Id), created on first use and stored in
~/.config/arc-client-python/installation-id (%APPDATA% on Windows). Arc may
include this ID in its own opt-out telemetry so Basekick can count SDK
installations across Arc servers. The ID is not derived from your machine, user
or token, and nothing about your queries, databases or data is included.
Disable the ID with any of:
DO_NOT_TRACK=1
ARC_CLIENT_SEND_INSTALLATION_ID=0
ArcClient(host="localhost", token="...", send_installation_id=False)
In ephemeral containers, set ARC_CLIENT_INSTALLATION_ID to a fixed UUID so
each start is not counted as a new installation.
Documentation
See the full documentation for detailed guides and API reference.
License
MIT License - see LICENSE for details.
Server compatibility and safe management updates
The SDK distinguishes partial updates from complete replacements:
update()sends only supplied non-Nonefields, without fetching a definition. Use this on servers with partial PUT semantics. ExistingNonearguments remain omitted; usefrom arc_client import CLEARto send JSON null for nullable update fields.replace()sends every mutable field explicitly in one PUT. Arc 26.09.3 uses full-definition PUT semantics for retention policies and continuous queries, so usereplace()on that release. The method also supports servers with partial PUT semantics. It intentionally overwrites the whole definition; coordinate concurrent edits before calling it.
There is no server-capability guessing or retry with a different update payload.
Both sync and async clients provide the same methods. CQ replacements include
tag_columns; retention replacements include database, measurement, and buffer_days.
Query results retain truncated, truncation_reason, rows_capped, and row_cap
when their wire format supplies them. query_msgpack() returns UTC
datetime values when a timestamp is exactly representable at microsecond resolution.
Submicrosecond or out-of-range timestamps remain msgpack.Timestamp, preserving
.seconds, .nanoseconds, and .to_unix_nano(). Such cells require an explicit
serialization choice when exporting JSON. Arrow completion metadata is available
in the returned table schema as described above.
DELETE results expose failed, unreachable, unflushed, and cold-tier omission details.
HTTP 207 remains a result that callers must inspect. Non-2xx typed exceptions retain
structured details in error.response_body. Data DELETE requests are never automatically
replayed after a server or transport failure, because work may already have committed.
Automatic 429/503 and ambiguous transport retries apply only to read-only HTTP methods. Other mutations retry only connection-establishment failures; unknown write outcomes are surfaced for the caller to reconcile, rather than replayed automatically.
Query-client requests already carry the configured database in x-arc-database. Use
unqualified measurement names in those SQL requests, for example
client.query.query("SELECT * FROM cpu LIMIT 10"). CQ definitions run inside
the server and use the qualified source measurement, such as default.cpu,
as shown in the CQ example above.
A client timeout does not confirm cancellation of retention work. Check execution history and resulting data before submitting it again. On Arc 26.09.3 and earlier, a running execution is missing from that history until it finishes (fixed in Arc 27.01.1).
Metadata
Release files for arc-tsdb-client 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| arc_tsdb_client-0.2.0.tar.gz | 116.6 kB | Without provenance | Details for arc_tsdb_client-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| arc_tsdb_client-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for arc_tsdb_client-0.2.0-py3-none-any.whl |
Total release size: 290.2 kB
Release files / arc_tsdb_client-0.2.0.tar.gz
| Download URL | arc_tsdb_client-0.2.0.tar.gz |
|---|---|
| Size | 116.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3c2ccaba5a9977fd3299381a7f64a7daf42cbb9e4d9b4d772d4904acbb3e0428
|
|
BLAKE2b-256 checksum How to use checksums |
7c499e2694dc62253576935156b6740301f8d70620d1d3dee8ca7d4e459d8b55
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / arc_tsdb_client-0.2.0-py3-none-any.whl
| Download URL | arc_tsdb_client-0.2.0-py3-none-any.whl |
|---|---|
| Size | 173.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4985408fe31c76c3c0f5c3ee3efd9036bbc7084e1dd69f6e641efb044c12fcb5
|
|
BLAKE2b-256 checksum How to use checksums |
653fd0d9bb068f0661ce676adef2be0b80489d4a45e5bfc87e76defa9417cd2d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for arc-tsdb-client 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.