ca46b9fffad1 - thought about your comment and here is a solution:
Map your DB Results Import to an Object Type "Heartbeat", where result's timestamp (e.g. Import's START_TIME) is mapped to the Name / Label).
The Heartbeat object will only have its four default Attributes, and the Import will recycle these with Missing Objects Remove, after 1 sync - so new objects will be created whenever the Monitoring Import runs successfully (including its own last run), and older objects will be deleted.
Configure an Automation rule:
WHEN: Scheduled event - every n min / hours / days etc (adjustable, depending on the checkup resolution you wish to have, and other params like imports frequency etc.).
IF: objectType = Heartbeat AND Created < now(-n <d/h/m>) //again, depending on the checkup resolution you wish to have...
THEN: possible Actions: Email - send Monitoring Email
Create Jira Ticket - if needed
HTTP Request: you can create an Object or trigger any other system...
Attribute Value - set a Status or any Attribute in a corresponding object - if needed...
So - if the Monitoring Import did not run, no Heartbeat object will be created / deleted... If there are heartbeat objects which were Created before the set threshold (in the Automation rule) - this means that the Monitoring Import did not run within the set period, and an action will be triggered... 
ca46b9fffad1 - thought about your comment and here is a solution:
Map your DB Results Import to an Object Type "Heartbeat", where result's timestamp (e.g. Import's START_TIME) is mapped to the Name / Label).
The Heartbeat object will only have its four default Attributes, and the Import will recycle these with Missing Objects Remove, after 1 sync - so new objects will be created whenever the Monitoring Import runs successfully (including its own last run), and older objects will be deleted.
Configure an Automation rule:
WHEN: Scheduled event - every n min / hours / days etc (adjustable, depending on the checkup resolution you wish to have, and other params like imports frequency etc.).
IF: objectType = Heartbeat AND Created < now(-n <d/h/m>) //again, depending on the checkup resolution you wish to have...
THEN: possible Actions: Email - send Monitoring Email
Create Jira Ticket - if needed
HTTP Request: you can create an Object or trigger any other system...
Attribute Value - set a Status or any Attribute in a corresponding object - if needed...
So - if the Monitoring Import did not run, no Heartbeat object will be created / deleted... If there are heartbeat objects which were Created before the set threshold (in the Automation rule) - this means that the Monitoring Import did not run within the set period, and an action will be triggered...