Question 460
A customer asks for the reason behind the following failure: An incident dashboard loses correlation values at high load because join output limits are reached. Which explanation is strongest?
Explanation
Correct Answer
Join invokes constrained subsearch behavior and can be less suitable than aggregations, lookups, or carefully bounded alternatives. This technical distinction is illustrated by: An incident dashboard loses correlation values at high load because join output limits are reached. The recommended operational decision is: Evaluate the join command's result and time limits and redesign large correlations when necessary. Evidence should show: Stress tests show complete matched entities without hidden row truncation at the expected data volume.
Incorrect Answers
This is a valid distinction for the separate example A search is slow and an administrator immediately increases indexer CPU without examining the job details. It does not account for the reported symptom, which is governed by join invokes constrained subsearch behavior and can be less suitable than aggregations, lookups, or carefully bounded alternatives.
The competing mechanism can matter elsewhere, for instance: A scheduled report combines a broad outer search with a slow subsearch that repeats identical expensive work each run. The target problem instead rests on join invokes constrained subsearch behavior and can be less suitable than aggregations, lookups, or carefully bounded alternatives.
This is a valid distinction for the separate example Job inspector exposes a remote peer delay that does not appear in the local CPU chart. It does not account for the reported symptom, which is governed by join invokes constrained subsearch behavior and can be less suitable than aggregations, lookups, or carefully bounded alternatives.