netx

Independent operations tool (web + MCP) for alarm-centric workflows.

Licensed under the MIT License. Security reports: SECURITY.md.

Phase 1 scope

• Import ZTE Alarm Monitor Excel
• Normalize and store alarms into an isolated PostgreSQL
• Query and aggregate alarms via REST API
• Expose the same capabilities through built-in remote MCP (/mcp)
• Quick diagnostics endpoint (/v1/diagnostics)
• AP analysis bridge to oclaw (/v1/ap/analyze)

Environment setup (from scratch)

0) Prerequisites

• Python 3.11+ (project currently tested on newer versions too)
• Node.js 20+ (includes npm) for frontend
• PostgreSQL 14+
• PowerShell (Windows startup scripts use .ps1)

Quick check:

python --version
node --version
npm --version
psql --version

If Node/npm is missing (Windows example):

winget install OpenJS.NodeJS.LTS

1) Initialize PostgreSQL role/database (Windows, recommended)

For first-time setup on a new machine, run:

cd netx
powershell -ExecutionPolicy Bypass -File .\scripts\init_pg.ps1

The script is idempotent: it creates/repairs role netx, database netx, grants privileges, and verifies connection.

Common options:

powershell -ExecutionPolicy Bypass -File .\scripts\init_pg.ps1 `
  -SuperUser postgres `
  -SuperPassword "your-postgres-password" `
  -NetxUser netx `
  -NetxPassword "your-netx-password" `
  -NetxDatabase netx

2) Python virtual environment and backend deps

cd netx
python -m venv .venv
.\.venv\Scripts\python -m pip install --upgrade pip
.\.venv\Scripts\python -m pip install -r requirements.txt

3) Frontend deps (npm)

cd .\web
npm install
cd ..

4) Configure environment variables

Option A: temporary env vars in current shell

$env:NETX_DATABASE_URL = "postgresql+psycopg://netx:netx@127.0.0.1:5432/netx"
$env:NETX_HOST = "127.0.0.1"
$env:NETX_PORT = "8890"

Option B: local .env (recommended)

NETX_DATABASE_URL=postgresql+psycopg://postgres:admin123@127.0.0.1:5432/netx
NETX_OCLAW_ANALYZE_TOKEN=admin123
NETX_OCLAW_HEALTH_URL=http://127.0.0.1:8787/admin/api/ops-ai/health
# App login (required for production)
NETX_AUTH_ENABLED=true
NETX_AUTH_SECRET=replace-with-a-long-random-string
NETX_BOOTSTRAP_ADMIN_USERNAME=admin
NETX_BOOTSTRAP_ADMIN_PASSWORD=change-me-on-first-boot

Auth & audit

不必改 .env 也能用（本机默认）：

项	默认值
登录账号	admin / admin123
NETX_AUTH_SECRET	内置开发密钥（生产请改）
MCP Token 文件	首次启动写入 data/auth/mcp_token

生产建议在 .env 覆盖：

NETX_AUTH_SECRET=your-long-random-secret
NETX_BOOTSTRAP_ADMIN_PASSWORD=your-strong-password

• Web：打开 /login，用 admin / admin123（首次建库后生效）。工作台有 API Key 页可为不同用户生成 Token 并设置有效期。
• MCP：优先读环境变量 NETX_API_TOKEN；未设置时自动读 data/auth/mcp_token（API 启动时生成）。也可在 Cursor MCP 配置里显式填写：

"NETX_API_TOKEN": "nxt_...."

Token 内容见 data/auth/mcp_token，或登录后调用 POST /v1/api-tokens 新建。

5) Start services

Direct backend start:

.\.venv\Scripts\python -m netx_api.main

Or use automation scripts (recommended):

• API only (background):

powershell -ExecutionPolicy Bypass -File .\scripts\start_netx.ps1 -SkipInstall -Background

• API + Vite UI (background):

powershell -ExecutionPolicy Bypass -File .\scripts\start_netx.ps1 -SkipInstall -Background -WithWeb

Stop all started services:

powershell -ExecutionPolicy Bypass -File .\scripts\stop_netx.ps1 -Force

Primary web UI (Vite): http://127.0.0.1:5173/
API base: http://127.0.0.1:8890/

After npm run build in web/, the API can also serve the UI at http://127.0.0.1:8890/ (same origin). See NETX_UI_DIST_DIR in .env.example.

Windows installer (optional)

Fool-proof Windows delivery via NetX-Setup-*.exe (bundled or external Postgres, program/data split, offline upgrade over existing installs) lives under packaging/. Linux installs are unchanged — keep using your own Postgres and scripts/start_netx.sh.

6) MCP（Cursor / Codex / Claude / DSH）

先启动 netx API（§5）。MCP 已内置在 API 同端口：http://127.0.0.1:8890/mcp（Streamable HTTP）。客户端只需 URL + Bearer token，不必再装 Python MCP 包。

完整说明见：docs/MCP.md（topology / bizMonitor 分组见同目录文档）。配置示例：mcp.all.json、mcp.json。

# Claude Code
claude mcp add --transport http netx http://127.0.0.1:8890/mcp \
  --header "Authorization: Bearer <token>"

# 只要 ops / topology / bizMonitor 之一：
# http://127.0.0.1:8890/mcp?groups=ops

Useful API endpoints

• POST /v1/alarms/import (legacy import path, kept for compatibility)
• GET /v1/batches
• GET /v1/batches/{batch_id}
• GET /v1/batches/{batch_id}/errors.csv
• GET /v1/alarms
• GET /v1/alarms/aggregate
• GET /v1/diagnostics?batch_id=...
• GET /v1/ume/alarms
• GET /v1/ume/alarms/aggregate
• GET /v1/ume/diagnostics
• GET /v1/integrations/status
• POST /v1/ap/analyze

Web UI now includes an AI analyze panel that calls /v1/ap/analyze directly.

AP bridge auth (optional but recommended)

Set the same token on both sides:

• oclaw env: OCLAW_OPS_AI_SHARED_TOKEN=<token>
• netx env: NETX_OCLAW_ANALYZE_TOKEN=<token>

Optional: configure oclaw health check endpoint (defaults shown in .env.example):

• NETX_OCLAW_HEALTH_URL=http://127.0.0.1:8787/admin/api/ops-ai/health

analyze-sync runs a full LLM + gateway turn in oclaw; if netx reports timeout errors, raise the read timeout (seconds):

• NETX_OCLAW_ANALYZE_READ_TIMEOUT_SEC=180 (default 180; was effectively ~35s before)

Key sample file

Phase 1 parser (netx_api/config/parsers/zte_alarm_monitor_v1.yaml) remains available for historical compatibility. The recommended data source is UME sync (ume_alarms_current), while legacy import (POST /v1/alarms/import) is still kept available as a fallback path.

Contributing

Fork / PR 流程与注意事项见仓库根目录 CONTRIBUTING.md。