> ## Documentation Index > Fetch the complete documentation index at: https://docs.eorion.com/llms.txt > Use this file to discover all available pages before exploring further. # 获取列表 > Queries for historic job logs that fulfill the given parameters. The size of the result set can be retrieved by using the [Get Job Log Count](https://docs.camunda.org/manual/7.22/reference/rest/history/job-log/get-job-log-query-count/) method. ## OpenAPI ````yaml GET /history/job-log openapi: 3.0.2 info: title: ORION Platform REST API description: OpenApi Spec for ORION Camunda Platform REST API. version: 7.22.6-ee license: name: Apache License 2.0 url: http://www.apache.org/licenses/LICENSE-2.0.html servers: - url: http://{host}:{port}/{contextPath} description: The API server for the default process engine variables: host: default: localhost port: default: '8080' contextPath: default: engine-rest - url: http://{host}:{port}/{contextPath}/engine/{engineName} description: The API server for a named process engine variables: host: default: localhost port: default: '8080' contextPath: default: engine-rest engineName: default: default - url: '{url}' description: The API server with a custom url variables: url: default: '' security: - basicAuth: [] tags: - name: Authorization - name: Batch - name: Condition - name: Decision Definition - name: Decision Requirements Definition - name: Deployment - name: Engine - name: Event Subscription - name: Execution - name: External Task - name: Filter - name: Group - name: Historic Activity Instance - name: Historic Batch - name: Historic Decision Definition - name: Historic Decision Instance - name: Historic Decision Requirements Definition - name: Historic Detail - name: Historic External Task Log - name: Historic Identity Link Log - name: Historic Incident - name: Historic Job Log - name: Historic Process Definition - name: Historic Process Instance - name: Historic Task Instance - name: Historic User Operation Log - name: Historic Variable Instance - name: History Cleanup - name: Identity - name: Incident - name: Job - name: Job Definition - name: Message - name: Metrics - name: Migration - name: Modification - name: Process Definition - name: Process Instance - name: Signal - name: Schema Log - name: Task - name: Task Attachment - name: Task Comment - name: Task Identity Link - name: Task Local Variable - name: Task Variable - name: Telemetry - name: Tenant - name: User - name: Variable Instance - name: Version externalDocs: description: Find out more about ORION Rest API url: https://docs.eorion.com paths: /history/job-log: get: tags: - Historic Job Log summary: Get Job Logs description: >- Queries for historic job logs that fulfill the given parameters. The size of the result set can be retrieved by using the [Get Job Log Count](https://docs.camunda.org/manual/7.22/reference/rest/history/job-log/get-job-log-query-count/) method. operationId: getHistoricJobLogs parameters: - name: logId in: query schema: type: string description: Filter by historic job log id. - name: jobId in: query schema: type: string description: Filter by job id. - name: jobExceptionMessage in: query schema: type: string description: Filter by job exception message. - name: jobDefinitionId in: query schema: type: string description: Filter by job definition id. - name: jobDefinitionType in: query schema: type: string description: >- Filter by job definition type. See the [User Guide](https://docs.camunda.org/manual/7.22/user-guide/process-engine/the-job-executor/#job-creation) for more information about job definition types. - name: jobDefinitionConfiguration in: query schema: type: string description: Filter by job definition configuration. - name: activityIdIn in: query schema: type: string description: >- Only include historic job logs which belong to one of the passed activity ids. - name: failedActivityIdIn in: query schema: type: string description: >- Only include historic job logs which belong to failures of one of the passed activity ids. - name: executionIdIn in: query schema: type: string description: >- Only include historic job logs which belong to one of the passed execution ids. - name: processInstanceId in: query schema: type: string description: Filter by process instance id. - name: processDefinitionId in: query schema: type: string description: Filter by process definition id. - name: processDefinitionKey in: query schema: type: string description: Filter by process definition key. - name: deploymentId in: query schema: type: string description: Filter by deployment id. - name: tenantIdIn in: query schema: type: string description: >- Only include historic job log entries which belong to one of the passed and comma- separated tenant ids. - name: withoutTenantId in: query schema: type: boolean description: >- Only include historic job log entries that belong to no tenant. Value may only be `true`, as `false` is the default behavior. - name: hostname in: query schema: type: string description: Filter by hostname. - name: jobPriorityLowerThanOrEquals in: query schema: type: integer format: int64 description: >- Only include logs for which the associated job had a priority lower than or equal to the given value. Value must be a valid `long` value. - name: jobPriorityHigherThanOrEquals in: query schema: type: integer format: int64 description: >- Only include logs for which the associated job had a priority higher than or equal to the given value. Value must be a valid `long` value. - name: creationLog in: query schema: type: boolean description: >- Only include creation logs. Value may only be `true`, as `false` is the default behavior. - name: failureLog in: query schema: type: boolean description: >- Only include failure logs. Value may only be `true`, as `false` is the default behavior. - name: successLog in: query schema: type: boolean description: >- Only include success logs. Value may only be `true`, as `false` is the default behavior. - name: deletionLog in: query schema: type: boolean description: >- Only include deletion logs. Value may only be `true`, as `false` is the default behavior. - name: sortBy in: query schema: enum: - timestamp - jobId - jobDefinitionId - jobDueDate - jobRetries - jobPriority - activityId - executionId - processInstanceId - processDefinitionId - processDefinitionKey - deploymentId - hostname - occurrence - tenantId type: string description: |- Sort the results lexicographically by a given criterion. Must be used in conjunction with the sortOrder parameter. - name: sortOrder in: query schema: enum: - asc - desc type: string description: >- Sort the results in a given order. Values may be asc for ascending order or desc for descending order. Must be used in conjunction with the sortBy parameter. - name: firstResult in: query schema: type: integer description: >- Pagination of results. Specifies the index of the first result to return. - name: maxResults in: query schema: type: integer description: >- Pagination of results. Specifies the maximum number of results to return. Will return less results if there are no more results left. responses: '200': content: application/json: schema: type: array items: $ref: '#/components/schemas/HistoricJobLogDto' examples: example-1: summary: GET `/history/job-log?jobId=aJobId` description: GET `/history/job-log?jobId=aJobId` value: - id: someId timestamp: 2015-01-15T15:22:20.000+0200 removalTime: 2018-02-10T14:33:19.000+0200 jobId: aJobId jobDefinitionId: aJobDefinitionId activityId: serviceTask jobType: message jobHandlerType: async-continuation jobDueDate: null jobRetries: 3 jobPriority: 15 jobExceptionMessage: null failedActivityId: null executionId: anExecutionId processInstanceId: aProcessInstanceId processDefinitionId: aProcessDefinitionId processDefinitionKey: aProcessDefinitionKey deploymentId: aDeploymentId rootProcessInstanceId: aRootProcessInstanceId tenantId: null hostname: aHostname batchId: aBatchId creationLog: true failureLog: false successLog: false deletionLog: false description: Request successful. '400': content: application/json: schema: $ref: '#/components/schemas/ExceptionDto' description: >- Returned if some of the query parameters are invalid, for example if a `sortOrder` parameter is supplied, but no `sortBy`. See the [Introduction](https://docs.camunda.org/manual/7.22/reference/rest/overview/#error-handling) for the error response format. components: schemas: HistoricJobLogDto: type: object properties: id: type: string nullable: true description: The id of the log entry. timestamp: type: string format: date-time nullable: true description: The time when the log entry has been written. removalTime: type: string format: date-time nullable: true description: >- The time after which the log entry should be removed by the History Cleanup job. Default format `yyyy-MM-dd'T'HH:mm:ss.SSSZ`. For further info see the [docs](https://docs.camunda.org/manual/7.22/reference/rest/overview/date-format/) jobId: type: string nullable: true description: The id of the associated job. jobDueDate: type: string format: date-time nullable: true description: The date on which the associated job is supposed to be processed. jobRetries: type: integer format: int32 nullable: true description: The number of retries the associated job has left. jobPriority: type: integer format: int64 nullable: true description: The execution priority the job had when the log entry was created. jobExceptionMessage: type: string nullable: true description: >- The message of the exception that occurred by executing the associated job. failedActivityId: type: string nullable: true description: >- The id of the activity on which the last exception occurred by executing the associated job. jobDefinitionId: type: string nullable: true description: >- The id of the job definition on which the associated job was created. jobDefinitionType: type: string nullable: true description: >- The job definition type of the associated job. See the [User Guide](https://docs.camunda.org/manual/7.22/user-guide/process-engine/the-job-executor/#job-creation) for more information about job definition types. jobDefinitionConfiguration: type: string nullable: true description: The job definition configuration type of the associated job. activityId: type: string nullable: true description: The id of the activity on which the associated job was created. executionId: type: string nullable: true description: The execution id on which the associated job was created. processInstanceId: type: string nullable: true description: >- The id of the process instance on which the associated job was created. processDefinitionId: type: string nullable: true description: >- The id of the process definition which the associated job belongs to. processDefinitionKey: type: string nullable: true description: >- The key of the process definition which the associated job belongs to. deploymentId: type: string nullable: true description: The id of the deployment which the associated job belongs to. rootProcessInstanceId: type: string nullable: true description: >- The process instance id of the root process instance that initiated the process which the associated job belongs to. tenantId: type: string nullable: true description: The id of the tenant that this historic job log entry belongs to. hostname: type: string nullable: true description: |- The name of the host of the Process Engine where the job of this historic job log entry was executed. batchId: type: string nullable: true description: >- The ID of the batch associated with this job. `null` if no batch is associated with this job. The following jobs are associated with batches: * Seed Jobs * Monitor Jobs * Batch Execution Jobs creationLog: type: boolean nullable: true description: >- A flag indicating whether this log represents the creation of the associated job. failureLog: type: boolean nullable: true description: >- A flag indicating whether this log represents the failed execution of the associated job. successLog: type: boolean nullable: true description: >- A flag indicating whether this log represents the successful execution of the associated job. deletionLog: type: boolean nullable: true description: >- A flag indicating whether this log represents the deletion of the associated job. ExceptionDto: title: ExceptionDto type: object properties: type: type: string nullable: true description: An exception class indicating the occurred error. message: type: string nullable: true description: A detailed message of the error. code: type: number description: >- The code allows your client application to identify the error in an automated fashion. You can look up the meaning of all built-in codes and learn how to add custom codes in the [User Guide](https://docs.camunda.org/manual/7.22/user-guide/process-engine/error-handling/#exception-codes). securitySchemes: basicAuth: type: http scheme: basic ````