-
Notifications
You must be signed in to change notification settings - Fork 780
Closed
Labels
P:storage-optimizationPriority: Give operators greater control over storage and storage optimizationPriority: Give operators greater control over storage and storage optimizationindexermetrics
Milestone
Description
Feature Request
Summary
Once the indexer pruning mechanism and the corresponding gRPC service are merged, we need a way to indicate to the operator the retain heights requested by the data companion.
Suggested metrics are
block_indexer_retain_height: Requested block indexer retain heighttx_indexer_retain_height: Requested tx indexer retain heightblock_indexer_base_height: The minimum height at which we have block events (should demonstrate the effects of pruning the block indexer)tx_indexer_base_height: The minimum height at which we have transaction events (should demonstrate the effects of pruning the tx indexer)
Why do we need this feature?
This will give operators of the data companion the opporutinity to monitor whether their requested retain height was accepted an whether the events were indeed pruned.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
P:storage-optimizationPriority: Give operators greater control over storage and storage optimizationPriority: Give operators greater control over storage and storage optimizationindexermetrics