Is your feature request related to a problem? Please describe.
Phoenix currently supports SQLite and PostgreSQL storage backends, but not MySQL databases.
Some self-hosted users (like me) already operate MySQL infrastructure and may prefer to use it instead of introducing another database.
Describe the solution you'd like
I have a working prototype that adds MySQL as a standard SQLAlchemy backend using mysql+aiomysql.
https://github.com/PsiACE/phoenix/tree/add-mysql-storage-backend
The approach is limited to self-hosted deployments and new installations: create the schema from the current SQLAlchemy models, stamp the Alembic head, and add MySQL query/upsert/type handling where needed.
I have tested OTLP ingestion, basic GraphQL queries, span descendants, trace count time series, sessions, and span costs against MySQL 8 and a MySQL-compatible backend.
I would like to know whether this is something the maintainers would be open to reviewing upstream.
Is your feature request related to a problem? Please describe.
Phoenix currently supports SQLite and PostgreSQL storage backends, but not MySQL databases.
Some self-hosted users (like me) already operate MySQL infrastructure and may prefer to use it instead of introducing another database.
Describe the solution you'd like
I have a working prototype that adds MySQL as a standard SQLAlchemy backend using
mysql+aiomysql.https://github.com/PsiACE/phoenix/tree/add-mysql-storage-backend
The approach is limited to self-hosted deployments and new installations: create the schema from the current SQLAlchemy models, stamp the Alembic head, and add MySQL query/upsert/type handling where needed.
I have tested OTLP ingestion, basic GraphQL queries, span descendants, trace count time series, sessions, and span costs against MySQL 8 and a MySQL-compatible backend.
I would like to know whether this is something the maintainers would be open to reviewing upstream.