Prom metrics missing using python worker and go workflow

Community Support
,
1

Hi,

I have a temporal dev env in k8s, I am seeing temporal_activity_schedule_to_start_latency metrics, but only in namespace temporal_system, instead of my own workflow namespaces.

I am using python worker who talk to go workflow, it seems worker is the emitting the specific metric. Thus I wonder if I need special setting/configurations when setting up python worker in code/deploy it in k8s?

2

Do you have SDK metrics enabled and are you looking at SDK metrics?
Temporal server (worker service that runs internal workflows) is going to emit SDK metrics for workflows that run in temporal-system internal namespace only, yes.