mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-11-21 14:44:00 +00:00
- fix 404 links after renaming (#5653)
- improve wording on diagram - swap enterprise/about chapters for page clarity
This commit is contained in:
parent
0038102b98
commit
7e68722686
5 changed files with 8 additions and 7 deletions
|
@ -18,6 +18,8 @@ VictoriaMetrics Anomaly Detection, also known as `vmanomaly`, is a service for d
|
||||||
|
|
||||||
Please refer to [our guide section](/anomaly-detection/#practical-guides-and-installation) to find out more.
|
Please refer to [our guide section](/anomaly-detection/#practical-guides-and-installation) to find out more.
|
||||||
|
|
||||||
|
> **Note: `vmanomaly` is a part of [enterprise package](https://docs.victoriametrics.com/enterprise.html). You need to get a [free trial license](https://victoriametrics.com/products/enterprise/trial/) for evaluation.**
|
||||||
|
|
||||||
## What is anomaly score?
|
## What is anomaly score?
|
||||||
Among the metrics produced by `vmanomaly` (as detailed in [vmanomaly output metrics](/anomaly-detection/components/models.html#vmanomaly-output)), `anomaly_score` is a pivotal one. It is **a continuous score > 0**, calculated in such a way that **scores ranging from 0.0 to 1.0 usually represent normal data**, while **scores exceeding 1.0 are typically classified as anomalous**. However, it's important to note that the threshold for anomaly detection can be customized in the alert configuration settings.
|
Among the metrics produced by `vmanomaly` (as detailed in [vmanomaly output metrics](/anomaly-detection/components/models.html#vmanomaly-output)), `anomaly_score` is a pivotal one. It is **a continuous score > 0**, calculated in such a way that **scores ranging from 0.0 to 1.0 usually represent normal data**, while **scores exceeding 1.0 are typically classified as anomalous**. However, it's important to note that the threshold for anomaly detection can be customized in the alert configuration settings.
|
||||||
|
|
||||||
|
@ -31,7 +33,6 @@ The decision to set the changepoint at `1.0` is made to ensure consistency acros
|
||||||
1. For more detailed information, please visit the [overview section](/anomaly-detection/Overview.html#about).
|
1. For more detailed information, please visit the [overview section](/anomaly-detection/Overview.html#about).
|
||||||
2. To view a diagram illustrating the interaction of components, please explore the [components section](/anomaly-detection/components/).
|
2. To view a diagram illustrating the interaction of components, please explore the [components section](/anomaly-detection/components/).
|
||||||
|
|
||||||
|
|
||||||
## What data does vmanomaly operate on?
|
## What data does vmanomaly operate on?
|
||||||
`vmanomaly` operates on data fetched from VictoriaMetrics, where you can leverage full power of [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html) for data selection, sampling, and processing. Users can also [apply global filters](https://docs.victoriametrics.com/#prometheus-querying-api-enhancements) for more targeted data analysis, enhancing scope limitation and tenant visibility.
|
`vmanomaly` operates on data fetched from VictoriaMetrics, where you can leverage full power of [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html) for data selection, sampling, and processing. Users can also [apply global filters](https://docs.victoriametrics.com/#prometheus-querying-api-enhancements) for more targeted data analysis, enhancing scope limitation and tenant visibility.
|
||||||
|
|
||||||
|
|
|
@ -14,8 +14,6 @@ aliases:
|
||||||
|
|
||||||
# Overview
|
# Overview
|
||||||
|
|
||||||
**_vmanomaly_ is a part of [enterprise package](https://docs.victoriametrics.com/enterprise.html). You need to request a [free trial license](https://victoriametrics.com/products/enterprise/trial/) for evaluation.**
|
|
||||||
|
|
||||||
## About
|
## About
|
||||||
|
|
||||||
**VictoriaMetrics Anomaly Detection** (or shortly, `vmanomaly`) is a service that continuously scans VictoriaMetrics time
|
**VictoriaMetrics Anomaly Detection** (or shortly, `vmanomaly`) is a service that continuously scans VictoriaMetrics time
|
||||||
|
@ -36,6 +34,8 @@ In addition to that, setting up alerting rules manually has been proven to be te
|
||||||
error-prone, while anomaly detection can be easier to set up, and use the same model for different
|
error-prone, while anomaly detection can be easier to set up, and use the same model for different
|
||||||
metrics.
|
metrics.
|
||||||
|
|
||||||
|
> **Note: `vmanomaly` is a part of [enterprise package](https://docs.victoriametrics.com/enterprise.html). You need to get a [free trial license](https://victoriametrics.com/products/enterprise/trial/) for evaluation.**
|
||||||
|
|
||||||
## How?
|
## How?
|
||||||
|
|
||||||
VictoriaMetrics Anomaly Detection service (**vmanomaly**) allows you to apply several built-in
|
VictoriaMetrics Anomaly Detection service (**vmanomaly**) allows you to apply several built-in
|
||||||
|
|
|
@ -14,15 +14,15 @@ In the dynamic and complex world of system monitoring, VictoriaMetrics Anomaly D
|
||||||
## Practical Guides and Installation
|
## Practical Guides and Installation
|
||||||
Begin your VictoriaMetrics Anomaly Detection journey with ease using our guides and installation instructions:
|
Begin your VictoriaMetrics Anomaly Detection journey with ease using our guides and installation instructions:
|
||||||
|
|
||||||
- **Overview**: Find out how `vmanomaly` service operates [here](/anomaly-detection/overview.html)
|
- **Overview**: Find out how `vmanomaly` service operates [here](/anomaly-detection/Overview.html)
|
||||||
- **Integration**: Integrate anomaly detection into your observability ecosystem. Get started [**here**](/anomaly-detection/guides/guide-vmanomaly-vmalert.html).
|
- **Integration**: Integrate anomaly detection into your observability ecosystem. Get started [**here**](/anomaly-detection/guides/guide-vmanomaly-vmalert.html).
|
||||||
|
|
||||||
- **Installation Options**: Select the method that aligns with your technical requirements:
|
- **Installation Options**: Select the method that aligns with your technical requirements:
|
||||||
- **Docker Installation**: Suitable for containerized environments. See [Docker guide](/anomaly-detection/overview#run-vmanomaly-docker-container).
|
- **Docker Installation**: Suitable for containerized environments. See [Docker guide](/anomaly-detection/Overview.html#run-vmanomaly-docker-container).
|
||||||
- **Helm Chart Installation**: Appropriate for those using Kubernetes. See our [Helm charts](https://github.com/VictoriaMetrics/helm-charts/tree/master/charts/victoria-metrics-anomaly).
|
- **Helm Chart Installation**: Appropriate for those using Kubernetes. See our [Helm charts](https://github.com/VictoriaMetrics/helm-charts/tree/master/charts/victoria-metrics-anomaly).
|
||||||
|
|
||||||
|
|
||||||
> Note: starting from [v1.5.0](./CHANGELOG.md#v150) `vmanomaly` requires a [license key](/anomaly-detection/overview#licensing) to run. You can obtain a trial license key [**here**](https://victoriametrics.com/products/enterprise/trial/index.html).
|
> **Note**: starting from [v1.5.0](./CHANGELOG.md#v150) `vmanomaly` requires a [license key](/anomaly-detection/Overview.html#licensing) to run. You can obtain a trial license key [**here**](https://victoriametrics.com/products/enterprise/trial/index.html).
|
||||||
|
|
||||||
## Key Components
|
## Key Components
|
||||||
Explore the integral components that configure VictoriaMetrics Anomaly Detection:
|
Explore the integral components that configure VictoriaMetrics Anomaly Detection:
|
||||||
|
|
Binary file not shown.
Before Width: | Height: | Size: 60 KiB After Width: | Height: | Size: 40 KiB |
|
@ -8,6 +8,6 @@ menu:
|
||||||
weight: 11
|
weight: 11
|
||||||
---
|
---
|
||||||
|
|
||||||
vmanomaly currently has own section.
|
vmanomaly currently has its own section.
|
||||||
|
|
||||||
Please head to [Anomaly Detection section](/anomaly-detection) to find out more.
|
Please head to [Anomaly Detection section](/anomaly-detection) to find out more.
|
||||||
|
|
Loading…
Reference in a new issue