Skip to content

Conversation

@AAber
Copy link

@AAber AAber commented Apr 23, 2025

My company uses Temporal server as a monolith to run workflows, similar to how Airbyte do.

I configured the Temporal server to expose the metrics on port 9090 and Prometheus to scrap the metrics.
I refactored the dashboard json file to show the dashboard panels based on the metrics sent from the Temporal monolith server.
I think other users that run Temporal in this configuration will find this file useful.

What was changed

I updated the dashboard default json and added the resulting json as a new file named temporal-monolith-dashboard.json into the misc folder.

Why?

I don't run the Temporal app as a cluster I just have the Temporal server and UI (no worker/matching/history).

  1. How was this tested:
    I run Temporal in AWS EKS and I tested this json dashboard in my Prometheus Grafana Helm app that runs in the same EKS cluster.

  2. Any docs updates needed?
    I don't think so.

@CLAassistant
Copy link

CLAassistant commented Apr 23, 2025

CLA assistant check
All committers have signed the CLA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants