Timecharts allow you to see the change in metric value over time. The amount of data visualized on a graph is dependent on the time selection selected within the Dashboard. You can aggregate metrics from multiple sources into a single line, or graph a line per combination of segment labels.
Time aggregation: For example, the average value of
sysdig_host_cpu_used_percent metric is computed for each entity over 1 hour at 1-minute intervals.
Group Rollup: For each
host_hostName the values from time
aggregation are averaged over the scope and the top 10 segments are
shown on the chart.
For information on configuring a chart, see Create a New Panel.
Types of Timecharts
Timechart look and feel can be configured under Display settings when configuring a panel.
When to Use
|When quickly identifying outlier segments is important.
When plotting a single metric over time.
|When an aggregate view of segments is needed.
|When metrics are sometimes reporting zero.
PromQL-based panels and Form-based panels follow different rules when it comes to choosing which data granularity to use when displaying time series.
PromQL-based panels dynamically choose the appropriate granularity in order to balance maximum resolution with acceptable performance. For a 10-second granular metric such as
sysdig_container_cpu_used_percent, the below table can be used as a reference.
|Number of data points displayed
|60 data points
|360 data points
|360 data points
|720 data points
|144 data points
|96 data points
|168 data points
|336 data points
Timecharts are optimised to refresh as soon as new data is available. As a consequence, if a dashboard contains timechart as well as non-timechart panels, the former might have a higher refresh date.
For SaaS users, form-based panel granularity is now equivalent to PromQL panels. More details here.
Form-based panels follow a static rule when choosing the sampling to use per query.
|< 20 minutes
|< 2 hours
|< 1 day
|< 14 days
|>= 14 days
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.