🚀🚀nezhahq/nezha 发布新版本啦! 版本号: v2.3.2 变更日志: **Full Changelog**: https://github.com/nezhahq/nezha/compare/v2.3.1...v2.3.2 🎉🎉感谢该版本的贡献者: - naiba 💪💪 为群组加速 https://t.me/boost/nezhamonitoring
🔥4
Signed 哪吒通知小助手

Channel
@nezhanews
On this record: Growth · Engagement · Reactions · Posts · Handles named that no longer answer · Telegram's recommendations · Cite this entry
3,554subscribers
-13 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002162825195 |
|---|---|
| Type | Channel |
| Username | @nezhanews |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 1 September 2026 |
| On Telegram | t.me/nezhanews |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Sept 2026, 16:35 | 3,554 | -5 |
| 29 Aug 2026, 18:08 | 3,559 | -3 |
| 23 Aug 2026, 16:18 | 3,562 | +2 |
| 16 Aug 2026, 21:17 | 3,560 | +1 |
| 13 Aug 2026, 12:06 | 3,559 | -4 |
| 10 Aug 2026, 21:14 | 3,563 | -4 |
| 7 Aug 2026, 14:32 | 3,567 | no change |
| 7 Aug 2026, 14:21 | 3,567 | first reading |
19 posts held, back to 15 March 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 19 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
61 reactions across 13 posts, in 5 distinct kinds. The most used accounts for 47.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 29 | 47.5% | |
| ❤ | 20 | 32.8% | |
| 🔥 | 8 | 13.1% | |
| custom 5134535472818685462 | 2 | 3.28% | |
| 🏆 | 2 | 3.28% |
Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it is Telegram’s.
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 15 of the 19 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 61 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 15 March 2026 to 3 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
🚀🚀nezhahq/nezha 发布新版本啦! 版本号: v2.3.2 变更日志: **Full Changelog**: https://github.com/nezhahq/nezha/compare/v2.3.1...v2.3.2 🎉🎉感谢该版本的贡献者: - naiba 💪💪 为群组加速 https://t.me/boost/nezhamonitoring
🔥4
Signed 哪吒通知小助手
🚀🚀nezhahq/nezha 发布新版本啦! 版本号: v2.3.1 变更日志: ## What's Changed * chore(deps): bump the github-actions group with 2 updates by @dependabot[bot] in https://github.com/nezhahq/nezha/pull/1218 * fix(security): harden server and service deletion lifecycle by @naiba with @Copilot in https://github.com/nezhahq/nezha/pull/1220 ## New Contributors * @naiba with @Copilot made their first contribution in https://github.com/nezha…
❤1
Signed 哪吒通知小助手
🚀🚀nezhahq/agent 发布新版本啦! 版本号: v2.3.1 变更日志: ## What's Changed * Fixing CodeQL issues by @naiba with @Copilot in https://github.com/nezhahq/agent/pull/259 ## New Contributors * @naiba with @Copilot made their first contribution in https://github.com/nezhahq/agent/pull/259 **Full Changelog**: https://github.com/nezhahq/agent/compare/v2.3.0...v2.3.1 🎉🎉感谢该版本的贡献者: - Copilot 💪💪 为频道加速 https://t.me/boost/nezhanews
Signed 哪吒通知小助手
🚀🚀nezhahq/agent 发布新版本啦! 版本号: v2.3.0 变更日志: ## What's Changed * chore(deps): bump actions/checkout from 6 to 7 in the github-actions group by @dependabot[bot] in https://github.com/nezhahq/agent/pull/250 * chore(deps): bump github.com/prometheus-community/pro-bing from 0.9.0 to 0.9.1 in the go-dependencies group by @dependabot[bot] in https://github.com/nezhahq/agent/pull/251 * chore(deps): bump the go-dependencies gr…
🏆2
Signed 哪吒通知小助手
🚀🚀nezhahq/nezha 发布新版本啦! 版本号: v2.2.10 变更日志: **Full Changelog**: https://github.com/nezhahq/nezha/compare/v2.2.9...v2.2.10 🎉🎉感谢该版本的贡献者: - naiba - github-actions[bot] 💪💪 为频道加速 https://t.me/boost/nezhanews
❤3
Signed 哪吒通知小助手
Reminder: watchtower 已经狗带了,你们的容器可能很久没更新了,目前没什么特别好的替代方案,可以平滑迁移到 https://github.com/naiba-forks/watchtower
👍2
#社区项目 #社区主题 社区项目推荐 https://github.com/karllao/nezha-pixel Nezha Pixel 像素风格的 哪吒监控 (Nezha) 前台前端,基于 Vue 3 + Vite + TypeScript 与 @mmt817/pixel-ui 像素风组件库实现。 特性 🎮 复古像素风格界面(Press Start 2P + VT323 字体,CRT 网格背景) 📡 通过 WebSocket 实时刷新服务器状态(/api/v1/ws/server) 📊 服务器列表 + 单机详情 + TSDB 历史指标曲线(CPU / Mem / Disk / Net) 🔌 服务监控(HTTP/TCP/ICMP)可用率与循环流量统计 🌗 像素风明/暗双主题,自动持久化 🔍 按分组 / 在线状态过滤,按 CPU/MEM/网速排序 🛠 与官方 nezha-dash 完全相同的 API 路径与字段,可直接挂到…
👍10
Signed 白歌🦄 共穷国际大中华区总裁
哪吒 API 和 MCP 文档均已更新 • REST API 新增 Token 验证方式。现在可以在管理面板中创建 API Token,并按需限制 PAT 权限范围,相比直接使用账号凭据更安全,也更适合自动化接入。 • MCP 功能已完善,可将哪吒面板接入 Codex、Claude Code、OpenClaw 等 Agent,通过自然语言或自动化工作流完成服务器监控、状态查询,基础运维等各种好玩的操作。 • 哪吒社群 API 机器人 @nezha_offical_bot 已同步更新,支持最新 API 端点,并内置轻量 LLM 对话功能用于测试体验。(当然了,使用前需要自行准备并绑定一个大模型 API 😝) 文档地址: API:https://nezha.wiki/guide/api.html MCP:https://nezha.wiki/guide/mcp.html 启用条件 Dashboard >= v2.1.4 Age…
custom 51345354728186854622❤1
Signed 白歌🦄 共穷国际大中华区总裁
Nezha MCP 来了 用 AI 帮你分析是否被入侵 要求:dashboard >= v2.1.4 agent >= v2.1.0
哪吒监控公告板 pinned «关于哪吒监控旧版本安全缺陷的风险提示与自查建议 发布时间:2026年5月31日 正如此前公告中提到,哪吒监控旧版本存在多个安全缺陷。为降低潜在安全风险,我们强烈建议所有用户立即更新到最新版本,并根据自身部署情况开展必要的安全自查。 相关漏洞由安全研究人员报告。部分问题在修复版本发布后陆续公开披露。基于负责任披露原则,同时考虑到当时未发现相关问题被大规模利用的明确证据,我们未在修复完成前公开漏洞细节。现修复版本、更新提醒和相关安全公告均已发布,出于透明、负责的态度,我们对相关缺陷的影响范围和处置建议进行说明。…»
关于哪吒监控旧版本安全缺陷的风险提示与自查建议 发布时间:2026年5月31日 正如此前公告中提到,哪吒监控旧版本存在多个安全缺陷。为降低潜在安全风险,我们强烈建议所有用户立即更新到最新版本,并根据自身部署情况开展必要的安全自查。 相关漏洞由安全研究人员报告。部分问题在修复版本发布后陆续公开披露。基于负责任披露原则,同时考虑到当时未发现相关问题被大规模利用的明确证据,我们未在修复完成前公开漏洞细节。现修复版本、更新提醒和相关安全公告均已发布,出于透明、负责的态度,我们对相关缺陷的影响范围和处置建议进行说明。 相关披露信息可参考项目 GitHub Security Advisories 页面。感谢安全研究人员和社区用户对项目安全性的报告与反馈。 一、主要影响范围 根据已公开的安全公告,旧版本中的相关缺陷主要涉及以下几类风险: 1. 未登录场景下的敏感配置文件读取风险; 2. 多用户场景下的权限隔离和资源归属校验不足;…
👍5❤4
Signed 白歌🦄 共穷国际大中华区总裁
再次提醒大家更新至最新版本。今天会披露安全报告,你的面板随时可能被入侵。
❤3
Showing the 12 most recent of 19 posts we hold for @nezhanews. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
@nezhanews named 3 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 6 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 1 September 2026 — this entry's latest reading, not the date you are reading this.
“哪吒监控公告板” (@nezhanews), 3,554 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/nezhanews.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.