davidradl commented on code in PR #26107:
URL: https://github.com/apache/flink/pull/26107#discussion_r1945011019


##########
docs/layouts/shortcodes/generated/forst_native_metric_configuration.html:
##########
@@ -0,0 +1,246 @@
+<table class="configuration table table-bordered">
+    <thead>
+        <tr>
+            <th class="text-left" style="width: 20%">Key</th>
+            <th class="text-left" style="width: 15%">Default</th>
+            <th class="text-left" style="width: 10%">Type</th>
+            <th class="text-left" style="width: 55%">Description</th>
+        </tr>
+    </thead>
+    <tbody>
+        <tr>
+            
<td><h5>state.backend.forst.metrics.actual-delayed-write-rate</h5></td>
+            <td style="word-wrap: break-word;">false</td>
+            <td>Boolean</td>
+            <td>Monitor the current actual delayed write rate. 0 means no 
delay.</td>
+        </tr>
+        <tr>
+            <td><h5>state.backend.forst.metrics.background-errors</h5></td>
+            <td style="word-wrap: break-word;">false</td>
+            <td>Boolean</td>
+            <td>Monitor the number of background errors in RocksDB.</td>
+        </tr>
+        <tr>
+            <td><h5>state.backend.forst.metrics.block-cache-capacity</h5></td>
+            <td style="word-wrap: break-word;">false</td>
+            <td>Boolean</td>
+            <td>Monitor block cache capacity.</td>
+        </tr>
+        <tr>
+            
<td><h5>state.backend.forst.metrics.block-cache-pinned-usage</h5></td>
+            <td style="word-wrap: break-word;">false</td>
+            <td>Boolean</td>
+            <td>Monitor the memory size for the entries being pinned in block 
cache.</td>
+        </tr>
+        <tr>
+            <td><h5>state.backend.forst.metrics.block-cache-usage</h5></td>
+            <td style="word-wrap: break-word;">false</td>
+            <td>Boolean</td>
+            <td>Monitor the memory size for the entries residing in block 
cache.</td>
+        </tr>
+        <tr>
+            <td><h5>state.backend.forst.metrics.compaction-pending</h5></td>
+            <td style="word-wrap: break-word;">false</td>
+            <td>Boolean</td>
+            <td>Track pending compactions in RocksDB. Returns 1 if a 
compaction is pending, 0 otherwise.</td>
+        </tr>
+        <tr>
+            
<td><h5>state.backend.forst.metrics.cur-size-active-mem-table</h5></td>
+            <td style="word-wrap: break-word;">false</td>
+            <td>Boolean</td>
+            <td>Monitor the approximate size of the active memtable in 
bytes.</td>
+        </tr>
+        <tr>
+            
<td><h5>state.backend.forst.metrics.cur-size-all-mem-tables</h5></td>
+            <td style="word-wrap: break-word;">false</td>
+            <td>Boolean</td>
+            <td>Monitor the approximate size of the active and unflushed 
immutable memtables in bytes.</td>
+        </tr>
+        <tr>
+            
<td><h5>state.backend.forst.metrics.estimate-live-data-size</h5></td>
+            <td style="word-wrap: break-word;">false</td>
+            <td>Boolean</td>
+            <td>Estimate of the amount of live data in bytes (usually smaller 
than sst files size due to space amplification).</td>
+        </tr>
+        <tr>
+            <td><h5>state.backend.forst.metrics.estimate-num-keys</h5></td>
+            <td style="word-wrap: break-word;">false</td>
+            <td>Boolean</td>
+            <td>Estimate the number of keys in RocksDB.</td>
+        </tr>
+        <tr>
+            
<td><h5>state.backend.forst.metrics.estimate-pending-compaction-bytes</h5></td>
+            <td style="word-wrap: break-word;">false</td>
+            <td>Boolean</td>
+            <td>Estimated total number of bytes compaction needs to rewrite to 
get all levels down to under target size. Not valid for other compactions than 
level-based.</td>

Review Comment:
   nit: needs -> needed
   Not valid for other compactions than level-based -> Only valid for 
level-based compaction



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to