Skip to content

Chart families ​

Choose a chart by the relationship in your data, then import its factory. Each family uses the same tokens, compact readings and lifecycle.

Open the examples gallery to try charts and copy their source. The tables below help you choose a visualization and its smallest factory import.

Metric charts ​

ChartTypical useVisualizationSmallest entry
LineChange across supplied times/categoriesline/chart/axis
AreaFilled or stacked time seriesarea/chart/axis
BarCategory comparisons or explicit time bucketsbar/chart/axis
ScatterTwo numeric coordinates, optional size/colorscatter/chart/scatter
DonutNon-negative category weights and sharepie/chart/donut
Top listRows in supplied rank ordertop-list/chart/top-list
TreemapNon-negative weights as proportional cellstreemap/chart/treemap
ValueOne-row aggregate quantitiesbig-number/scalar for direct values; /chart for documents

Paths are relative to @scopedb/scopeview. Horizontal category bars also use /chart/top-list. /report chooses and loads a layout when the type is not known ahead of time.

Traces and profiles ​

FamilyTypical useDocument kindEntry
Trace timelineSpan timing and parent relationshipstrace/trace
Flame graphInclusive weight across a call treeprofile/flame

The data format defines metric encodings, span timestamps and frame weights.

Reading behavior ​

Line/area charts connect samples with straight segments and preserve explicit gaps. Stacked inspection reports individual source quantities. Top lists preserve input order; they do not sort or aggregate. Trace timing uses supplied nanoseconds, and profile width comes from self weight plus descendants. Small marks retain keyboard access to their exact readings.

Next steps ​