Closed
Description
Describe the bug
Running a worker with the histogram bucket overrides config below gives the expected custom bucket boundaries on temporal_request_latency_seconds_bucket
and temporal_long_request_latency_seconds_bucket
, but not on temporal_workflow_task_execution_latency
.
histogramBucketOverrides: {
request_latency: [3, 31, 314, 3141, 31415, 314159],
workflow_task_execution_latency: [3, 31, 314, 3141, 31415, 314159],
},
Modifying this block so that views for overrides are initialized before the default views gives me the expected bucket boundaries… But the comment above that code make it sound like there might be drawbacks at doing so.