VictoriaMetrics/docs/anomaly-detection/components
Fred Navruzov c9d8627676
- v1.11 doc updates (#5852)
- fix dead links
2024-02-23 01:11:05 +02:00
..
models.md - v1.11 doc updates (#5852) 2024-02-23 01:11:05 +02:00
monitoring.md docs: vmanomaly - updates of v1.10.0 and model type section (#5813) 2024-02-16 15:31:56 +01:00
reader.md update guide and changelog to 1.9.1 (#5706) 2024-01-29 17:23:06 +01:00
README.md - v1.11 doc updates (#5852) 2024-02-23 01:11:05 +02:00
scheduler.md - v1.11 doc updates (#5852) 2024-02-23 01:11:05 +02:00
vmanomaly-components.webp - fix 404 links after renaming (#5653) 2024-01-22 01:14:54 +02:00
writer.md

title weight menu aliases
Components 2
docs
identifier parent weight
vmanomaly-components anomaly-detection 2
/anomaly-detection/components/
/anomaly-detection/components/index.html

Components

This chapter describes different components, that correspond to respective sections of a config to launch VictoriaMetrics Anomaly Detection (or simply vmanomaly) service:

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_id param description.

vmanomaly-components