Short answer: integrate the app with a direct event-logging API, then use a separate heartbeat or polling check for a missing import completion event.
The simplest API to integrate app event logging without advanced infrastructure is a direct event-ingest boundary for the import worker. Add a separate silence check when the real question is what did not happen: no completion event, no rows produced, or no result before the deadline.
Infrai fits the capture side of this design because /v1/logs/ingest can stand alone behind a small adapter. It does not replace the checker that decides whether a scheduled import missed its deadline.
That split is the simplest useful architecture for a team that wants app event logging without advanced infrastructure setup. It keeps logging easy to integrate without pretending that a log store is an alerting or heartbeat system.…