The ccp_pg_hba_checksum metric was accidentally removed during a rebase/merge conflict resolution. This commit adds that metric back and adjusts a metrics test accordingly.

Author: dsessler7

internal/collector/generated/postgres_5m_metrics.json

@@ -35,3 +35,15 @@
           Function monitor.sequence_status() can provide more details if run directly on system.
         static_attributes:
           server: "localhost:5432"
+
+  - sql: SELECT monitor.pg_hba_checksum() AS status;
+    metrics:
+      - metric_name: ccp_pg_hba_checksum
+        value_column: status
+        description: |
+          Value of checksum monitoring status for pg_catalog.pg_hba_file_rules (pg_hba.conf).
+          0 = valid config. 1 = settings changed.
+          Settings history is available for review in the table `monitor.pg_hba_checksum`.
+          To reset current config to valid after alert, run monitor.pg_hba_checksum_set_valid(). Note this will clear the history table.
+        static_attributes:
+          server: "localhost:5432"

internal/collector/postgres_5m_metrics.yaml

@@ -17,9 +17,9 @@ func TestRemoveMetricsFromQueries(t *testing.T) {
 	err := json.Unmarshal(fiveMinuteMetrics, &fiveMinuteMetricsArr)
 	assert.NilError(t, err)
 
-	assert.Equal(t, len(fiveMinuteMetricsArr), 2)
+	assert.Equal(t, len(fiveMinuteMetricsArr), 3)
 	newArr := removeMetricsFromQueries([]string{"ccp_database_size_bytes"}, fiveMinuteMetricsArr)
-	assert.Equal(t, len(newArr), 1)
+	assert.Equal(t, len(newArr), 2)
 
 	t.Run("DeleteOneMetric", func(t *testing.T) {
 		sqlMetricsData := `[