fix: metric receive storage size (#56)

Author: Sunny6889

metric_monitor/REMOTE_WRITE_WITH_THANOS.md

@@ -182,7 +182,7 @@ Core configuration for Thanos Receive in [thanos-receive.yml](./docker-compose/t
 ##### 1. Storage configuration
 - Local Storage:
   `../receive-data:/receive/data` maps the host directory for metric TSDB storage.
-  - Retention Policy: `--tsdb.retention=30d` auto-purges data older than 30 days. As tested, it takes about **6GB of disk space per month for one java-tron(v4.7.6+) FullNode**.
+  - Retention Policy: The `--tsdb.retention=30d` flag automatically purges data older than 30 days. Based on testing with a java-tron(v4.7.6+) FullNode using a 1-second metric scrape interval, storage consumption averages approximately **8GB of disk space per month**.
 
 - External Storage:
   `../conf:/receive` mounts configuration files. The `--objstore.config-file` flag enables long-term storage in MinIO/S3-compatible buckets. In this case, it is [bucket_storage_bucket.yml](conf/bucket_storage_bucket.yml).

metric_monitor/conf/prometheus-remote-write.yml

@@ -35,14 +35,14 @@ remote_write:
       X-Service-Group: "tron-fullnode-group1"
     remote_timeout: 10s
     queue_config:
-      capacity: 2500
+      capacity: 25000
       max_shards: 200 # the maximum number of shards, or parallelism, Prometheus will use for each remote-write queue
       min_shards: 1
-      max_samples_per_send: 500
+      max_samples_per_send: 5000
       batch_send_deadline: 5s
-      min_backoff: 30ms
+      min_backoff: 200ms
       max_backoff: 5s
     metadata_config:
       send: true
       send_interval: 1s # How frequently metric metadata is sent to remote storage.
-      max_samples_per_send: 500
+      max_samples_per_send: 5000