> ## 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 the number of historic job logs that fulfill the given parameters. Takes the same parameters as the [Get Job Logs](https://docs.camunda.org/manual/7.22/reference/rest/history/job-log/get-job-log-query/) method. ## OpenAPI ````yaml GET /history/job-log/count 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/count: get: tags: - Historic Job Log summary: Get Job Log Count description: >- Queries for the number of historic job logs that fulfill the given parameters. Takes the same parameters as the [Get Job Logs](https://docs.camunda.org/manual/7.22/reference/rest/history/job-log/get-job-log-query/) method. operationId: getHistoricJobLogsCount 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. responses: '200': content: application/json: schema: $ref: '#/components/schemas/CountResultDto' examples: example-1: summary: GET `/history/job-log/count?jobId=aJobId` description: GET `/history/job-log/count?jobId=aJobId` value: count: 1 description: Request successful. '400': content: application/json: schema: $ref: '#/components/schemas/ExceptionDto' description: Returned if some of the query parameters are invalid. components: schemas: CountResultDto: type: object properties: count: type: integer format: int64 description: The number of matching instances. 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 ````