Skip to content

PostgreSQL backup tool with Point-In-Time-Recovery and restore verification

FEATURE (priorities): Update priorities

Rostislav Dugin0abc2225de62
diff --git a/backend/internal/features/monitoring/postgres/metrics/service_test.go b/backend/internal/features/monitoring/postgres/metrics/service_test.go
index 26803a0f..91a80d11 100644
--- a/backend/internal/features/monitoring/postgres/metrics/service_test.go
+++ b/backend/internal/features/monitoring/postgres/metrics/service_test.go
@@ -272,7 +272,13 @@ func Test_GetMetricsWithFilterByType_FilterWorks(t *testing.T) {
}
// Test filtering by System RAM type
- systemRamMetrics, err := service.GetMetrics(testUser, database.ID, MetricsTypeSystemRAM, from, to)
+ systemRamMetrics, err := service.GetMetrics(
+ testUser,
+ database.ID,
+ MetricsTypeSystemRAM,
+ from,
+ to,
+ )
assert.NoError(t, err)
assert.Len(t, systemRamMetrics, 1)
for _, metric := range systemRamMetrics {
@@ -287,7 +293,13 @@ func Test_GetMetricsWithFilterByType_FilterWorks(t *testing.T) {
// Test time filtering - get only recent metrics (last hour)
recentFrom := now.Add(-1 * time.Hour)
- recentRamMetrics, err := service.GetMetrics(testUser, database.ID, MetricsTypeDbRAM, recentFrom, to)
+ recentRamMetrics, err := service.GetMetrics(
+ testUser,
+ database.ID,
+ MetricsTypeDbRAM,
+ recentFrom,
+ to,
+ )
assert.NoError(t, err)
assert.Len(t, recentRamMetrics, 1) // Only the metric from 1 hour ago
assert.Equal(t, float64(2048000), recentRamMetrics[0].Value)
diff --git a/contribute/README.md b/contribute/README.md
index bf10469a..45a7f7ee 100644
--- a/contribute/README.md
+++ b/contribute/README.md
@@ -86,7 +86,6 @@ Backups flow:
Notifications flow:
- add Mattermost
-- add MS Teams
Extra:
@@ -99,6 +98,7 @@ Monitoring flow:
- add system metrics (CPU, RAM, disk, IO) (in progress by Rostislav Dugin)
- add queries stats (slowest, most frequent, etc. via pg_stat_statements)
+- add triggering backups and restores via API
- add alerting for slow queries (listen for slow query and if they reach >100ms - send message)
- add alerting for high resource usage (listen for high resource usage and if they reach >90% - send message)
- add DB size distribution chart (tables, indexes, etc.)