Traceability > Audit Logs > Jobs

Technical Overview

• There are several ways to launch a job in the Product-Live platform:
  • Using the app.product-live.com UI
    • In the Action menu, several actions are available, each corresponding to a job
  • Using the settings.product-live.com UI:
    • In the Data Factory section, users can create and launch jobs
    • When a job is created, a periodicity can be added to it, which will ensure the job runs at regular intervals
  • Using the public (calcifer) API
    • Through the job execution endpoint
• Launching a job, creates a job instance which represents a single execution of the job. The execution is not started right away, but it is added to a queue. We distinguish between the events of queueing an execution and its actual start. For now only the first event (job.queue) is logged.
• When an execution completes, a log is emitted (job.end).

Audit Logs

Audit Log	Description
job.queue	A job instance has been queued for execution
job.end	The execution of a job instance has completed

job.queue

• Description: A job instance was created and queued for execution.

• Details:

  • accountId: The account of the user that launched the job
  • userId: The user that launched the job, not always available
  • jobOwnerAccountId: The account of the owner of the job
  • actionOrigin: The origin of the action (value may be: APP, SETTINGS, PERIODIC, API, PUBLICATION, UNKOWN)
  • jobId: The id of the job
  • jobType: The type of the job (USER, SYSTEM)
  • jobKey: The key of the job, when its a USER job
  • jobTitle : The title of the job, when its a USER job
  • jobPeriodicity: The periodicity of the job, when its a USER job
  • systemJobType: The type of the system job (table-delete-items-system, refresh-items-system, table-import-items-system), when its a SYSTEM job
  • pipelineId: The id of the pipeline
  • jobInstanceId: The id of the job instance

• Example

{
  "Id": "3fd28929-228d-11ef-91f5-002248824020",
  "TimeGenerated [UTC]": "2024-06-04T16:12:33.7430000Z",
  "EntityType": "job",
  "PlType": "job.queued",
  "Version": 2,
  "Details": {
    "accountId":"4201",
    "userId":"5",
    "jobOwnerAccountId":"4201",
    "jobId":"67a0bdc2d57ed1d3c254713b",
    "jobKey":"export-items_api_1",
    "jobTitle":"export-items_api",
    "jobType":"USER",
    "jobInstanceId":"67a0bf50d57ed1d3c254713c",
    "pipelineId":"674f4b87761a6b19c9f0ee74",
    "jobPeriodicity":[],
    "actionOrigin":"API"
  }
}

job.end

• Description: A job instance has finished execution.

• Details:

  • accountId: The account of the user that launched the job
  • userId: The user that launched the job, not always available
  • jobOwnerAccountId: The account of the owner of the job
  • jobInstanceId: The id of the job instance
  • jobInstanceStatus : The status of the job instance once completed (COMPLETED, COMPLETED_WITH_ERRORS, TIMED_OUT, FAILED, TERMINATED, UNKNOWN, REMOVED, USER_ERROR)
  • jobInstanceUpdatedAt : The timestamp when the job instance was updated, in the format of an ISO string.
  • jobInstanceStartAt : The timestamp when the job instance started execution, in the format of an ISO string.
  • jobInstanceEndAt : The timestamp when the job instance completed execution, in the format of an ISO string.
  • jobId: The id of the job
  • jobTitle : The title of the job
  • pipelineId: The id of the pipeline

• Example

{
  "Id": "3fd28929-228d-11ef-91f5-002248824020",
  "TimeGenerated [UTC]": "2024-06-04T16:12:33.7430000Z",
  "EntityType": "job",
  "PlType": "job.end",
  "Version": 2,
  "Details": {
    "accountId": "4201",
    "userId": "5",
    "jobOwnerAccountId": "4201",
    "jobId": "675abb0fd17621b8c0460d09",
    "jobTitle": "init-items-multilang-fournisseur",
    "jobInstanceId": "67a0928eeda50fbacb06cac7",
    "jobInstanceStatus": "COMPLETED",
    "jobInstanceUpdatedAt": "2025-02-03T09:55:30.0070000Z",
    "jobInstanceStartAt": "2025-02-03T09:55:26.0580000Z",
    "jobInstanceEndAt": "2025-02-03T09:55:29.3010000Z",
    "pipelineId": "674f4b87761a6b19c9f0ee74"
  }
}