Scenario
Alerts disappear only for one log family after detection rule updates.
An Elastic detection rule is updated and one index set still misses alerts because the transform keeps writing the legacy ecs category
The rule is correct, but one transform pipeline still emits the previous ecs category value that the updated rule no longer matches.
What to check first
- Identify the primary failure signal in the Incident Response scenario.
- Separate visible symptoms from the underlying technical dependency.
- Describe the safest recovery path and the follow-up prevention work.
Checking checklist
- Summarize the current impact and the last known change.
- Collect direct evidence from logs, runtime state, and configuration before changing anything.
- Separate immediate recovery from permanent prevention work.
Recovery and prevention
Inspect transform output fields before weakening the rule.
Questions worth viewing together
No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.
State the root cause, the evidence that supports it, and the safest recovery direction.
The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.
Similar cases seen in the field