P1:闭环时限管控、治理成效评估、站型阈值系数与接口测试

- 闭环状态流转自动记录接单/闭环时间,状态值校验;按断站分级判定响应时限
  (及时/超时/超时未响应/未到期/无记录),新增及时响应率、平均闭环时长、超时未闭环指标与筛选
- 新增治理成效评估 /api/effect:分界日期前后指标对比与问题站点逐站改善判定
- 新增站型阈值系数(实际阈值 = 场景阈值 × 站型系数)及配置接口与页面
- 样例数据新增接单/闭环时间(独立随机数,原字段不变),导入支持并校验
- 新增 tests/test_api.py(权限、导入模板、闭环流程、站型系数、成效评估、无数据边界)
- 修复:新流水无告警匹配时根因分析报错;空筛选时超长站点清单返回 500

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
treeandClaude Opus 5.5 committed 2026-11-18 15:14:06 +08:00
1 parent e9616af34d
commit 0e070a64fe
13 files changed
+6540 -6043

No files matched your search

+67 -5
View File
@@ -1,9 +1,9 @@
import {html} from 'vendor';
import {html, TextField, useState} from 'vendor';
import {useApp, useFetch} from '../api.js';
import {accentMax, fixed, num} from '../format.js';
import {EChart} from '../components/EChart.js';
import {DataTable} from '../components/DataTable.js';
import {Kpi, Loading, Section} from '../components/ui.js';
import {Cause, Kpi, Loading, Section, VerdictTag} from '../components/ui.js';
const BENCH_COLUMNS = [
{key: 'scene', title: '场景'}, {key: 'sites', title: '站点数'}, {key: 'count', title: '退服次数'},
@@ -11,6 +11,24 @@ const BENCH_COLUMNS = [
{key: 'availability', title: '可用率(%)'}, {key: 'long_ratio', title: '超长占比(%)'}, {key: 'repeat_rate', title: '重复退服率(%)'},
{key: 'users', title: '受影响用户', render: num}, {key: 'user_h', title: '用户·小时', render: num},
{key: 'loss_gb', title: '业务损失(GB)', render: num},
{key: 'response_rate', title: '及时响应率(%)', render: v => v ?? '—'},
{key: 'avg_close_h', title: '平均闭环(h)', render: v => v ?? '—'},
];
const EFFECT_COLUMNS = [
{key: 'metric', title: '指标'}, {key: 'before', title: '治理前', render: v => (v == null ? '—' : num(v))},
{key: 'after', title: '治理后', render: v => (v == null ? '—' : num(v))},
{key: 'change', title: '变化(%)', render: v => (v === null ? '—' : `${v > 0 ? '+' : ''}${v}`)},
{key: 'verdict', title: '判定', render: v => html`<${VerdictTag} value=${v}/>`},
];
const EFFECT_SITE_COLUMNS = [
{key: 'site_name', title: '基站名称'}, {key: 'scene', title: '场景'}, {key: 'site_type', title: '站型'},
{key: 'kind', title: '治理前问题'}, {key: 'top_cause', title: '主要根因', render: v => html`<${Cause} value=${v}/>`},
{key: 'count_before', title: '月均次数·前'}, {key: 'count_after', title: '月均次数·后'},
{key: 'min_before', title: '月均时长·前(分)', render: num}, {key: 'min_after', title: '月均时长·后(分)', render: num},
{key: 'change', title: '次数变化(%)', render: v => (v === null ? '—' : `${v > 0 ? '+' : ''}${v}`)},
{key: 'verdict', title: '判定', render: v => html`<${VerdictTag} value=${v}/>`},
];
/** 场景柱状图配置:最大的场景用强调色标出 */
@@ -41,12 +59,24 @@ export default function Impact() {
<${Kpi} title="重复退服率" value=${fixed(k.repeat_rate)} unit="%"/>
</div>
</${Section}>
<${Section} title="闭环管控" hint="响应时限从退服开始算:重要 2 小时、主要 4 小时、次要 24 小时">
<div className="kpis">
<${Kpi} title="闭环率" value=${fixed(k.closed)} unit="%"/>
<${Kpi} title="及时响应率" value=${fixed(k.response_rate) || '—'} unit="%" sub="及时 ÷(及时 + 超时 + 超时未响应)"/>
<${Kpi} title="平均闭环时长" value=${k.avg_close_h ?? '—'} unit="h" sub="退服开始 → 闭环;无接单 / 闭环时间的记录不计"/>
<${Kpi} title="超时未闭环" value=${num(k.overdue_open)} unit="条" sub="可在退服流水管理中筛选处理"/>
</div>
</${Section}>
<${Section} span=${6} title="分场景退服率" hint="单位:%">
<${EChart} option=${sceneBar(bench, bench.map(x => x.outage_rate))}/>
</${Section}>
<${Section} span=${6} title="分场景受影响用户·小时" hint="单位:万人·h">
<${EChart} option=${sceneBar(bench, bench.map(x => +(x.user_h / 1e4).toFixed(1)))}/>
</${Section}>
<${Section} title="通信场景运维考核指标横向对标">
<${DataTable} rowKey="scene" columns=${BENCH_COLUMNS} rows=${bench}/>
</${Section}>
<${Effect}/>
<${Section} title="口径说明">
<div className="note">
退服率 = 总退服时长 ÷(站点数 × 统计周期);统计周期取顶栏的月份 / 日期范围,未筛选时为全部流水首日至末日。
@@ -54,8 +84,40 @@ export default function Impact() {
覆盖补偿:站点 500 米内每有一个邻站,受影响用户与话务损失下降 10%(室分站 5%),最低保留 40%。
</div>
</${Section}>
<${Section} title="通信场景运维考核指标横向对标">
<${DataTable} rowKey="scene" columns=${BENCH_COLUMNS} rows=${bench}/>
</${Section}>
</div>`;
}
/** 治理成效评估:以分界日期把统计周期分成前后两段,比较考核指标与问题站点的变化 */
function Effect() {
const {filters} = useApp();
const [split, setSplit] = useState('');
const {data} = useFetch('/api/effect', {...filters, split});
const picker = html`
<${TextField} type="date" label="治理分界日期" labelHidden controlSize="small" value=${split || data?.split || ''}
onChange=${e => setSplit(e.target.value)}/>`;
if (!data) return html`<${Section} title="治理成效评估" extra=${picker}><${Loading}/></${Section}>`;
const hint = `${data.begin} ~ ${data.split}(${data.days_before} 天)对比 ${data.split} ~ ${data.end}(${data.days_after} 天)`;
return html`
<${Section} title="治理成效评估" hint=${hint} extra=${picker}>
<div className="grid">
<div className="span-5">
<${DataTable} rowKey="metric" columns=${EFFECT_COLUMNS} rows=${data.rows}/>
<div className="note">
两段各按自身天数折算,长度不同也可直接比较;变化在 ±10% 以内记为持平。
退服存在季节性(夏季雷雨、高温停电多),跨季节对比时请结合同期数据判断。
</div>
</div>
<div className="span-7">
<div className="chips">
<div className="chip"><span>治理前问题站点</span>${data.sites.length} 个</div>
<div className="chip" data-tone="green"><span>改善</span>${data.improved}</div>
<div className="chip"><span>持平</span>${data.flat}</div>
<div className="chip"><span>恶化</span>${data.worsened}</div>
</div>
<${DataTable} rowKey="ne_id" columns=${EFFECT_SITE_COLUMNS} rows=${data.sites} maxHeight=${420}/>
</div>
</div>
</${Section}>`;
}