chore(logs): move capture-logs management port off 8081#59213
Merged
Conversation
The local capture-logs management port collided with the temporal-ui container, which binds to 8081. Move it to 3304 so it parks next to the other Rust dev services (3301-3309) instead of fighting local infra on the 8080 range. Generated-By: PostHog Code Task-Id: b548992c-3d7e-411d-a611-8bcb3ddf4301
Contributor
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Contributor
|
🎭 Playwright didn't run on this PR — your changes touch code that could affect E2E behavior, but Playwright is opt-in via label now to keep CI cost down. Add the Most PRs don't need this. Real regressions still get caught on master and fix-forward. |
Contributor
|
Reviews (1): Last reviewed commit: "chore(logs): move capture-logs managemen..." | Re-trigger Greptile |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
|
Size Change: -3.93 kB (0%) Total Size: 118 MB 📦 View Changed
ℹ️ View Unchanged
|
benjackwhite
approved these changes
May 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The
capture-logsRust service started bybin/start-rust-serviceexportsMANAGEMENT_BIND_PORT=8081, which collides with the localtemporal-uicontainer. When both run together, the temporal UI is unreachable onlocalhost:8081(or the management endpoint fails to bind, depending on start order).The 8081 binding landed alongside an unrelated larger change and was never intended to be sticky — it can move freely.
Changes
bin/start-rust-service: setMANAGEMENT_BIND_PORT=3304forcapture-logs, parking it next to the other Rust dev services (3301 batch-import-worker, 3302 cymbal, 3303 cyclotron-janitor, 3305 embedding-worker, 3306–3309 capture variants). 3304 was the only unused slot in that adjacent range.BIND_PORT=4320for actual log ingestion is unchanged.How did you test this code?
I'm an agent — I did not run the dev stack to verify. Confirmed by inspection that:
bin/start-rust-serviceor any Rust serviceconfig.rsdefault,MANAGEMENT_BIND_PORTseparately.Recommend a reviewer brings up
hogli start(or./bin/start) withcapture-logsenabled and confirmslocalhost:8081returns the temporal UI whilecapture-logshealth/metrics respond onlocalhost:3304.Publish to changelog?
no
Docs update
No docs reference this port.
🤖 Agent context
Authored by PostHog Code (Claude Opus 4.7) from a Slack thread where the original author confirmed the 8081 binding wasn't intentional and could move anywhere. Chose 3304 over higher ports (3310+) to keep the Rust dev services contiguous; verified by grepping
bin/start-rust-serviceand the per-serviceconfig.rsdefaults that no other service claims 3304.Created with PostHog Code