No user-submitted related servers found.
Scored across 35 tools
Most tools have clearly distinct purposes: kill_session vs kill_query, table_sizes vs table_fragmentation vs table_status, and the read/analysis pairs (lock_waits vs lock_wait_rca, top_queries vs slow_query_rca) are well separated, with descriptions explicitly cross-referencing each other. The main overlap is the one-shot 'overview' tool, which duplicates subsets of server_version, connection_stats, long_running_queries and table_fragmentation, creating mild redundancy an agent could stumble over.
Nearly all names are snake_case and readable, with a sensible convention of verb_noun for actions (kill_session, create_index, set_global_variable) and noun-phrase for reads (table_sizes, index_stats). Minor deviations exist (undo_list vs undo_apply, the single-word 'overview', and the 'rca' suffix group), but they are consistent within their families.
35 tools is on the heavy side for a single server and sits above the typical 3-15 range; several read probes (server_version, connection_stats, show_status) are partially subsumed by 'overview'. However, the breadth of the MySQL AIOps domain (health, sessions, locks, replication, indexes, fragmentation, queries, plus governed writes) means most tools target a genuinely distinct signal rather than padding.
Coverage is strong and coherent: a full read surface (status, variables, sessions, transactions, lock-wait/slow-query/replication RCA, index and fragmentation analysis, replication/binlog state) plus reversible writes (kill, optimize/analyze, create/drop index, set global variable, reset stats) backed by an undo framework. Gaps are minor for the AIOps scope: no replication-control actions (start/stop/promote replica) and no schema/table DDL beyond index operations.