GRAYLOG - Chapter 4, Exercise 1 Solution
==========================================================
Following a Scheduler Job Downstream

PROBLEM
-------
You've found one log line for a scheduler job with jobRunId:abc123, but
a follow-up search for jobRunId:abc123 only returns that one line, even
though you know the job triggered further downstream processing. Using
this chapter's own material, explain what to search for next.

SOLUTION
--------
This chapter's own warn-box established that jobRunId is scheduler-
specific, and that a job originating in the scheduler does NOT keep its
own jobRunId name as it propagates further into the system - it is
forwarded downstream under the different field name requestId instead.

Since the ID value itself (abc123) carries forward unchanged, only the
FIELD NAME changes once the job leaves the scheduler:

    requestId:abc123

ANSWER: Search for requestId:abc123 (the same ID value, but under the
requestId field name) rather than continuing to search jobRunId - the
trail hasn't gone cold, it has simply changed field names as the job
moved past the scheduler into the rest of the system.

----
WHY THIS WORKS AS AN ANSWER

This is a direct application of the chapter's own explicit warning about
jobRunId being forwarded downstream as requestId. Without knowing this
real, specific quirk, a reasonable person would conclude the
investigation had hit a dead end - the chapter's own point in flagging
it is exactly to prevent that false conclusion.