Conversation
Step 4 exercises REDACT and THROTTLE only, and the seeded rules are span DROP/SAMPLE rules that match nothing the load generator emits. The new step 6 adds four rules: DROP on logs by log.severity, trace-consistent SAMPLE for one tenant, ROUTE to cold-storage (which reroutes without counting as a drop), and DROP on a metric by metric.name. Each comes with its expected ruleset line, a pass check, and a reference run of measured values. Also notes that the Going further examples assume only the step 4 rules, and adds troubleshooting for a mistyped ROUTE destination and for SAMPLE on LOGS being ignored. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds step 6 to
deploy/sandbox/README.md: four more rules that cover the paths the step 4 REDACT/THROTTLE rules don't.drop-debug-logs: DROP LOGSlog.severityEQUALSDEBUGlog.severityvirtual fieldsample-initech-traces: SAMPLE TRACEStenant_idEQUALSinitech, rate0.25route-acme-logs-cold: ROUTE LOGStenant_idEQUALSacme→cold-storagedrop-cache-miss-metric: DROP METRICSmetric.nameEQUALSsearch.cache.missesmetric.namevirtual fieldFor each rule, the section gives the expected
ruleset updatedline, how the rule behaves, a pass check (PromQL, or adocker logsone-liner), and a reference-run table of measured values.It also:
Why
Step 4 exercises REDACT and THROTTLE only, and the seeded rules are span DROP/SAMPLE rules that match nothing the load generator emits. Before launch, every action and every signal should have a demo someone can reproduce.
How the numbers were produced
origin/main, with the 3 seeded rules and the 4 step-4 rules in place.PolicyRule, the same row the dashboard's Create rule action writes. The UI click path wasn't exercised for these four.rules_total 11 / traces 5 / logs 5 / metrics 1 / ignored 0.debug/cold, logs dropped exactly 500/s.search_cache_misses_totalstale whilepayments_requests_totalkeeps updating.RestartCountstayed at 0.Docs only; no code or config changes.
🤖 Generated with Claude Code