mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-12-15 00:13:30 +01:00
a68518c0e0
* first edit
* typo 1
* typo 2
* fixes 3
* fixes 4
* fixes 5
* fixes, cross links
* v1.10 config
* models why, self-monitoring fix
* config next steps
* fixes
* minor fix
(cherry picked from commit
|
||
|---|---|---|
| .. | ||
| models.md | ||
| monitoring.md | ||
| reader.md | ||
| README.md | ||
| scheduler.md | ||
| vmanomaly-components.webp | ||
| writer.md | ||
| title | weight | menu | aliases | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Components | 2 |
|
|
Components
This chapter describes different components, that correspond to respective sections of a config to launch VictoriaMetrics Anomaly Detection (or simply vmanomaly) service:
- Model(s) section - Required
- Reader section - Required
- Scheduler section - Required
- Writer section - Required
- Monitoring section - Optional
Note
: starting from v1.7.0, once the service starts, automated config validation is performed. Please see container logs for errors that need to be fixed to create fully valid config, visiting sections above for examples and documentation.
Below, you will find an example illustrating how the components of vmanomaly interact with each other and with a single-node VictoriaMetrics setup.
Note
: Reader and Writer also support multitenancy, so you can read/write from/to different locations - see
tenant_idparam description.
