From 5f1120249fb60ffaa804d2203a8dffe181aea61325d2dea85e6271ee7b477b9d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Dan=20=C4=8Cerm=C3=A1k?= Date: Wed, 8 May 2024 16:29:53 +0000 Subject: [PATCH] [info=36c80aa7e389001a2f598272bbfbc304] OBS-URL: https://build.opensuse.org/package/show/devel:BCI:Tumbleweed/pcp-image?expand=0&rev=129 --- README.md | 7 ++++--- pcp-image.changes | 5 +++++ 2 files changed, 9 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index b2298fa..ea10222 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,8 @@ -# Performance Co-Pilot container +# openSUSE Tumbleweed Performance Co-Pilot (pcp): Performance Co-Pilot ![Redistributable](https://img.shields.io/badge/Redistributable-Yes-green) +## Description Performance Co-Pilot ([PCP](https://pcp.io)) is a system performance analysis toolkit. ## Usage @@ -34,7 +35,7 @@ $ sudo podman run -d \ ## Configuration -### Environment Variables +### Environment variables #### `PCP_SERVICES` Default: `pmcd,pmie,pmlogger,pmproxy` @@ -52,7 +53,7 @@ Default: `localhost:6379` Redis connection spec(s) - could be any individual cluster host, and all hosts in the cluster will be automatically discovered. Alternately, use comma-separated hostspecs (non-clustered setup) -### Configuration Files +### Configuration files For custom configuration options beyond the above environment variables, it is advised to use a bind mount with a configuration file on the host to the container. Example command to run a pmlogger-only container: diff --git a/pcp-image.changes b/pcp-image.changes index 7d52bb3..01e7001 100644 --- a/pcp-image.changes +++ b/pcp-image.changes @@ -1,3 +1,8 @@ +------------------------------------------------------------------- +Wed May 8 16:26:31 UTC 2024 - Dirk Mueller + +- README fixes - better titles and follow recommended document structure + ------------------------------------------------------------------- Tue May 7 19:07:24 UTC 2024 - Dirk Mueller