Event names that survive team boundaries

Teams adopt path metrics with good intentions, then watch charts thrash because the same handoff fires under three names. Application analytics for developer network workflows only work when identity, stage, and ownership stay consistent across boundaries.

Before you tune alerts, audit the event dictionary. Collapse synonyms, require a stable `path_stage` property, and document which retries should not inflate failure counts. Clean inputs make modest boards more useful than ornate ones.

Once the stream is trustworthy, workflow reviews become a conversation tool instead of an argument about which graph is “the real one.”