proxysql

History

Rene Cannao a880f1cf9d docs(design): replace status-var registry with Prometheus access for plugins ProxySQL already has prometheus-cpp linked in deps/ and a Prometheus registry that core counters/gauges feed; scrapers already poll its /metrics endpoint. A separate plugin-private status-var sink would duplicate that machinery and target the wrong protocol surface -- SHOW MYSQL STATUS is a MySQL-protocol response that core owns and that mixes plugin metrics with wire-protocol details. Replaces the second Step 2 ABI extension: before: register_status_var(name) -> handle status_var_inc(handle, delta) -> surfaces in SHOW MYSQL STATUS after: get_prometheus_registry() -> prometheus::Registry* -> plugins use prometheus-cpp directly against the shared registry; their counters / gauges / histograms appear at the same /metrics endpoint as core's For plugin state that is naturally tabular and queryable via admin SQL, the existing ABI already covers it -- register_table(stats_db, ...). GenAI's existing stats_mcp_query_tools_counters / stats_mcp_query_digest / stats_mcp_query_rules (and their _reset siblings) currently registered in Admin_Bootstrap.cpp move to the plugin via that path during Step 4; no new ABI is required for that. Updates throughout: ABI extensions section, Step 2 description, error handling (registry overflow becomes name-collision exception), testing (test_plugin_status_var-t becomes test_plugin_prometheus-t), module layout (plugin_status_vars.cpp becomes plugin_metrics.cpp), and ProtocolX coordination note.		2 months ago
..
2026-04-07-mysqlx-plugin-design.md	Add mysqlx plugin design spec	3 months ago
2026-04-09-mysqlx-canonical-commands-design.md	spec: mysqlx canonical admin commands design	3 months ago
2026-04-16-genai-plugin-carveout-design.md	docs(design): replace status-var registry with Prometheus access for plugins	2 months ago
2026-04-17-mysqlx-route-identity-design.md	docs(mysqlx): add route-identity design spec and implementation plan	2 months ago