# Prometheus metrics configuration confusion

**URL:** <https://community.temporal.io/t/prometheus-metrics-configuration-confusion/6592>\
**Category:** Community Support\
**Tags:** go-sdk, helm, metrics\
**Created:** [November 29, 2022, 5:28am UTC](https://community.temporal.io/t/prometheus-metrics-configuration-confusion/6592 "2022-11-29T05:28:28Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![madhu](https://avatars.discourse-cdn.com/v4/letter/m/a8b319/32.png) [@madhu](https://community.temporal.io/u/madhu)\
**Post date:** [April 4, 2023, 11:49am UTC](https://community.temporal.io/t/prometheus-metrics-configuration-confusion/6592/6 "2023-04-04T11:49:22Z")

</div>

> [@tihomir](#):
>
> you could set different configs for each role if you wanted

i think its now deprecated and removed,can you please confirm @tihomir ,

> [@Metrics endpoint not being enabled on upgrade](https://community.temporal.io/t/metrics-endpoint-not-being-enabled-on-upgrade/5247/6):
>
> The per service metrics endpoint is deprecated since v1.11.0 [Release v1.11.0 · temporalio/temporal · GitHub](https://github.com/temporalio/temporal/releases/tag/v1.11.0) And it is removed from code in 1.16.0. Please use the global config for metrics, see more here: [Temporal Cluster configuration reference | Temporal Documentation](https://docs.temporal.io/references/configuration/#metrics)

and

> **[Release v1.11.0 · temporalio/temporal](https://github.com/temporalio/temporal/releases/tag/v1.11.0)**
>
> IMPORTANT
> This release contains a serious issue (#1697). Do not use this release. Use v1.11.2 instead.
> Release Highlights
> Schema Changes
> This release includes minor schema changes for MySQL/Postgre...

But, if thats the case, its certainly a bug in the helms, because helms still seem to use per service metric configuration and has no defination for global values.

---

_[View the full topic](https://community.temporal.io/t/prometheus-metrics-configuration-confusion/6592)._