> ## 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. # 获取计数(POST) > Queries for the number of historic external task logs that fulfill the given parameters. This method takes the same message body as the [Get External Task Logs (POST)](https://docs.camunda.org/manual/7.22/reference/rest/history/external-task-log/post-external-task-log-query/) method and therefore it is slightly more powerful than the [Get External Task Log Count](https://docs.camunda.org/manual/7.22/reference/rest/history/external-task-log/get-external-task-log-query-count/) method. ## OpenAPI ````yaml POST /history/external-task-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/external-task-log/count: post: tags: - Historic External Task Log summary: Get External Task Log Count (POST) description: >- Queries for the number of historic external task logs that fulfill the given parameters. This method takes the same message body as the [Get External Task Logs (POST)](https://docs.camunda.org/manual/7.22/reference/rest/history/external-task-log/post-external-task-log-query/) method and therefore it is slightly more powerful than the [Get External Task Log Count](https://docs.camunda.org/manual/7.22/reference/rest/history/external-task-log/get-external-task-log-query-count/) method. operationId: queryHistoricExternalTaskLogsCount requestBody: content: application/json: schema: $ref: '#/components/schemas/HistoricExternalTaskLogQueryDto' examples: example-1: summary: POST `/history/external-task-log/count` value: externalTaskId: anExternalTaskId responses: '200': content: application/json: schema: $ref: '#/components/schemas/CountResultDto' examples: example-1: summary: POST `/history/external-task-log/count` description: POST `/history/external-task-log/count` 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. See the [Introduction](https://docs.camunda.org/manual/7.22/reference/rest/overview/#error-handling) for the error response format. components: schemas: HistoricExternalTaskLogQueryDto: type: object description: >- A Historic External Task Log instance query which defines a list of Historic External Task Log instances properties: logId: type: string nullable: true description: Filter by historic external task log id. externalTaskId: type: string nullable: true description: Filter by external task id. topicName: type: string nullable: true description: Filter by an external task topic. workerId: type: string nullable: true description: >- Filter by the id of the worker that the task was most recently locked by. errorMessage: type: string nullable: true description: Filter by external task exception message. activityIdIn: type: array nullable: true items: type: string description: >- Only include historic external task logs which belong to one of the passed activity ids. activityInstanceIdIn: type: array nullable: true items: type: string description: >- Only include historic external task logs which belong to one of the passed activity instance ids. executionIdIn: type: array nullable: true items: type: string description: >- Only include historic external task logs which belong to one of the passed execution ids. processInstanceId: type: string nullable: true description: Filter by process instance id. processDefinitionId: type: string nullable: true description: Filter by process definition id. processDefinitionKey: type: string nullable: true description: Filter by process definition key. tenantIdIn: type: array nullable: true items: type: string description: >- Only include historic external task log entries which belong to one of the passed and comma-separated tenant ids. withoutTenantId: type: boolean nullable: true description: >- Only include historic external task log entries that belong to no tenant. Value may only be `true`, as `false` is the default behavior. priorityLowerThanOrEquals: type: integer format: int64 nullable: true description: >- Only include logs for which the associated external task had a priority lower than or equal to the given value. Value must be a valid `long` value. priorityHigherThanOrEquals: type: integer format: int64 nullable: true description: >- Only include logs for which the associated external task had a priority higher than or equal to the given value. Value must be a valid `long` value. creationLog: type: boolean nullable: true description: >- Only include creation logs. Value may only be `true`, as `false` is the default behavior. failureLog: type: boolean nullable: true description: >- Only include failure logs. Value may only be `true`, as `false` is the default behavior. successLog: type: boolean nullable: true description: >- Only include success logs. Value may only be `true`, as `false` is the default behavior. deletionLog: type: boolean nullable: true description: >- Only include deletion logs. Value may only be `true`, as `false` is the default behavior. sorting: type: array nullable: true description: >- An array of criteria to sort the result by. Each element of the array is an object that specifies one ordering. The position in the array identifies the rank of an ordering, i.e., whether it is primary, secondary, etc. Sorting has no effect for `count` endpoints. items: type: object properties: sortBy: type: string nullable: true enum: - timestamp - externalTaskId - topicName - workerId - retries - priority - activityId - activityInstanceId - executionId - processInstanceId - processDefinitionId - processDefinitionKey - tenantId description: |- Sort the results lexicographically by a given criterion. Must be used in conjunction with the sortOrder parameter. sortOrder: type: string nullable: true enum: - asc - desc 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. 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 ````