chore: fixed incorrect tempo config schema for podman provider

paritytech · Apr 25, 2023 · 8cb0b71 · 8cb0b71
1 parent c0da81a
commit 8cb0b71
Showing 1 changed file with 5 additions and 3 deletions.
diff --git a/javascript/packages/orchestrator/src/providers/podman/resources/configs/tempo.yaml b/javascript/packages/orchestrator/src/providers/podman/resources/configs/tempo.yaml
@@ -28,16 +28,18 @@ compactor:
     block_retention: 1h
     compacted_block_retention: 10m
 
+# v2_ suffix comes from the config schema present in the documentation here: 
+# https://grafana.com/docs/tempo/latest/configuration/#storage
 storage:
   trace:
     backend: local                     # backend configuration to use
     block:
       bloom_filter_false_positive: .05 # bloom filter false positive rate.  lower values create larger filters but fewer false positives
-      index_downsample_bytes: 1000     # number of bytes per index record
-      encoding: zstd                   # block encoding/compression.  options: none, gzip, lz4-64k, lz4-256k, lz4-1M, lz4, snappy, zstd, s2
+      v2_index_downsample_bytes: 1000     # number of bytes per index record
+      v2_encoding: zstd                   # block encoding/compression.  options: none, gzip, lz4-64k, lz4-256k, lz4-1M, lz4, snappy, zstd, s2
     wal:
       path: /tmp/tempo/wal             # where to store the the wal locally
-      encoding: snappy                 # wal encoding/compression.  options: none, gzip, lz4-64k, lz4-256k, lz4-1M, lz4, snappy, zstd, s2
+      v2_encoding: snappy                 # wal encoding/compression.  options: none, gzip, lz4-64k, lz4-256k, lz4-1M, lz4, snappy, zstd, s2
     local:
       path: /tmp/tempo/blocks
     pool: