<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Grafana on BIFIT Mitigator</title>
    <link>https://docs.mitigator.ru/v26.04/en/tags/grafana/</link>
    <description>Recent content in Grafana on BIFIT Mitigator</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language><atom:link href="https://docs.mitigator.ru/v26.04/en/tags/grafana/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Access to the Grafana Interface</title>
      <link>https://docs.mitigator.ru/v26.04/en/kb/graphite/grafana/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.mitigator.ru/v26.04/en/kb/graphite/grafana/</guid>
      <description>MITIGATOR comes with Grafana which can be used to create custom dashboards. See the Grafana documentation to understand exactly how to do this.
To gain access to the Grafana web interface, you need to set up the service, which is disabled by default. You can temporarily do this with the following command:
docker-compose up -d --scale grafana=1 grafana To enable grafana permanently, you need to change scale from 0 to 1 in docker-compose.</description>
    </item>
    <item>
      <title>Graphite on a Separate Server</title>
      <link>https://docs.mitigator.ru/v26.04/en/kb/graphite/grafbase/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.mitigator.ru/v26.04/en/kb/graphite/grafbase/</guid>
      <description>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).</description>
    </item>
    <item>
      <title>Подключение внешней Grafana</title>
      <link>https://docs.mitigator.ru/v26.04/en/kb/graphite/ext-grafana/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.mitigator.ru/v26.04/en/kb/graphite/ext-grafana/</guid>
      <description>Чтобы внешняя Grafana могла получать данные с Graphite нужно пробросить порт 3080 из контейнера, для чего:
Cоздать, либо дополнить docker-compose.override.yml следующим: services: gateway: ports: - &amp;#34;13080:3080&amp;#34; Перезапустить MITIGATOR: docker-compose down &amp;amp;&amp;amp; 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 </description>
    </item>
    <item>
      <title>Graphs</title>
      <link>https://docs.mitigator.ru/v26.04/en/kb/graphite/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.mitigator.ru/v26.04/en/kb/graphite/</guid>
      <description>In MITIGATOR for working with graphs are used: ClickHouse, Graphite, Grafana, Carbon, CarbonAPI.
All of the above have the ability to be fine-tuned depending on requirements.
Articles describing various set up aspects:
Access to the Grafana Interface Graphite on a Separate Server Setting the Storage Time for Metrics in Graphite Using a Single Graphite for Multiple MITIGATOR Clusters </description>
    </item>
  </channel>
</rss>