ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Goal is to lower storage and resource consumption for a low-traffic Prometheus deployment by keeping only a short local window and offloading longer-term data. The configuration involves --storage.tsdb.retention.time for local pruning, a coarser scrape_interval to reduce head block series churn, and remote_write to a separate store. Drop relabeling is also u
The actions/upload-artifact action utilizes the retention-days input to manage the lifecycle of generated files. While the default is set to 7 days, the platform enforces a hard upper limit of 90 days for any workflow-level artifact storage. This constraint presents a challenge for long-term release tracking or compliance requirements where build outputs mus
Waku Store provides historical message retrieval from a local database on full nodes. The protocol defines the store query interface but does not mandate retention duration, pruning intervals, or resource caps. Retention, pruning and max peer settings are implementation choices, so behavior differs across clients and deployments. The design goal is to operat
Goal and constraint Consider a namespace on a Pulsar 3.x cluster where recent messages must stay replayable if a deployment is rolled back. Only persistent topics backed by BookKeeper ledgers qualify, and bookie SSD capacity is limited, so retention cannot grow without bound. Tiered storage offload is available but adds retrieval latency for offloaded ledger
Our team relies on Figma's built-in version history as the rollback mechanism for design files. Restoring an earlier version is non-destructive — it copies the old state to the top of the history as a new version — so the rollback itself can be undone. That part of the behavior is well documented and works as expected. The unresolved constraint is retention.
During a recent deployment, a critical JavaScript error appeared in user sessions. Clarity’s Session Replay captures interactions, but the default 10% sample rate may miss the affected sessions. Raising the sample rate could improve visibility, yet it raises concerns about page load performance and the volume of data retained for analysis. Additionally, the
prometheus
githubactions
waku
pulsar
figma
clarity