Question 70
The production review includes this finding: At a retail distribution site during an endpoint rollout, reviewers observe the following: Application logs use UTC but dashboards show events shifted by several hours because Splunk guesses local time. What principle should guide the diagnosis?
Explanation
Correct Answer
Event-time correctness depends on the timestamp format and timezone assigned during parsing. The actionable correction is configure a suitable timezone interpretation and timestamp extraction for that sourcetype. Evidence of correct operation is A known UTC timestamp indexes at the expected absolute event time.
Incorrect Answers
This option serves the scenario “A device log contains no parsable event-time field and the administrator treats search-time formatting as a complete fix”. Ingest time and event occurrence time can differ; an absent source timestamp cannot be reconstructed from display format alone. The present scenario is distinguished by “Event-time correctness depends on the timestamp format and timezone assigned during parsing”.
This principle explains a different operational condition: A sourcetype uses a date format ambiguous between day-first and month-first, causing events to land in the wrong period. For the current issue, event-time correctness depends on the timestamp format and timezone assigned during parsing. The corresponding action is Configure a suitable timezone interpretation and timestamp extraction for that sourcetype.
The related but distinct situation is “An event arrives as raw bytes, but administrators expect indexed fields and timestamps without any parsing-stage work”. Parsing turns acquired streams into correctly bounded, time-labeled events before indexing. For the stated problem, “Event-time correctness depends on the timestamp format and timezone assigned during parsing” addresses the central condition.