Correlation keys that survive service renames
Service names change; join keys should not. A short note on durable identifiers for infrastructure event analytics.
Display names are for humans. Correlation keys are for machines that must still join last quarter’s deploy events to this week’s capacity shift.
We favour opaque, stable identifiers emitted at the edge and carried through application analytics unchanged. Human-readable labels live as properties, not as the join field.
That habit makes Event Intake Mapping and Incident Trail Reconstruction far cheaper the second time you need them.