OpenEdge HCK — Health Check Kit

Monitor the health of your Progress OpenEdge databases without leaving VS Code. HCK provides a real-time dashboard for buffer usage, lock contention, transactions, replication status and I/O statistics — plus a suite of AI / MCP tools that let Copilot and other agents diagnose your databases for you.

Features

Real-time health dashboard — a webview showing live database health at a glance, including a composite health summary (connections, buffer hit ratio, area %full, backup age, BI/AI state, license usage and latch waits).
Activity monitoring — buffer, page-writer, server, index, record, space and I/O activity counters.
Database status — storage-area status, buffer status, checkpoints, connections, file list, active locks and transactions.
Lock & contention analysis — active locks, blocked clients and a waiter-to-holder blocking tree.
Replication monitoring — OpenEdge Replication agent and server status.
Statistics — cumulative and per-user table/index statistics and user I/O patterns.
AI & MCP tools — 40+ language-model tools (referenceable in Copilot Chat) and a built-in MCP server so AI agents can query database health and run guarded maintenance actions (disconnect user, clear lock, reset statistics) with confirmation.

Requirements

Requirement	Details
VS Code	`1.101.0` or newer
Node.js	v18 or newer — required to run the HCK backend server
OpenEdge (DLC)	A supported Progress OpenEdge installation. HCK reads the runtime path from the ABL extension's `abl.configuration.runtimes` setting (point it at your DLC directory).
OpenEdge ABL extension	The OpenEdge ABL VS Code extension must be installed and `abl.configuration.runtimes` configured.
OpenEdge Config Management	`AI4YOU.openedge-config-management` — installed automatically as an extension dependency.

Getting Started

Install — search for OpenEdge HCK - Health Check Kit in the Extensions panel and click Install, or install the provided .vsix via the Extensions ⋯ menu → Install from VSIX….

Configure the OpenEdge runtime in your VS Code settings:

{
  "abl.configuration.runtimes": [
    { "name": "12.2", "path": "C:/Progress/OpenEdge" }
  ],
  "abl.configuration.defaultRuntime": "12.2"
}

Add a database connection to openedge-project.json at your project root:

{
  "dbConnections": [
    {
      "name": "sports2020",
      "connect": "-db sports2020 -H localhost -S 10001"
    }
  ]
}

Open HCK in any of three ways:
- Click the HCK icon (pulse / heartbeat) in the Activity Bar.
- Right-click any file in the Explorer → 🏥 HCK - Health Check Kit.
- Open the Command Palette (Ctrl+Shift+P) → 🏥 HCK - Health Check Kit.
The backend starts automatically; the first launch may take a few seconds while OpenEdge initialises.

See the User Guide and Quick Start for a full walkthrough.

Extension Settings

This extension contributes the following settings:

Setting	Type	Default	Description
`hck.httpPort`	number	`23003`	HTTP port for the HCK backend server.
`hck.ablSocketPort`	number	`23000`	Socket port for ABL communication.

Change these if the defaults conflict with other services on your machine.

Commands

Command	Title
`openedge-hck.showHCK`	🏥 HCK - Health Check Kit

The extension also contributes 40+ AI language-model tools (all prefixed HCK: and referenceable in Copilot Chat with #) and an MCP server (OpenEdge HCK) that exposes the same health-check and maintenance capabilities to AI agents.

Known Issues

Symptom	Fix
Backend fails to start	Check the HCK Backend output channel for errors.
"No OpenEdge runtime configured"	Set `abl.configuration.runtimes` in VS Code settings.
Port conflicts	Change `hck.httpPort` (default `23003`) or `hck.ablSocketPort` (default `23000`) in settings.

Maintenance tools that alter database state (disconnect user, clear lock, reset statistics, run management task) always require confirmation before executing.

Release Notes

See CHANGELOG.md for the full release history.

License

This is proprietary software. See LICENSE.txt for details.

OpenEdge HCK - Health Check Kit

KH-IT