refresh interval set to 30s

Signed-off-by: Pratik Mankawde <3397372+pratikmankawde@users.noreply.github.com>

docker/telemetry/grafana/dashboards/consensus-health.json

@@ -1333,5 +1333,5 @@
   "title": "Consensus Health",
   "uid": "consensus-health",
   "description": "What this shows: Consensus health for XRPL nodes: how reliably and quickly the network agrees each ledger, and where agreement breaks down.  \u2014  Use it to: Spot stalled or slow consensus rounds and pinpoint the phase where agreement is failing.",
-  "refresh": "10s"
+  "refresh": "30s"
 }

docker/telemetry/grafana/dashboards/fee-market.json

@@ -600,5 +600,5 @@
   "title": "Fee Market & TxQ",
   "uid": "fee-market",
   "version": 1,
-  "refresh": "10s"
+  "refresh": "30s"
 }

docker/telemetry/grafana/dashboards/job-queue.json

@@ -686,5 +686,5 @@
   "title": "Job Queue Analysis",
   "uid": "job-queue",
   "version": 1,
-  "refresh": "10s"
+  "refresh": "30s"
 }

docker/telemetry/grafana/dashboards/ledger-data-sync.json

@@ -1005,5 +1005,5 @@
   },
   "title": "Ledger Data & Sync",
   "uid": "ledger-data-sync",
-  "refresh": "10s"
+  "refresh": "30s"
 }

docker/telemetry/grafana/dashboards/ledger-operations.json

@@ -562,6 +562,6 @@
   },
   "title": "Ledger Operations",
   "uid": "ledger-operations",
-  "refresh": "10s",
+  "refresh": "30s",
   "description": "What this shows: Ledger construction, validation, and storage activity and timing for this node.  \u2014  Use it to: Confirm ledgers are being built, validated, and stored on schedule and find the slow stage when they are not."
 }

docker/telemetry/grafana/dashboards/network-traffic.json

@@ -984,5 +984,5 @@
   },
   "title": "Network Traffic",
   "uid": "network-traffic",
-  "refresh": "10s"
+  "refresh": "30s"
 }

docker/telemetry/grafana/dashboards/node-health.json

@@ -5210,5 +5210,5 @@
   },
   "title": "Node Health",
   "uid": "node-health",
-  "refresh": "10s"
+  "refresh": "30s"
 }

docker/telemetry/grafana/dashboards/overlay-traffic-detail.json

@@ -763,5 +763,5 @@
   },
   "title": "Overlay Traffic Detail",
   "uid": "overlay-traffic-detail",
-  "refresh": "10s"
+  "refresh": "30s"
 }

docker/telemetry/grafana/dashboards/peer-network.json

@@ -491,5 +491,5 @@
   },
   "title": "Peer Network",
   "uid": "peer-network",
-  "refresh": "10s"
+  "refresh": "30s"
 }

docker/telemetry/grafana/dashboards/peer-quality.json

@@ -569,5 +569,5 @@
   },
   "title": "Peer Quality",
   "uid": "peer-quality",
-  "refresh": "10s"
+  "refresh": "30s"
 }

docker/telemetry/grafana/dashboards/rpc-pathfinding.json

@@ -790,5 +790,5 @@
   },
   "title": "RPC & Pathfinding",
   "uid": "rpc-pathfinding",
-  "refresh": "10s"
+  "refresh": "30s"
 }

docker/telemetry/grafana/dashboards/rpc-performance.json

@@ -1110,6 +1110,6 @@
   },
   "title": "RPC Performance",
   "uid": "rpc-performance",
-  "refresh": "10s",
+  "refresh": "30s",
   "description": "What this shows: Per-command and per-method RPC performance: call rates, error rates, and latency distributions.  \u2014  Use it to: Identify slow or failing RPC commands and track client-facing request latency."
 }

docker/telemetry/grafana/dashboards/transaction-overview.json

@@ -1105,6 +1105,6 @@
   },
   "title": "Transaction Overview",
   "uid": "transaction-overview",
-  "refresh": "10s",
+  "refresh": "30s",
   "description": "What this shows: Transaction flow through this node: receipt, processing, results, per-stage timing, and queue behavior.  \u2014  Use it to: Trace transactions from arrival to ledger, and locate stalls in processing or the queue."
 }

docker/telemetry/grafana/dashboards/validator-health.json

@@ -1144,5 +1144,5 @@
   },
   "title": "Validator Health",
   "uid": "validator-health",
-  "refresh": "10s"
+  "refresh": "30s"
 }