pub struct AnalyticsConfig {
pub max_forecast_horizon: usize,
pub max_training_points: usize,
}Expand description
Analytics engine configuration: the bounds on what one call may ask for.
Configurable via TOML under the [analytics] section.
Both fields are bounds, and that is the whole section on purpose. The
model, the detector, the confidence level and the threshold are arguments
to the analytics API — ForecastConfig and AnomalyConfig, passed per
call — and no deployment-wide default could reach them anyway: chronixd
serves no forecasting or anomaly endpoint, and SQL splits the choice
across two named functions.
Four default_* keys for exactly those once sat here with a serde
default, a validated type and no reader. Their absence is load-bearing
rather than tidy: deny_unknown_fields is the same mechanism that refuses
a typo, so a key that parses reads as a key that works.
Fields§
§max_forecast_horizon: usizeMaximum forecast horizon in data points.
max_training_points: usizeMaximum number of training points fed to a model.
Trait Implementations§
Source§impl Clone for AnalyticsConfig
impl Clone for AnalyticsConfig
Source§fn clone(&self) -> AnalyticsConfig
fn clone(&self) -> AnalyticsConfig
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more