liveBook · Manning

Time-series database

As explained in Cloud Observability in Action

A time series database is a database optimized for storing and querying values indexed by time.

A time-series database (TSDB) stores and queries metric signals with time as the main index. Its bookkeeping unit is a metric composed of one or more time series, each tracking values over time. section 5.3

Core structure and query patterns include:

  • Time is divided into buckets, potentially as fine-grained as seconds or milliseconds. section 5.3
  • Each time series has a unique name and dimensions such as HTTP status code, URL path, or method. section 5.3
  • Queries retrieve values or aggregates for matching series at an instant or across a time range. section 5.3

Service invocation counter

The series mysvc_http_request_total{status_code="400"} records HTTP API invocations returning status 400. As a counter, it increases monotonically; subtracting values across periods gives invocations during that period. section 5.3

Figure 5.2 Time series database concept, showing N time series of the mysvc_http_request_total metric

Use the figure to inspect how a metric expands into multiple time series indexed by time. section 5.3

How Cloud Observability in Action covers it

How deep it goes
Defines time buckets, series dimensions, counters, data points, and instant or range queries.
Examples
Uses container memory, service invocations, and an HTTP 400 request counter with status-code dimensions.
What you can do after
Evaluate/understand metric behavior by retrieving values or aggregates for selected series and time ranges.
How it connects
Ties metrics to time series, dimensions, counters, and time-range queries.

Also explained in

Compare how 3 books explain time-series database →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Cloud Observability in Action. The section links point to the parts of the book it draws on.