Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Cluster Dashboard: add an Operations surface (live currentOp + kill)

Aperta
  • Qualcosa non va?
#910 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
30/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
typescript, vscode
Ambito
devtools, observability

Direzione di ricerca

Inizia con il prototipo in src/webviews/documentdb/clusterDashboard/components/OperationsTab.tsx e operationHistory.ts, quindi segui getCurrentOperations, killOperation e clearOperationHistory in clusterDashboardRouter.ts. Leggi getClusterHealth.ts e i relativi test per comprendere l’ambito delle operazioni correnti, la redazione, la cronologia e le limitazioni della piattaforma. Il lavoro è completato quando il design della superficie, il comportamento del polling, i messaggi sui privilegi, lo stato dell’interruzione, la cronologia transitoria e il comportamento sulle piattaforme non supportate sono risolti esplicitamente.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Summary

Add a Operations surface to the Cluster Dashboard: a live view of what the cluster is currently doing, with the ability to inspect and terminate a running operation.

This was prototyped inside the Cluster Dashboard PR (#823) but has been pulled out of that PR's scope. The dashboard now leads with the storage/inventory view alone, and Operations should land as its own focused change so it gets the design and review attention it needs.

Why it is worth its own work item

The prototype surfaced several questions that are about operations monitoring specifically, not about the dashboard shell, and each of them deserves a deliberate answer rather than a default:

  • currentOp breadth varies by privilege. On a least-privileged connection the chain falls back to the caller's own operations, so a count of "1" can mean one operation on an idle cluster or one of yours among hundreds. The scope has to be reported alongside the number, or the number misinforms.
  • killOp is not an acknowledgement. It replies {ok: 1} whether or not anything matched, so the UI can only distinguish requested / cancelled / gone / failed / unverified — it can never truthfully say "the operation has been killed".
  • Operations are transient. An operation seen in one poll is usually absent from the next, so a plain snapshot table flickers and cannot be acted on. The prototype kept an observed-operation history keyed by occurrence identity; whether that is the right model is an open design question.
  • Command payloads carry customer data. A current operation includes query filter values, document contents and the client address that issued them. Anything that displays, copies or exports them needs an explicit redaction and consent story.
  • Platform support is uneven. Azure DocumentDB (vCore) rejects serverStatus, so anything derived from it is unavailable there and the surface has to degrade honestly rather than showing a sampling artifact dressed up as a rate.

Existing material

A working implementation is on feature/cluster-dashboard-poc and can be used as the starting point:

  • src/webviews/documentdb/clusterDashboard/components/OperationsTab.tsx — the live table, history accordion, and kill flow
  • src/webviews/documentdb/clusterDashboard/operationHistory.ts (+ tests) — occurrence identity and the observed-operation window
  • clusterDashboardRouter.ts — getCurrentOperations, killOperation, clearOperationHistory
  • src/documentdb/utils/getClusterHealth.ts — listCurrentOperations, killOperation, CURRENT_OP_SHARE_WINDOW_MS, and buildCommandPreview's redaction

Note that operationHistory.ts and listCurrentOperations are still in use: the dashboard's View Raw Diagnostics document reports current and observed operations even with the tab gone.

Open questions for the work item

  • Is Operations a tab on the Cluster Dashboard, a separate view, or a tree surface?
  • Does it poll continuously, or on demand? Continuous polling of a production cluster from a panel nobody is looking at is the failure mode to avoid.
  • What is the minimum privilege set it should support, and what does it say when it has less?
Lingua principale
TypeScript
Stelle
33
Fork
22
Merge medio
18h 6m
PR unite (30g)
41

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di microsoft/vscode-documentdb

Tutte le issue di microsoft/vscode-documentdb

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.