Skip to content

expose Prometheus :7300 via enclaver ingress - #4

Open
jjeangal wants to merge 1 commit into
espresso/batcherfrom
jean/expose-batcher-metrics-7300
Open

jjeangal wants to merge 1 commit into
espresso/batcherfrom
jean/expose-batcher-metrics-7300

Conversation

@jjeangal

@jjeangal jjeangal commented Sep 15, 2026

Copy link
Copy Markdown
Member

Adds MetricsPort (7300) to the enclave ingress list so a host-side collector can scrape op-batcher's --metrics endpoint (the port is otherwise unreachable, logs escape via stdout relay, but Prometheus is pull, needing ingress).


ReadinessPort uint16 = 8338
// MetricsPort exposes op-batcher's Prometheus endpoint (--metrics.port) out of
// the enclave so a host-side collector can scrape it.
MetricsPort uint16 = 7300

@philippecamacho philippecamacho Sep 15, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So is the Prometheus service already configured to run or will this be done in another PR?

@jjeangal jjeangal Sep 15, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is so we can build an enclave image that has that port available when we run the batch poster! So the other PR that sets up Prometheus will happen in the op-deploy-combined repository.

@philippecamacho philippecamacho left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

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