Question 480
A Splunk platform team observes this behavior: A team tests a SEDCMD rule on historical indexed events and concludes the change failed because old records are unchanged. Which technical principle best explains the issue?
Explanation
Correct Answer
Ingest-time SEDCMD rules affect new event processing rather than retroactively rewriting indexed history. This explains why the administrator should validate the rule on fresh input and document separate reingestion requirements for any existing records. A direct test would be: A fresh sample is transformed and existing stored records remain unchanged unless properly reindexed.
Incorrect Answers
The related but distinct situation is “An appliance embeds a transient password in a predictable raw text fragment and administrators propose deleting it in dashboards only”. SEDCMD can perform supported raw-text substitutions during ingestion; dashboard redaction is too late for stored secrets. For the stated problem, “Ingest-time SEDCMD rules affect new event processing rather than retroactively rewriting indexed history” addresses the central condition.
That interpretation fits A SEDCMD substitution intended for one sourcetype unexpectedly alters unrelated log messages after a broad stanza edit. It is not the main cause here. Confirm the correct reasoning using A fresh sample is transformed and existing stored records remain unchanged unless properly reindexed.
This alternative addresses the separate case “A transformation works on an indexer but a similar stanza on a universal forwarder has no effect”. The controlling mechanism is that configuration has to reside on a capable processing stage, not merely on any Splunk instance. The deciding requirement here is “Ingest-time SEDCMD rules affect new event processing rather than retroactively rewriting indexed history”.