Different client worker metric names for Java and Go SDKs

Community Support
, ,
1

Hi,

I’m wondering is this a normal behaviour and if it can be somehow influenced.

Go SDK metric: temporal_activity_schedule_to_start_latency_bucket
Java SDK metric: temporal_activity_schedule_to_start_latency_seconds_bucket

Those 2 are the same metric where for java seconds is added. Is there a parameter which can unify the metric naming to temporal_activity_schedule_to_start_latency_bucket for the SDKs or we have to handle Java and Go metrics differently?

Thanks,
A

2

This has recently been fixed in Support OpenMetric-style naming by cretz · Pull Request #756 · temporalio/sdk-go · GitHub. I just need to merge the sample at Update Tally Prometheus sample by cretz · Pull Request #191 · temporalio/samples-go · GitHub that shows how to apply the suggested Prometheus naming.

1 Like
3

thanks @Chad_Retz - will this follow into the System Worker as well?

4

I assume you mean on the server side. Unfortunately that could cause backwards incompatible metric name alterations whereas this is opt in. I will discuss the options with the server team.