A scheduled import can fail loudly or stop producing results without throwing anything. Those are different signals, and forcing both through an error tracker creates noise while still missing the quiet failure. TL;DR: use grouped error tracking for thrown exceptions and backend failures; pair it with a heartbeat monitor when the actual question is whether the import ran and produced a result. Choose full APM only when you also need trace trees across services.

System shape Best signal Noise risk Choose it when

Grouped errors plus heartbeat Exceptions plus missing-run detection Low if fingerprints and schedules are stable You operate scheduled B2B imports and want a short path to triage

Full APM plus heartbeat Exceptions, traces, and missing-run detection Higher setup and telemetry volume A failure must be followed across several services

My recommendation is conditional: start with the first shape when import failures are local to a Node.js worker and distributed trace trees would not change the…