Telegram RegisterThe public register of Telegram

Channel

Zabbix Recipes

@zabbix_ru

On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry

3,616subscribers

+14 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002045222738
TypeChannel
Username@zabbix_ru
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/zabbix_ru

Growth

3,6023,6163,6096 August 2026 — 3,602 subscribers6 August 2026 — 3,602 subscribers9 August 2026 — 3,612 subscribers12 August 2026 — 3,616 subscribers6 August 202612 August 2026
4 measurements spanning 7 days, net +14. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 3,600–3,618 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 17:073,616+4
9 Aug 2026, 08:053,612+10
6 Aug 2026, 04:343,602no change
6 Aug 2026, 04:023,602first reading

Engagement

20 posts held, back to 27 March 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
65.4%
avg views ÷ 3,616 subscribers
Avg views / post
2,370
7 posts measured
Reaction rate
0.942%
reactions ÷ views · ER floor
Posts in window
7
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 29 July 2026
Posts held20 (27 March 202629 July 2026)
Views total16,560
Reactions total156
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 23:00 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

394 reactions across 20 posts, in 6 distinct kinds. The most used accounts for 46.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥18346.4%
👍17143.4%
256.35%
👎82.03%
😁61.52%
🆒10.254%

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 20 of the 20 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 394reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 27 March 2026 to 29 July 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.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 20 we hold a reading for · 5%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @zabbix_ru. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 20 most recent posts we hold for this entry, published 27 March 2026 to 29 July 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

29 Jul 2026, 10:01 UTC≈1,320 views21 reactionsread 7 August 2026

🎓 Официальный сертификат Zabbix — больше, чем просто документ При выборе обучения многие обращают внимание на программу курса и опыт преподавателя. Это важно. Но есть еще один фактор, который остается с вами надолго после окончания курса — официальный сертификат Zabbix. Компания Gals Software является официальным тренинг-партнером Zabbix, поэтому после успешного прохождения обучения и сдачи экзамена слушатели полу

👍8🔥63😁3👎1

28 Jul 2026, 09:36 UTC≈1,340 views10 reactionsread 7 August 2026

Доступ к экспертной поддержке Zabbix в почасовом формате Не каждую проблему в Zabbix можно решить поиском по документации или настройкой нескольких параметров. Иногда причина скрывается в архитектуре системы, взаимодействии компонентов или особенностях работы конкретной версии. Например: 👉 сервер периодически падает под нагрузкой; 👉 после обновления появились ошибки; 👉 не удается разобраться с производительность

🔥7😁2👍1

27 Jul 2026, 09:43 UTC≈1,540 views21 reactionsread 7 August 2026

Zabbix 8.0.0beta2 (случился 9 июля) 8.0 все ближе. Забыли вам сказать. Заметки к релизу @zabbix_ru

🔥15👍6

23 Jul 2026, 10:39 UTC≈4,610 views29 reactionsread 7 August 2026

Posted without readable text

👍14🔥114

21 Jul 2026, 13:31 UTC≈2,130 views21 reactionsread 7 August 2026
Photo

mattermost-zabbix-template Если так получилось, что вам нужно поставить на мониторинг Mattermost, присмотритесь к этому шаблону. Репозиторий на Github @zabbix_ru

👍13🔥62

16 Jul 2026, 12:04 UTC≈3,060 views22 reactionsread 7 August 2026
Photo

Zabbix обновил роудмэп по грядущим релизам. Что нас ждет в 8.0 LTS, 8.2, 8.4 и 9.0 LTS, можно посмотреть на специальной странице. @zabbix_ru

👍12🔥72😁1

16 Jul 2026, 10:00 UTC≈2,560 views32 reactionsread 7 August 2026
Photo

The Evolution of an SNMP Auto-Discovery Tool Вы подключаете к сети новое устройство — межсетевой экран, NAS, ИБП, коммутатор от производителя, который вы еще не стандартизировали. Открываете список шаблонов Zabbix. Ничего не совпадает. Скачиваете пакет MIB от производителя. Он огромный. Запускаете snmpwalk. Выводит тысячи строк. А затем начинается настоящая работа: выясняется, что всё это значит для мониторинга. Им

🔥22👍64

9 Jul 2026, 06:24 UTC≈3,000 views11 reactionsread 7 August 2026
Photo

Zabbix Handy Tips: Providing Additonal Context to Zabbix Events with Regsub Macro Function Функции regsub/iregsub можно использовать для извлечения частей значений элементов данных и предоставления дополнительного контекста в тегах проблем и названиях событий. В этом коротком видео показывают пример использования таких функций для заполнения названий событий, тегов и включения корреляции событий на основе триггеров

👍5🔥42

19 Jun 2026, 09:06 UTC≈3,790 views17 reactionsread 7 August 2026
Photo

Мониторинг сервиса Ivideon-server с помощью Zabbix В этой статье автор рассказывает как он собрал полноценный шаблон Zabbix для контроля камер видеонаблюдения на базе Ivideon-server. Что умеет шаблон: ✅ Автоматически обнаруживать камеры через LLD ✅ Контролировать доступность каждой камеры ✅ Проверять, ведётся ли архивная запись ✅ Создавать отдельные триггеры по каждой камере ✅ Работать с Ivideon Server 3.9 и 3.12

🔥11👍42

11 Jun 2026, 09:14 UTC≈3,890 views9 reactionsread 7 August 2026

Один из вебинаров уже сегодня. Регистрируйтесь, если еще не.

🔥6👍3

3 Jun 2026, 13:33 UTC≈4,860 views16 reactionsread 7 August 2026

Вебинары от Zabbix на английском языке в июне Отличная возможность задать свои вопросы. 11 июня 18:00 мск Распределенный мониторинг с помощью прокси Zabbix. Регистрация 18 июня 18:00 мск Мониторинг Windows Server с помощью Zabbix. Регистрация @zabbix_ru

👍10🔥6

23 May 2026, 06:13 UTC≈5,650 views20 reactionsread 7 August 2026
Photo

Мониторинг Kerio Connect через Zabbix 7 Если ваша почта на базе почтового сервера Kerio Connect, то вот описание готового шаблона, который работает через JSON-RPC Admin API. Репозиторий на Гитхаб @zabbix_ru

👍13🔥7

Showing the 12 most recent of 20 posts we hold for @zabbix_ru. 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.

Citation-graph rank

Citation-graph rank — 216,841 of 1,350,102entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“Zabbix Recipes” (@zabbix_ru), 3,616 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/zabbix_ru.

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.