temporalio / temporalio/temporal

Support for HTTPS metrics endpoint on OSS Temporal

Open
#7,780 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
23.2k
Forks
1.9k
Avg merge
2d 8h
Merged PRs (30d)
228

Description

Is your feature request related to a problem? Please describe.

We are self-hosting OSS Temporal in our Kubernetes cluster. We are required to expose only secure APIs, including metrics APIs, from any container running in our cluster.

Describe the solution you'd like
A feature that allows to load a dedicated certificate different from the Temporal's inter-node and frontend certificate for the metrics endpoint.

For example, we would like to run other services within the mesh and run self-hosted Temporal with native TLS, and with that model, Prometheus is already loaded with the service-mesh certificate to scrape from other containers. So, if Temporal can serve the metrics endpoint with the same certificate, it would be straightforward for Prometheus to access the HTTPS metrics endpoint.

Describe alternatives you've considered
Alternatives are really tough, tried to put the temporal inside the service mesh, didn't work well.

Additional context
-N/A-

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Begin by locating Temporal's metrics endpoint and the existing certificate-loading paths for inter-node and frontend traffic; done means the metrics endpoint can serve HTTPS with a dedicated certificate for Prometheus to scrape.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes, prometheus
Domain
infrastructure, observability, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.