Table of Contents


  1. Preface
  2. Monitoring jobs
  3. Monitoring Data Integration jobs
  4. Data Integration job log files
  5. Monitoring Mass Ingestion jobs
  6. Monitoring Data Accelerator for Azure jobs
  7. Monitoring Data Profiling jobs
  8. Monitoring imports and exports
  9. Monitoring file transfer jobs
  10. Monitoring elastic clusters
  11. Monitoring source control logs



File ingestion job details

File ingestion
job details

The job results for each
file ingestion
task instance display the status of the job, and success and error statistics.
To view detailed information about a
file ingestion
task, click the task name on the
My jobs
page in
Mass Ingestion
or on the
All Jobs
tab of the
Mass Ingestion
page in the
You can download the job. The following image shows the details of a
file ingestion
Job details of file ingestion jobs

Job Properties

The job properties for the file ingestion task instance display general properties about the instance.
The following table describes the job properties:
Task Name
Name of the task.
Task Type
Task type. In this case, file ingestion task.
Started By
Name of the user or schedule that started the job.
Start Time
Date and time when the job was started.
End Time
Date and time when the job completed or stopped.
The amount of time the job ran before it completed or was stopped.


The job results for the file ingestion task instance display the status of the job and error statistics.
The job results include the following properties:
Job status. A job can have one of the following statuses:
  • Running
    . The job is still running.
  • Success
    . The job completed successfully.
  • Failed
    . The job did not complete because it encountered errors
  • Aborted
    . The job was aborted.
Session Log
Allows you to download the session log file. By default, Informatica Intelligent Cloud Services stores session logs for 10 runs before it overwrites the logs with the latest runs.If you need the session logs for earlier runs, take a backup of the directory that holds the session log files.
Session log files are written to the following directory:
<Secure Agent installation directory>/apps/Data_Integration_Server/logs
Success Files
Number of files that are successfully transferred, downloaded, and uploaded to the target.
Error Files
Number of files that were not transferred to the target.
Duplicate Files
Number of files that were identified as duplicates.
Error Message
Error message, if any, that is associated with the job.

File Events

This section shows the total number of files that the file ingestion task has transferred with information about each file.
The File Events section is updated each time the
file ingestion
task transfers a file, and the state of the file updates throughout the file transfer process. You can track the progress of a file transfer based on the state of the file.
The File Events section displays the following properties for each file:
The name of the file.
File size
The size of the file in bytes.
The state of the file transfer. A file can have one of the following states:
  • Success
    . The file transfer completed successfully.
  • Failed
    . The file transfer did not complete because it encountered errors.
  • Processing
    . The file transfer is still running.
  • Duplicate
    . The task previously transferred a file with the same name, directory location, and size.
  • Interrupted
    . The file transfer is interrupted because of network issues or changed server credentials during the file transfer. Run the file ingestion task to resume the transfer of the interrupted files. This state is applicable when the file ingestion task transfers file from the advanced FTP, advanced SFTP, or advanced FTPS sources.
  • In Doubt
    . The previous task instance encountered errors while transferring the file. Applicable for tasks where the source is configured to skip duplicate files.
You can monitor the State property to track the progress of the file transfer of each file.
Transfer Type
The type of file transfer. A file can have one of the following transfer types:
  • <source_name>
    Download. The file is downloaded from source.
    is the name of the source.
  • <target_name>
    Upload. The file is uploaded to the target.
    is the name of the target.
  • Copy from Source. The
    file ingestion
    task is performing file processing actions.
  • Copy to Target. The file is transferred from a local directory to a local directory.
Start time
Date and time when the file transfer started.
The length of time to transfer the file, in milliseconds.
Applies to file events in Failed status. The message includes the reason for failure of the event based on the file transfer type.

Updated February 12, 2021