Eduwer Camacaro

process latency on this branch: ``` ❯ curl -s localhost:1822/metrics | grep process_latency | grep core kafka_stream_thread_process_latency_avg{application_id="my-cluster",kafka_version="3.7.0",thread_id="my-cluster-1-core-StreamThread-1",topology="core",} 0.2539119774508039 kafka_stream_thread_process_latency_avg{application_id="my-cluster",kafka_version="3.7.0",thread_id="my-cluster-1-core-StreamThread-2",topology="core",} 0.2518005141691956 kafka_stream_thread_process_latency_max{application_id="my-cluster",kafka_version="3.7.0",thread_id="my-cluster-1-core-StreamThread-1",topology="core",} 3.0 kafka_stream_thread_process_latency_max{application_id="my-cluster",kafka_version="3.7.0",thread_id="my-cluster-1-core-StreamThread-2",topology="core",} 2.0 ```

Naming for user task node

1

https://github.com/littlehorse-enterprises/littlehorse/blob/master/schemas/wf_spec.proto#L192

Cover user task reassignment hooks with a end-to-end test

1

See this commit: https://github.com/littlehorse-enterprises/littlehorse/commit/4150021a22e1a83acc1cb7438d63d5563e4805f0 We should create an e2e that cover user task reassignment. we rolled back because it is taking too long.

Newly created principals should not surpass those held by the principal who is creating them.

Measure Metrics Aggregator performance.

1

### Context Workflow metrics are calculated on a per-partition basis and then aggregated into a repartition store (see PartitionMetricsModel). To avoid sending many records into the repartition topic, we send...

This PR introduced a new way to do retries in the internal grpc client side: https://github.com/littlehorse-enterprises/littlehorse/pull/872 We need to implement some backoff policy for these retries in order to avoid...

…tric levels

It would be helpful to see all of the details associated with a sleep node: - Sleep time - Remaining time