# How to specify the protocol (HTTP/gRPC) for sending OpenTelemetry metrics?

**URL:** <https://community.temporal.io/t/how-to-specify-the-protocol-http-grpc-for-sending-opentelemetry-metrics/11825>\
**Category:** Community Support\
**Tags:** python-sdk\
**Created:** [April 18, 2024, 9:48pm UTC](https://community.temporal.io/t/how-to-specify-the-protocol-http-grpc-for-sending-opentelemetry-metrics/11825 "2024-04-18T21:48:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ysl](https://avatars.discourse-cdn.com/v4/letter/y/4af34b/32.png) [@ysl](https://community.temporal.io/u/ysl)\
**Post date:** [April 18, 2024, 9:48pm UTC](https://community.temporal.io/t/how-to-specify-the-protocol-http-grpc-for-sending-opentelemetry-metrics/11825/1 "2024-04-18T21:48:25Z")

</div>

The [temporalio.runtime.OpenTelemetryConfig](https://python.temporal.io/temporalio.runtime.OpenTelemetryConfig.html) class only allows us to specify a url. How do I specify the protocol? Do I just use, for example, `grpc://localhost:4317` if I want to connect to a gRPC endpoint?

---

<div class="post-metadata">

**Author:** ![Chad\_Retz](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/chad_retz/32/1396_2.png) [@Chad\_Retz](https://community.temporal.io/u/Chad_Retz)\
**Post date:** [April 19, 2024, 11:39am UTC](https://community.temporal.io/t/how-to-specify-the-protocol-http-grpc-for-sending-opentelemetry-metrics/11825/2 "2024-04-19T11:39:15Z")

</div>

It is always assumed to be gRPC. This is the same type of URL you might provide to [OpenTelemetry OTLP Exporters — OpenTelemetry Python documentation](https://opentelemetry-python.readthedocs.io/en/latest/exporter/otlp/otlp.html).

---

<div class="post-metadata">

**Author:** ![JamieD](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/jamied/32/4980_2.png) [@JamieD](https://community.temporal.io/u/JamieD)\
**Post date:** [October 15, 2024, 8:41pm UTC](https://community.temporal.io/t/how-to-specify-the-protocol-http-grpc-for-sending-opentelemetry-metrics/11825/3 "2024-10-15T20:41:22Z")

</div>

Hmmm, why is it only grpc? It looks like I should be able to give it a HTTPS endpoint and an authorization headder to hit http in the Typescript SDK. Is the Temporal SDK enforcing that it use GRPC? Both Http and grpc are valid ways of exporting to opentelemetry.

If we use grpc, how do we setup the certificates for authentication?

---

<div class="post-metadata">

**Author:** ![Chad\_Retz](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/chad_retz/32/1396_2.png) [@Chad\_Retz](https://community.temporal.io/u/Chad_Retz)\
**Post date:** [October 15, 2024, 9:18pm UTC](https://community.temporal.io/t/how-to-specify-the-protocol-http-grpc-for-sending-opentelemetry-metrics/11825/4 "2024-10-15T21:18:33Z")

</div>

We have [an issue open](https://github.com/temporalio/sdk-core/issues/820) for OTel HTTP support, but it is gRPC only at the moment. You can set a header but we do not currently support mTLS. We can open an issue for this as well.