Device Virtual Server dashboard: missing descriptions explaining availability (isAvailable) vs enabled (isEnabled)

未关闭 适合新手
#277 0 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

@R34SGA 已经在做这个了。

开始于 2026年10月22日。

  • #278 来自 @R34SGA —— 未关闭

评估

难度
1/5
预计耗时
1 小时以内
新手友好度
88/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
活跃
技术栈
grafana, json
领域
documentation

调研方向

打开 services/grafana/provisioning/dashboards/bigip/device/device-virtual-server.json,找到 issue 中提到的三个面板。阅读它们现有的 description 字段,然后添加简洁的文字,说明运行时可用性与管理启用状态的区别,包括 24 小时面板。三个面板都能通过 Grafana 的信息图标显示这种区别后,即为完成。

由索引模型根据 Issue 内容生成。

描述

Problem

On the Device Virtual Server dashboard (services/grafana/provisioning/dashboards/bigip/device/device-virtual-server.json), the three panels in the "Availability" row have no description:

  • Virtual Server State isAvailable
  • Virtual Server isEnabled
  • Virtual Server Availability [24h]

These two concepts are frequently confused:

  • Availability (isAvailable) is the runtime state: the health of the virtual server based on its pool members (available when at least one member is up).
  • Enabled (isEnabled) is the administrative state: whether the virtual server has been enabled or disabled by an admin. A disabled VS receives no traffic regardless of pool member health.

Because the panels carry no description, the Grafana "info" icon does not appear in the panel header on the base view, and a user cannot tell from the dashboard why a virtual server can show isEnabled = 1 while isAvailable = 0 (all pool members down, or no default pool), or vice versa.

Proposed change

Fill the existing (empty) description fields on the isAvailable and isEnabled panels and add a description to the [24h] panel, explaining the difference between runtime availability and administrative state. Grafana renders the description field with an info icon on the panel header, so no layout or data changes are required.

This is a pure dashboard-JSON change; no collector or backend code is affected.

主要语言
Python
星标
107
派生
44
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

f5devcentral/application-study-tool 的其他 Issue

查看 f5devcentral/application-study-tool 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。