feat(su): implement prometheus #888

permaweb · Jul 23, 2024 · 87868a1 · 87868a1
1 parent 918697c
commit 87868a1
Show file tree

Hide file tree

Showing 13 changed files with 647 additions and 228 deletions.
diff --git a/servers/su/.env.example b/servers/su/.env.example
@@ -9,4 +9,5 @@ SU_DATA_DIR=/home/rocksdb
 USE_DISK=true
 MIGRATION_BATCH_SIZE=10
 DB_WRITE_CONNECTIONS=1
-DB_READ_CONNECTIONS=40
+DB_READ_CONNECTIONS=40
+ENABLE_METRICS=true
diff --git a/servers/su/Cargo.lock b/servers/su/Cargo.lock
diff --git a/servers/su/Cargo.toml b/servers/su/Cargo.toml
@@ -32,6 +32,8 @@ actix-cors = "0.6.0"
 simd-json = "0.13.10"
 futures = "0.3.30"
 rocksdb = "0.22.0"
+prometheus-client = "0.22.3"
+sysinfo = "0.30.13"
 
 [[bin]]
 name = "su"

diff --git a/servers/su/README.md b/servers/su/README.md
@@ -47,6 +47,7 @@ Create a .env file with the following variables, or set them in the OS:
 - `USE_DISK` whether or not to write and read rocksdb, this is a performance enhancement for the data storage layer
 - `SU_DATA_DIR` if `USE_DISK` is `true`, this is where rocksdb will be initialized
 - `MIGRATION_BATCH_SIZE` when running the migration binary how many to fetch at once from postgres
+- `ENABLE_METRICS` enable prometheus metrics to be available on the  `/metrics` endpoint
 
 > You can also use a `.env` file to set environment variables when running in
 > development mode, See the `.env.example` for an example `.env`
@@ -121,6 +122,7 @@ in the container.
 - `USE_DISK` whether or not to write and read rocksdb, this is a performance enhancement for the data storage layer
 - `SU_DATA_DIR` if `USE_DISK` is `true`, this is where rocksdb will be initialized
 - `MIGRATION_BATCH_SIZE` when running the migration binary how many to fetch at once from postgres
+- `ENABLE_METRICS` enable prometheus metrics to be available on the  `/metrics` endpoint