You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/architecture.rst
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,18 +14,18 @@ Monitored hosts run the **Performance Metrics Collector Daemon (PMCD)**, which c
14
14
Each **PMDA** is responsible for gathering metrics of one specific domain - e.g., the kernel, services (e.g., PostgreSQL), or other instrumented applications.
15
15
The **pmlogger** daemon records metrics from **pmcd** and stores them in archive files on the hard drive.
16
16
17
-
Since **PCP 5** metrics can also be stored in the redis database, which allows multi-host performance analysis, the **pmproxy** daemon discovers new archives (created by **pmlogger**) and stores them in a redis database.
17
+
Since **PCP 5** metrics can also be stored in the valkey database, which allows multi-host performance analysis, the **pmproxy** daemon discovers new archives (created by **pmlogger**) and stores them in a valkey database.
18
18
19
19
Dashboards
20
20
----------
21
21
22
22
Performance Co-Pilot metrics can be analyzed with Grafana dashboards, using the **grafana-pcp** plugin.
23
23
There are two modes available:
24
24
25
-
* historical metrics across multiple hosts using the :doc:`datasources/redis` data source
25
+
* historical metrics across multiple hosts using the :doc:`datasources/valkey` data source
26
26
* live, on-host metrics using the :doc:`datasources/vector` data source
27
27
28
-
The :doc:`datasources/redis` data source sends :ref:`pmseries <pmseries-query-language>` queries to **pmproxy**, which in turn queries the redis database for metrics.
28
+
The :doc:`datasources/valkey` data source sends :ref:`pmseries <pmseries-query-language>` queries to **pmproxy**, which in turn queries the valkey database for metrics.
29
29
The :doc:`datasources/vector` data source connects to **pmproxy**, which in turn requests live metrics directly from a local or remote **PMCD**.
30
30
In this case, metrics are stored temporarily in the browser, and metric values are lost when the browser tab is refreshed.
31
-
The :doc:`PCP Redis data source <datasources/redis>` is required for persistence.
31
+
The :doc:`PCP Valkey data source <datasources/valkey>` is required for persistence.
0 commit comments