A Microsoft platform for building enterprise-level data integration and data transformations solutions.
Starting from SSIS 2012 onwards, it is better to deploy SSIS Projects to SSIS Catalog (SSISDB database behind the scenes). That way you will have a full data on SSIS packages execution, and much more.
I personally use the following T-SQL query to retrieve SSIS packages execution info.
USE SSISDB;
GO
/*
https://docs.microsoft.com/en-us/sql/integration-services/system-views/catalog-executions-ssisdb-database?redirectedfrom=MSDN&view=sql-server-ver15
*/
SELECT duration = CONVERT(CHAR(12), DATEADD(MILLISECOND, msec + 86400000, 0), 114)
, t2.status_name, FORMAT(created_time,'yyyy-MM-dd HH:mm') AS start_time, *
FROM CATALOG.executions as x
INNER JOIN (VALUES (1, 'Created', 'Active')
, (2, 'Running', 'Active')
, (3, 'Canceled', 'Failed')
, (4, 'Failed', 'Failed')
, (5, 'Pending', 'Active')
, (6, 'Ended unexpectedly', 'Failed')
, (7, 'Succeeded', 'Succeeded')
, (8, 'Stopping', 'Active')
, (9, 'Completed', 'Failed')) as t2(status_id, status_name, status_group)
ON x.status = t2.status_id
CROSS APPLY (VALUES (DATEDIFF(millisecond, start_time, end_time))) as t(msec)
WHERE folder_name = '...'
AND project_name = '...'
AND package_name = '....dtsx'
ORDER BY execution_id DESC;