From 8b0470b42b894ff02102221d83fe9937613a1976 Mon Sep 17 00:00:00 2001 From: Tomek Mrugalski Date: Fri, 20 Nov 2020 10:19:43 +0100 Subject: [#1539] Addressed problem of duplicate target names --- doc/sphinx/arm/stork.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc') diff --git a/doc/sphinx/arm/stork.rst b/doc/sphinx/arm/stork.rst index 3ae033973d..d21e35be44 100644 --- a/doc/sphinx/arm/stork.rst +++ b/doc/sphinx/arm/stork.rst @@ -18,7 +18,7 @@ and BIND 9. Stork is useful in a variety of scenarios: a single Stork server needs to be deployed, and one Stork agent on each machine to be monitored. - The Stork agent can integrate Kea with Prometheus and Grafana. Once the Stork - agent is active on the server, it serves as a Prometheus exporter. Users who have deployed + agent is active on the server, it serves as a Prometheus exporter. Users who have deployed Prometheus in their networks can visualize statistics as time series using Grafana. - Stork can act as both a dashboard and an integrator for Prometheus/Grafana. Once Stork @@ -46,5 +46,5 @@ to visualize data available in Prometheus; the most common approach is to use Grafana to provide visual dashboards. The Stork project provides dashboard definitions for Kea and BIND 9 that can be imported into Grafana very easily. -Learn more about Prometheus and Grafana on their websites: `Prometheus `_ -and `Grafana `_. +Learn more about Prometheus and Grafana on their websites: `Prometheus ` +and `Grafana `. -- cgit v1.2.3