search

uber-go / cadence-client

Framework for authoring workflows and activities running on top of the Cadence orchestration engine.
https://cadenceworkflow.io
MIT License
339 stars 128 forks source link

Tracking cache invalidation for different types of workflow depends on their runtime length #1277

Closed timl3136 closed 8 months ago

timl3136 commented 9 months ago

What changed? Added a new metrics with tag of workflow runtime type based on their timeout value.

Why? Currently the sticky cache invalidation metrics reports on only workflow level and it is difficult to identify whether that came from a short lived workflow or not. Sticky cache invalidation is important to track for the shortlived wf since high invalidation can slow the processing and increase network load significantly.

How did you test it? Tested both locally and on development environment

Potential risks This is only new metrics added.