wavekit
WaveKit is a simple on-prem tool designed to enhance observability for your RisingWave cluster, enabling faster issue detection, efficient troubleshooting, and improved performance.
WaveKit supports all RisingWave deployment types, including Docker, Kubernetes, and RisingWave Cloud.
Warning
**WaveKit is currently in the public preview stage.**
Note
_WaveKit uses a PostgreSQL database to store key cluster metadata, including connection details like hostnames and ports for RisingWave clusters. To ensure persistence, you’ll need to self-host a PostgreSQL database to prevent metadata loss._
Note
_To use WaveKit, ensure your RisingWave cluster is already running and accessible._
This method installs WaveKit with a bundled PostgreSQL database for convenience. However, if you prefer to use your own self-hosted PostgreSQL database for data persistence, skip to the next section.
You can start the WaveKit server in two ways:
Runs WaveKit with a bundled PostgreSQL database, but metadata is stored inside the container. If the container is removed, all metadata will be lost.
docker run --rm -p 8020:8020 --name wavekit risingwavelabs/wavekit:v0.1.2-pgbundle
Runs WaveKit with a bundled PostgreSQL database and stores metadata in a persistent Docker volume (wavekit-data), ensuring data persists across restarts.
docker run -p 8020:8020 --name wavekit -v wavekit-data:/var/lib/postgresql risingwavelabs/wavekit:v0.1.2-pgbundle
Once the server is running, open your browser and go to:
Use the following default credentials to log in:
rootrootTo install WaveKit using a standalone binary, follow these steps:
curl https://wavekit-release.s3.ap-southeast-1.amazonaws.com/download.sh | sh
WK_PG_DSN=postgres://postgres:postgres@localhost:5432/postgres ./wavekit
Note
Ensure you have a PostgreSQL database running on your machine and set the WK_PG_DSN environment variable to your database connection string.
The following section provides a step-by-step guide to setting up WaveKit with your self-hosted PostgreSQL database. This approach is recommended if you need persistent metadata with high availability.
First, create docker-compose.yaml file with the following content:
version: "3.9"
services:
wavekit:
image: cloudcarver/wavekit:v0.1.2
ports:
- "8020:8020"
environment:
WK_PORT: 8020
WK_PG_DSN: postgres://postgres:postgres@localhost:5432/postgres
WK_RISECTLDIR: /
db:
image: "postgres:latest"
ports:
- "5432:5432"
environment:
POSTGRES_PASSWORD: postgres
volumes:
- db-data:/var/lib/postgresql/data
volumes:
db-data:
wavekit-data:
Start WaveKit by running the following command:
docker compose up
When the server is running, open your browser and go to: http://localhost:8020
WaveKit offers flexible configuration options through either a configuration file or environment variables. For detailed information about available settings and configuration methods, please refer to our configuration documentation.
We welcome contributions to WaveKit! Please refer to our CONTRIBUTING.md for more information on how to contribute to the project.
WaveKit is available in two editions:
Content type
Image
Digest
sha256:19a18b336…
Size
78.5 MB
Last updated
about 1 year ago
docker pull risingwavelabs/wavekit:v0.4.0