Move Elixir observability dashboard to Phoenix#29
Merged
frantic-openai merged 2 commits intomainfrom Mar 5, 2026
Merged
Conversation
Summary: - replace the custom TCP observability server with a Phoenix and Bandit endpoint while preserving the existing JSON API routes - add a LiveView operations dashboard backed by a shared presenter and Phoenix PubSub updates - serve dashboard styling as a static CSS asset and document the new web stack and build flow Rationale: - keep the optional observability surface maintainable without carrying custom HTTP parsing and routing code - preserve the repo's no-node workflow while giving the dashboard a real Phoenix runtime and cleaner asset boundaries Tests: - make -C elixir all Co-authored-by: Codex <codex@openai.com>
Summary: - serve the dashboard CSS and Phoenix JavaScript bundles from compiled modules instead of filesystem-backed Plug.Static paths - allow form-style POST requests to pass through Plug.Parsers so the observability API keeps its existing 202 and 405 behavior - extend the endpoint tests and verify the built escript serves the asset URLs and refresh routes correctly Rationale: - the shipped escript cannot rely on dependency priv directories or app static files being present on disk at runtime - operational curl scripts previously posted empty form bodies, so the Phoenix parser needs to preserve that compatibility Tests: - make -C elixir all - ./bin/symphony --i-understand-that-this-will-be-running-without-the-usual-guardrails --port 40123 - curl -si http://127.0.0.1:40123/dashboard.css - curl -si http://127.0.0.1:40123/vendor/phoenix/phoenix.js - curl -si -X POST -d '' http://127.0.0.1:40123/api/v1/refresh - curl -si -X POST -d '' http://127.0.0.1:40123/api/v1/state Co-authored-by: Codex <codex@openai.com>
| @@ -0,0 +1,32 @@ | |||
| defmodule SymphonyElixirWeb.Endpoint do | |||
There was a problem hiding this comment.
elixir/lib/symphony_elixir_web/error_json.ex
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
2 participants
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.
Context
Replace the custom Elixir observability TCP server with Phoenix while keeping the shipped escript and existing operational API calls working the same way they did before.
TL;DR
Move the Elixir observability dashboard and API onto Phoenix without breaking the escript or curl workflows.
Summary
Alternatives
Test Plan
make -C elixir allmix -C elixir test test/symphony_elixir/extensions_test.exs./bin/symphony --i-understand-that-this-will-be-running-without-the-usual-guardrails --port 40123curl -si http://127.0.0.1:40123/dashboard.csscurl -si http://127.0.0.1:40123/vendor/phoenix/phoenix.jscurl -si -X POST -d '' http://127.0.0.1:40123/api/v1/refreshcurl -si -X POST -d '' http://127.0.0.1:40123/api/v1/state