*cloud — *`PROBLEM`* — 2026.06.04 Trigger: Free disk space is less than 20% on volume /mnt/data Trigger status: PROBLEM Trigger severity: Disaster
Signed newMFCalertBOT

Channel
@MFC_zabbix_alert
On this record: Topic · Growth · Engagement · Posts · Cite this entry
29subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001146401434 |
|---|---|
| Type | Channel |
| Username | @MFC_zabbix_alert |
| Created | Between 1 April 2016 and 30 November 2019 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 8 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 5 times, most recently 8 October 2026 |
| On Telegram | t.me/MFC_zabbix_alert |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 30 September 2026 and assigned it the closest of 31 fixed categories, at 98% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Aug 2026, 19:14 | 29 | -1 |
| 11 Aug 2026, 04:00 | 30 | no change |
| 6 Aug 2026, 09:36 | 30 | first reading |
20 posts held, back to 10 August 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 1 page 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 20 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
*cloud — *`PROBLEM`* — 2026.06.04 Trigger: Free disk space is less than 20% on volume /mnt/data Trigger status: PROBLEM Trigger severity: Disaster
Signed newMFCalertBOT
*cloud — *`PROBLEM`* — 2026.06.04 Trigger: Free disk space is less than 20% on volume /mnt/data Trigger status: PROBLEM Trigger severity: Disaster
Signed newMFCalertBOT
Resolved: DNS-Not working Problem has been resolved at 02:02:31 on 2026.08.11 Problem name: DNS-Not working Host: ipa Severity: Disaster Original problem ID: 16076328
Signed newMFCalertBOT
*ipa — *`OK`* — 2026.08.11 Trigger: DNS-Not working Trigger status: OK Trigger severity: Disaster
Signed newMFCalertBOT
*ipa — *`OK`* — 2026.08.11 Trigger: DNS-Not working Trigger status: OK Trigger severity: Disaster
Signed newMFCalertBOT
*ipa — *`OK`* — 2026.08.11 Trigger: DNS-Not working Trigger status: OK Trigger severity: Disaster
Signed newMFCalertBOT
Problem: DNS-Not working Problem started at 02:00:26 on 2026.08.11 Problem name: DNS-Not working Host: ipa Severity: Disaster Original problem ID: 16076328
Signed newMFCalertBOT
*ipa — *`PROBLEM`* — 2026.08.11 Trigger: DNS-Not working Trigger status: PROBLEM Trigger severity: Disaster
Signed newMFCalertBOT
*ipa — *`PROBLEM`* — 2026.08.11 Trigger: DNS-Not working Trigger status: PROBLEM Trigger severity: Disaster
Signed newMFCalertBOT
*ipa — *`PROBLEM`* — 2026.08.11 Trigger: DNS-Not working Trigger status: PROBLEM Trigger severity: Disaster
Signed newMFCalertBOT
*PKPVD-3 app3 — *`OK`* — 2026.08.11 Trigger: query-java-process-status Trigger status: OK Trigger severity: Disaster
Signed newMFCalertBOT
*PKPVD-3 app3 — *`OK`* — 2026.08.11 Trigger: pvd-java-process-status Trigger status: OK Trigger severity: Disaster
Signed newMFCalertBOT
Showing the 12 most recent of 20 posts we hold for @MFC_zabbix_alert. 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.
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 28 August 2026 — this entry's latest reading, not the date you are reading this.
“MFC_zabbix_alert” (@MFC_zabbix_alert), 29 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/MFC_zabbix_alert.
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.