https://docs.mitigator.ru/v26.04/en/tags/override/ Recent content in Override on BIFIT Mitigator Hugo -- gohugo.io en https://docs.mitigator.ru/v26.04/en/kb/graphite/grafbase/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.mitigator.ru/v26.04/en/kb/graphite/grafbase/ Moving Graphite to a separate server allows you to split the load between two servers. Until the metrics archive is transferred, only new graphs can be viewed in the MITIGATOR interface. Further in the text Server1 is the server with MITIGATOR, Server2 is the server to which the transfer is being performed. It is assumed that Server2 already has Docker and docker-compose installed and has a way to deliver the filebase from Server1 to Server2 (the amount of data can be more than 100 GB depending on the number of policies). https://docs.mitigator.ru/v26.04/en/kb/graphite/ext-grafana/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.mitigator.ru/v26.04/en/kb/graphite/ext-grafana/ Чтобы внешняя Grafana могла получать данные с Graphite нужно пробросить порт 3080 из контейнера, для чего: Cоздать, либо дополнить docker-compose.override.yml следующим: services: gateway: ports: - "13080:3080" Перезапустить MITIGATOR: docker-compose down && docker-compose up -d В Web-интерфейсе Grafana добавить источник данных: Выбрать тип Graphite и указать внешний адрес: Related Content Graphite on a Separate Server Access to the Grafana Interface Setting the Storage Time for Metrics in Graphite Using a Single Graphite for Multiple MITIGATOR Clusters Exporting Metrics to Prometheus Изменение конфигурационных параметров ClickHouse Challenge-response Authentication Module for HTTP/HTTPS Configuration Change Configuring Tiered Protection with MITIGATOR Core Isolation for Performance Optimization https://docs.mitigator.ru/v26.04/en/integrate/prometheus/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.mitigator.ru/v26.04/en/integrate/prometheus/ Metrics in MITIGATOR are stored in Graphite. It is possible to export metrics to Prometheus via graphite_exporter. To organize sending, you need to deploy and configure graphite_exporter (the main configuration file and the configuration file for metrics matching), then configure sending metrics to graphite_exporter. Brief sequence of actions: Writing a metric compliance configuration for specific needs. Deploying graphite_exporter with this configuration. Setting up data sending in the MITIGATOR system. graphite_exporter metrics matching configuration A list of metrics with a short description is available by link. https://docs.mitigator.ru/v26.04/en/kb/graphite/retention/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.mitigator.ru/v26.04/en/kb/graphite/retention/ MITIGATOR stores graph data in Graphite-ClickHouse. Fresh data is stored with a smaller sparsity, then thinned out: Term Sparcity Less than a day 5 seconds day to week 10 seconds week to month 1 minute month to 145 days 5 minutes Over 145 days 10 minutes The retention times are not cumulative, i.e. data for the last day of the last week is stored at a 5 second spacing, and the next 6 days (not 7) are stored at a 10 second spacing. https://docs.mitigator.ru/v26.04/en/kb/graphite/onegraphite/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.mitigator.ru/v26.04/en/kb/graphite/onegraphite/ Using a single Graphite for several MITIGATOR instances makes it possible to reduce the load on the computing resources of traffic processing complexes, simplify administration and set up complex monitoring. Set up The setup is similar to migration of Graphite to a separate server. If you have a host with Graphite configured, you must skip to the Configuring MITIGATOR to work with External Shared Graphite step. Create a directory for the services: