Skip to main content

Time Series Engine Overview

The Time Series Engine (TSE) is a metrics-only storage and query engine. The platform and edge push their own state as numbers, and PlantPulse Dashboard renders them.

Not the "Time Series Database" — a Different Thing

Due to the similar name, this is the most confusing area. The layers, what they store, and their query languages are all different.

Time Series Engine (TSE)Time Series Database
What it storesMetrics — system's own indicators like PLANTPULSE.JMX.* · PLANTPULSE.EDGE.*Sensor values — tag data points from the field (pp.tm_tag_point)
NatureMetrics-only (KairosDB lineage)General-purpose time series database (in-house fork of Aster TSDB)
Port7800 (plaintext) · 7801 (TLS)9042 (CQL)
QueryTQLCQL — built-in functions like time_bucket_gapfill
UIBundled PlantPulse Dashboard (3000) · Time Series Analyzer (7801)Query Console · Spark SQL
DocumentationThis sectionTime Series Database

"How was the equipment temperature?" is a database question; "how many records did the collector process yesterday?" is an engine question.

What's Included​

WhatValue
Enginetse — port 7800 (HTTP) · 7801 (TLS)
DashboardBundled PlantPulse Dashboard — port 3000
pd servicetimeseries — MASTER node only (as of 2026-09-05)
Actual storageAster TSDB (the engine sits on top of it)
The engine also writes to Aster TSDB — but it's still a different thing

The TSE does not have its own separate storage; it uses the same Aster TSDB ring. That doesn't make them the same thing — the keyspace and schema are different, and the query paths are different. Metrics stored in the engine won't show up even if you query the tag table with CQL.

Documents in This Section​

TaskDocument
Query from outside or write dataTQL and JDBC Driver
Create dashboardsCreating a Dashboard in PlantPulse Dashboard
Use with Prometheus·PromQLPrometheus Integration
View the engine's own metricsTime Series Analyzer
Modules·ports·startup orderplantpulse-timeseries Component