dhiaayachi / temporal

Temporal service
https://docs.temporal.io
MIT License
0 stars 0 forks source link

System search attributes to find workflows that are backoff retrying an activity #417

Open dhiaayachi opened 2 months ago

dhiaayachi commented 2 months ago

Is your feature request related to a problem? Please describe. It’s hard to find out those workflows . The only way is through logs but sometimes logs are too noisy to read and search when production is running in outrage.

Describe the solution you'd like Provide system search attributes like historyLength, eg retryingActivityType to help searching in webUI

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Add any other context or screenshots about the feature request here.

dhiaayachi commented 1 month ago

Thank you for your feature request. It's great to hear that you are thinking about how to improve the workflow search experience.

The Temporal Web UI currently uses the standard search attributes for filtering workflows. As you pointed out, this can be insufficient when dealing with specific production scenarios.

While we are working on more advanced search capabilities for the Web UI, you can use the Temporal CLI and custom search attributes as a workaround for now.

You can set custom search attributes, such as historyLength and retryingActivityType, to the workflow execution. You can then search for workflows based on those attributes using the Temporal CLI. This would enable you to find the specific workflow executions that you need.

You can find more information about custom search attributes in the Temporal documentation here.

Please let us know if you have any other questions.

dhiaayachi commented 1 month ago

Thank you for your feature request. We understand the need for enhanced search capabilities within the Temporal web UI to streamline workflow identification.

While we don't have direct UI-based search options for attributes like historyLength or retryingActivityType yet, you can use Search Attributes to achieve a similar outcome.

Here's how:

  1. Define Custom Search Attributes: You can create custom search attributes like retryCount or workflowVersion that reflect the information you need.
  2. Set Attributes during Workflow Start: Include your custom search attributes when starting a workflow.
  3. Utilize Search Attributes for Filtering: Use the Temporal CLI or the ListWorkflowExecutions API to filter workflows based on these attributes.

You can find more details on how to use Search Attributes here.

We appreciate your suggestion and will consider adding UI-based search capabilities in future releases.