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?