# Metrics not being emitted

**URL:** <https://community.temporal.io/t/metrics-not-being-emitted/1698>\
**Category:** Community Support\
**Created:** [March 11, 2021, 11:48am UTC](https://community.temporal.io/t/metrics-not-being-emitted/1698 "2021-03-11T11:48:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![claude](https://avatars.discourse-cdn.com/v4/letter/c/0ea827/32.png) [@claude](https://community.temporal.io/u/claude)\
**Post date:** [March 11, 2021, 11:48am UTC](https://community.temporal.io/t/metrics-not-being-emitted/1698/1 "2021-03-11T11:48:54Z")

</div>

Hello,

I’m trying to emit temporal metrics from our Kubernetes deployment to Datadog and followed the same approach that was done for cadence by adding the following to the annotations:

[ad.datadoghq.com/temporal-frontend.check\_names:](http://ad.datadoghq.com/temporal-frontend.check_names:) ‘[“openmetrics”]’  
[ad.datadoghq.com/temporal-frontend.init\_configs:](http://ad.datadoghq.com/temporal-frontend.init_configs:) ‘[{“skip\_proxy”:true}]’  
[ad.datadoghq.com/temporal-frontend.instances:](http://ad.datadoghq.com/temporal-frontend.instances:) ‘[{“prometheus\_url”: “http://%%host%%:9090/metrics”,“namespace”: “temporal”,“metrics”: [“workflow\*”,“temporal\_requests\*”,“fail\*”,“complete\*”,“schedule\*”]}]’

However, there are a lot of metrics missing in temporal that are available in cadence. For example, there is no temporal.worflow\_failed as there is a cadence.workflow\_failed and I see it in the code below.

Temporal Metrics: [temporal/defs.go at master · temporalio/temporal · GitHub](https://github.com/temporalio/temporal/blob/master/common/metrics/defs.go#L2292)

Any ideas about this?

Thanks

---

<div class="post-metadata">

**Author:** ![derek](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/derek/32/245_2.png) [@derek](https://community.temporal.io/u/derek)\
**Post date:** [March 11, 2021, 7:31pm UTC](https://community.temporal.io/t/metrics-not-being-emitted/1698/2 "2021-03-11T19:31:54Z")

</div>

i’m not sure about datadog and how they handles things, but internally we use prometheus operator with kubernetes and the kubernetes mixin … we’ve seen some metrics get missed when there are some collisions between metrics / labels that we have to correct for at ingestion time or we lose things - for instance, there are kubernetes namespaces and temporal namespaces - if we’re applying kubernetes based labels to metrics emitted from temporal then that collision needs to be handled. with prometheus we do that via scrape\_config. maybe there’s something similar going on in your datadog setup?