Server dashboard for Linux connections

Abierto
  • ¿Algo no está bien?
#3,657 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
clickhouse, mariadb, mysql, postgresql, swift
Área
database, desktop

Línea de trabajo

Read linux/ROADMAP.md and the macOS reference features/server-dashboard.mdx first. The issue leaves the roadmap decision open; if the feature is accepted, inspect how Linux network connections and database-specific catalog queries are handled. Done means PostgreSQL shows running queries and blocker relationships, and can cancel a query after confirmation.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement platform-linux
Problem

The Linux app shows nothing about what the server is doing: no sessions, no running queries, no locks. linux/ROADMAP.md, Backlog, Ideas lists "server monitoring (sessions, locks, slow queries)" as not committed. The macOS app has a server dashboard (features/server-dashboard.mdx).

When a query hangs or a table is locked, the user has to know each engine's catalog and type the query: pg_stat_activity on PostgreSQL, SHOW PROCESSLIST on MySQL and MariaDB, sys.dm_exec_requests on SQL Server, system.processes on ClickHouse.

Proposed solution
  • Decide whether it moves from Ideas into the backlog, and record it in linux/ROADMAP.md.
  • If yes, a Server tab per network connection, refreshed every few seconds while it is in front and paused otherwise:
    • sessions, with user, client address, database and state;
    • running queries, with their text and how long they have run, longest first;
    • locks and which session blocks which, where the engine reports it;
    • server version and uptime.
  • Cancel Query and End Session on a row, each asking first and refused on a read-only connection.
  • A panel the login cannot read says so instead of showing an empty list, for example pg_stat_activity without pg_read_all_stats showing only the user's own sessions.
  • Not offered for SQLite, which has no server.

Done means: on PostgreSQL, the tab lists the running queries, shows a blocked session and its blocker, and cancels one query after asking.

Alternatives considered

Query the engine's own catalog views from the editor.

Platform

Linux

Related database type

N/A / General

Lenguaje dominante
Swift
Estrellas
6.2k
Forks
412
Merge medio
3 h 56 min
PR fusionados (30 d)
669

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de TableProApp/TablePro

Todos los issues de TableProApp/TablePro

Issues similares

Más issues de Swift

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.