search

camunda / camunda-bpm-platform

Flexible framework for workflow and decision automation with BPMN and DMN. Integration with Quarkus, Spring, Spring Boot, CDI.
https://camunda.com/
Apache License 2.0
4.13k stars 1.56k forks source link

External Task lock history #2564

Open ThorbenLindhauer opened 3 years ago

ThorbenLindhauer commented 3 years ago

This issue was imported from JIRA:

Field Value
JIRA Link CAM-13947
Reporter 5VWqRZE
What is this name? This pseudonym name was generated based on the user name in JIRA to protect the personal data of our JIRA users. You can use this identifier to search for issues by the same reporter.
Has restricted visibility comments true

User Story (Required on creation):

As a user, I can gain insights on how long external tasks were waiting before being processed.

Functional Requirements (Required before implementation):

The external task log contains information about when a task was locked and if a lock expired.

Technical Requirements (Required before implementation):

Limitations of Scope (Optional):

Hints (optional):

Original Description

In the history tables for external tasks and jobs, it would be nice to be able to see entries for when an external task or job was locked. Currently, we can only see when these are created, completed, failed, deleted.

This is useful because it would allow us to report on how long a task or external job was waiting separately from its actual processing time.

Related forum thread: https://forum.camunda.org/t/external-tasks-history/6277

Links:

ThorbenLindhauer commented 3 years ago

This comment was imported from JIRA and written by user @tasso94

Hi 5VWqRZE,

Thank you for raising this feature request.

I think it has a feasible user story, and I see it generally in the scope of the product.

Our team has not the capacity to work on this feature request any time soon. Therefore we would appreciate it if you could contribute the feature to our codebase. You can raise a pull request on GitHub, and we will provide feedback on the implementation.

Best, Tassilo

ThorbenLindhauer commented 3 years ago

This comment was imported from JIRA and written by user @tmetzke

Hi 5VWqRZE,

thanks again for bringing this up. I agree with Tassilo here that this makes sense in the scope of the product. We will consider this feature in the next planning rounds. This does not yet mean that we will build this in the near future, but we do see a certain value to it. We will keep you in the loop about any progress within this ticket here.

In the meantime, as Tassilo mentioned, if you'd like to push progress for this yourself, we are more than happy to accept a pull request in our GitHub repository. If you need any pointers to get going, let us know.

Best, Tobias