Join keys

Finds the shared label — pod, service, namespace, or similar — that names the same thing on both the Log10x side and the customer metric backend. Without a shared label, the two cannot be compared safely. Picks the best match from values that appear on both sides; when nothing matches, returns "no shared label" instead of guessing. Usually called automatically by Correlate and Translate.

Example

"join key for logs ↔ metrics"

Found service (matches in 87% of overlap). Also considered: pod (54% — too many gone replicas), namespace (100% — too coarse, only 3 values), tenant (no shared values in window).

More to ask

• "re-run join keys, force refresh"
• "why did pod lose to service?"
• "join keys with 10m window"

Prerequisites

LOG10X_CUSTOMER_METRICS_URL configured.

Tool schema (advanced)

Field	Type	Required	Default	Description
candidate_labels	string[]	no	all	Labels to check. Omit to try all, preferred ones first.
minimum_jaccard	number	no	0.7	How closely the label values must overlap to count as a match. Lower to 0.5 when exploring, 0.3 in noisy environments with stale historical values.
window	string	no	—	Time window for which label values to compare (e.g., 10m, 1h). Ignores values from decommissioned pods or old replays. Recommended: 10m steady-state, 1h bursty. Alias: timeRange.
timeRange	string	no	—	Alias for window for consistency with the other tools.
force_refresh	boolean	no	false	Bypass the session cache.
environment	string	no	—	Environment nickname.