GRAYLOG - Chapter 8, Exercise 2 Solution
==========================================================
Why correlationId, Not requestId, for RMS Jobs

PROBLEM
-------
In Scenario 2, explain why correlationId is the right field to reach
for in Step 2, rather than requestId.

SOLUTION
--------
Chapter 4 established the real scope difference between these two
fields: requestId correlates the log lines from ONE single HTTP
request, while correlationId operates one level up, correlating one
item or job across CROSS-SERVICE steps - the chapter's own real example
being a Flux pipeline run touching several distinct services in
sequence.

An RMS integration job failing overnight is exactly this second kind of
thing - it's described in Scenario 2 as real infrastructure-level
activity on the rms-integration-cluster, not a single web request. A
job like this plausibly involves multiple internal steps, potentially
across multiple services, all belonging to the same overall job.

ANSWER: correlationId is the right field because an RMS integration job
is a cross-service, multi-step unit of work, which is exactly what
correlationId (not the narrower, single-request-scoped requestId) is
designed to trace, per Chapter 4's own real scope distinction.

----
WHY THIS WORKS AS AN ANSWER

This directly applies Chapter 4's own explicit correlationId-vs-
requestId scope comparison to a concrete real scenario, reinforcing
that the choice between the two fields depends on recognizing whether
the thing being traced is a single request or a broader, multi-step
job - a judgment call this chapter's own scenario was built specifically
to exercise.