Telegram RegisterThe public register of Telegram
Telegram profile photo for Мониторим ИТ

Channel

Мониторим ИТ

@monitorim_it

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

8,568subscribers

+65 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-1001368216193
TypeChannel
Username@monitorim_it
DescriptionКанал о наблюдаемости (Observability): логи, трейсы, метрики. Реклама: @gals_ad_bot Вопросы: @antoniusfirst @usr_bin_linux — Linux @zabbix_ru — Zabbix @elasticstack_ru — ElasticSearch/OpenSearch
Created27 March 2018 — measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live10 November 2026
Measurements held27
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/monitorim_it

Topic

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 11 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 the other topics.

Growth

8,5038,5738,5386 August 2026 — 8,503 subscribers6 August 2026 — 8,503 subscribers6 August 2026 — 8,515 subscribers12 August 2026 — 8,514 subscribers16 August 2026 — 8,517 subscribers20 August 2026 — 8,518 subscribers23 August 2026 — 8,523 subscribers26 August 2026 — 8,522 subscribers29 August 2026 — 8,521 subscribers1 September 2026 — 8,513 subscribers5 September 2026 — 8,521 subscribers10 September 2026 — 8,522 subscribers14 September 2026 — 8,524 subscribers18 September 2026 — 8,533 subscribers27 September 2026 — 8,542 subscribers5 October 2026 — 8,534 subscribers12 October 2026 — 8,543 subscribers15 October 2026 — 8,544 subscribers18 October 2026 — 8,547 subscribers21 October 2026 — 8,550 subscribers23 October 2026 — 8,562 subscribers26 October 2026 — 8,560 subscribers29 October 2026 — 8,563 subscribers1 November 2026 — 8,573 subscribers4 November 2026 — 8,570 subscribers7 November 2026 — 8,573 subscribers10 November 2026 — 8,568 subscribers8,5686 August 202610 November 2026
27 measurements spanning 96 days, net +65. 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 8,493–8,584 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
10 Nov 2026, 12:208,568-5
7 Nov 2026, 06:498,573+3
4 Nov 2026, 09:548,570-3
1 Nov 2026, 07:148,573+10
29 Oct 2026, 15:098,563+3
26 Oct 2026, 19:218,560-2
23 Oct 2026, 20:518,562+12
21 Oct 2026, 00:068,550+3
18 Oct 2026, 01:168,547+3
15 Oct 2026, 08:398,544+1
12 Oct 2026, 02:568,543+9
5 Oct 2026, 14:198,534-8
27 Sept 2026, 09:568,542+9
18 Sept 2026, 12:598,533+9
14 Sept 2026, 00:588,524+2
10 Sept 2026, 15:598,522+1
5 Sept 2026, 12:228,521+8
1 Sept 2026, 12:058,513-8
29 Aug 2026, 08:388,521-1
26 Aug 2026, 09:348,522first reading

Engagement

71 posts held, back to 16 July 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 46 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
24.0%
avg views ÷ 8,568 subscribers
Avg views / post
2,060
29 posts measured
Reaction rate
0.657%
reactions ÷ views · ER floor
Posts in window
30
of 71 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 10 November 2026
Posts held71 (16 July 2026 – 10 November 2026)
Views total59,633
Reactions total392
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 01:59 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.

What this channel posts

Photos
≈374
Videos
≈1
Links
≈1,750

Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
55s
Average length
28s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

914 reactions across 65 posts, in 6 distinct kinds. The most used accounts for 48.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥44348.5%
👍25728.1%
⚡9410.3%
❤849.19%
👎252.74%
🤔111.20%

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

Measured over the 71 most recent posts we hold, published 16 July 2026 to 10 November 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.

Advertising

Ad load
4.23%
3 of 71 posts carry an ad marker
Regulatory tokens
3
posts carrying an erid · 3 distinct tokens
Median views · ads
2,250
over 3 measured posts
Median views · rest
2,270
over 67 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2VtzqwvTM5F119 October 202619 October 2026
2VtzqxUmDUe117 July 202617 July 2026
2W5zFGKME7t110 November 202610 November 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 71 most recent posts we hold, published 16 July 2026 to 10 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

Telegram’s own ‘edited’ marker: 3 of 30 posts held from the last 30 days (10.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

10 Nov 2026, 12:05 UTC923 views10 reactionsread 11 November 2026
Photo

🐳 DockMon — единая панель для мониторинга и управления Docker-контейнерами Если контейнеров становится больше, чем помещается в выводе docker ps, управлять ими через консоль уже не всегда удобно. DockMon предлагает веб-интерфейс для наблюдения за Docker-инфраструктурой на одном или нескольких хостах. Основные возможности проекта: 🚀 мониторинг CPU, памяти и сетевого трафика в реальном времени 🚀 хранение историческ…

🔥9👎1

10 Nov 2026, 10:05 UTC≈1,060 views10 reactionsread 11 November 2026
Advertisementerid 2W5zFGKME7tPhoto

Конверсия падает, заказы не доходят до оформления. Где искать причину — в бизнес-процессе, приложении или внешнем сервисе? 📅 12 ноября в 11:00 (Мск), онлайн На вебинаре разберем, как использовать бизнес-мониторинг и техническую наблюдаемость вместе, а также применять ИИ с MCP для расследования инцидентов. Покажем, как: ◇ Обнаруживать отклонения бизнес-показателей и определять, какие бизнес-процессы затронуты. ◇ Пр…

🔥6⚡2👍2

10 Nov 2026, 06:02 UTC≈1,250 views10 reactionsread 11 November 2026
Photo

📊 Переменные Grafana становятся удобнее: меньше выпадающих списков и копирования между дашбордами Переменные позволяют превратить один дашборд в универсальный инструмент: выбрать кластер, регион, сервис или окружение — и автоматически обновить все панели. Но на больших дашбордах верхняя панель быстро превращается в коллекцию фильтров, а одинаковые переменные приходится вручную переносить между разными представлениям…

🔥6⚡2👍2

9 Nov 2026, 13:15 UTC≈1,400 views15 reactionsread 11 November 2026

Логи Linux: где искать причину, когда «ничего не работает» Посвящается всем тем, кто работает с логами. Когда сервис падает, сервер перезагружается или кто-то безуспешно пытается войти по SSH, ответ обычно уже записан в логах. Главное — понимать, где именно его искать и какой инструмент использовать. В этой статье собран подробный справочник по базовой работе с логами Linux: 🚀 чем отличаются journald и rsyslog 🚀 …

👍7🔥6⚡2

9 Nov 2026, 10:05 UTC≈1,100 views7 reactionsread 10 November 2026
Video

Как пустить LLM в прод и не сжечь все токены? 🤖 26 ноября Orion soft и Онтико проводят DevOps Lounge — бесплатный митап про AI в проде и в задачах DevOps-инженеров. — Orion soft: AI Gateway в Nova AI. Единая точка входа к моделям: RBAC, квоты и лимиты токенов, трейсинг, умная балансировка и фейловер. Плюс guardrails поверх гейтвея: фильтрация PII и неэтичного контента; — VK Tech: от локального харнесса с Codex и Cl…

🔥4👍2👎1

9 Nov 2026, 05:53 UTC≈1,450 views12 reactionsread 11 November 2026
Photo

Как VictoriaLogs видит ваши логи до того, как записать их на диск Производительность системы хранения начинается не с выбора алгоритма сжатия, а с модели данных. В этом материале автор разбирает внутреннее представление логов в VictoriaLogs и объясняет, как разные форматы входящих сообщений приводятся к единой структуре. У каждой записи есть три ключевые составляющие: 🚀 _time — временная метка 🚀 _msg — основное т…

👍5🔥4⚡3

6 Nov 2026, 13:15 UTC≈1,720 views16 reactionsread 11 November 2026
Video

Как найти причину сбоя платежей, не написав ни одного запроса к логам В VictoriaLogs появилась интеграция с Grafana Logs Drilldown — визуальным инструментом для поэтапного исследования логов. Теперь инженеру необязательно сразу вспоминать синтаксис LogsQL: данные можно последовательно фильтровать по сервисам, уровням, полям, версиям приложения и шаблонам сообщений прямо в Grafana Explore. В статье разбирается практ…

👍6🔥5⚡3❤2

6 Nov 2026, 08:03 UTC≈1,660 views14 reactionsread 11 November 2026
Video

Что нового в ClickStack: PromQL, интерактивные дашборды и AI-диагностика Команда ClickHouse собрала в одном материале изменения ClickStack за сентябрь и октябрь — сразу четыре релиза, с v2.39 по v2.42. Обновление получилось заметным: развиваются не только визуализация и поиск, но и полноценные сценарии расследования инцидентов. Среди обновлений: 🚀 интерактивные ad hoc-фильтры для дашбордов 🚀 поддержка PromQL во в…

🔥8⚡3👍3

5 Nov 2026, 08:13 UTC≈1,960 views11 reactionsread 11 November 2026

Grafana Alloy научился работать как нативный OpenTelemetry Collector Начиная с Alloy 1.21.0 встроенный OTel Engine перешёл в статус Public Preview. Теперь внутри Grafana Alloy можно запускать полноценный OpenTelemetry Collector с обычной YAML-конфигурацией — без преобразования в собственный синтаксис Alloy. Фактически у Alloy теперь два движка: 🚀 стандартный движок — универсальный комбайн для Prometheus, Loki, OTL…

🔥6⚡2👍2❤1

4 Nov 2026, 13:15 UTC≈1,650 views21 reactionsread 11 November 2026

Что такое span в OpenTelemetry и зачем он нужен Когда общаюсь с кем-то из клиентов за OpenTelemetry и рассказываю какая это все-таки универсальная вещь, невозможно обойти стороной разговор про трейсинг. А где трейсинг там и сами трейсы и их части — спаны. Многие используют понятия трейсы и спаны почти как синонимы. На самом деле разница тут простая: Span — это одна отдельная операция, а trace — вся история прохожде…

🔥9👍8❤2⚡1🤔1

3 Nov 2026, 13:25 UTC≈1,750 views16 reactionsread 11 November 2026
Photo

VictoriaMetrics или Prometheus: что выбрать для хранения метрик? В статье разбирают отличия этих двух решений: 🚀 архитектура хранения и обработки метрик 🚀 single-node и кластерный варианты VictoriaMetrics 🚀 различия между PromQL и MetricsQL 🚀 репликация, дедупликация и сроки хранения 🚀 миграция через Remote Write без немедленного отключения Prometheus 🚀 совместимость с ServiceMonitor, PodMonitor и PrometheusRu…

👍6🔥5❤3⚡2

3 Nov 2026, 09:44 UTCviews —

Мониторим ИТ pinned «Приходите на тренинги по Zabbix 8.0 Релиз Zabbix 8.0 уже совсем скоро. Запланируйте обучение команды, чтобы первыми получить знания об особенностях новой версии (а нововведений там много). Приглашаю вас на официальные вендорские тренинги Zabbix Certified…»

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

Posts edited after publishing

@monitorim_it edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
12 August 2026
Most recent edit
12 August 2026

Posts recorded as deleted after publishing

We recorded 9 posts on @monitorim_it as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
8 August 2026
Most recent seen missing
7 November 2026
Median time before seen missing
27 hours
Seen missing in the last 30 days
5

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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 6 registered channels — 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.

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.

Appears in Telegram’s recommendations for other channels

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.

DevOps&SRE Library
@devopslibrary · 19,870
Telegram ranks this channel #1 of 94 here — alongside 93 others — read 30 September 2026
IT STAND
@ITSTAND_ORG · 164,814
Telegram ranks this channel #3 of 98 here — alongside 97 others — read 9 September 2026
DevOps by REBRAIN
@rebrain_devops · 28,735
Telegram ranks this channel #3 of 94 here — alongside 93 others — read 9 September 2026
ServerAdmin.ru
@srv_admin · 32,701
Telegram ranks this channel #4 of 96 here — alongside 95 others — read 5 September 2026
Системный администратор
@i_odmin · 26,713
Telegram ranks this channel #11 of 89 here — alongside 88 others — read 12 September 2026
Devops Jobs — вакансии и резюме
@devops_jobs_feed · 22,271
Telegram ranks this channel #15 of 95 here — alongside 94 others — read 22 September 2026
Selectel
@Selectel · 62,423
Telegram ranks this channel #15 of 96 here — alongside 95 others — read 21 August 2026
MikroTik-сэнсэй
@mikrotik_sensei · 19,662
Telegram ranks this channel #16 of 92 here — alongside 91 others — read 1 October 2026
BZD • Книги для программистов
@bzd_channel · 36,213
Telegram ranks this channel #16 of 57 here — alongside 56 others — read 1 September 2026
Секреты сисадмина | DevOps, Linux, SRE
@sysadmin_library · 25,723
Telegram ranks this channel #20 of 85 here — alongside 84 others — read 13 September 2026
Книги для Системного Администратора
@i_odmin_book · 18,778
Telegram ranks this channel #21 of 83 here — alongside 82 others — read 5 October 2026
Yandex Cloud
@yandexcloudnews · 23,951
Telegram ranks this channel #21 of 97 here — alongside 96 others — read 22 September 2026
DevOps
@DevOPSitsec · 23,892
Telegram ranks this channel #22 of 90 here — alongside 89 others — read 18 September 2026
DevOps community for love
@devopsforlove · 44,606
Telegram ranks this channel #22 of 95 here — alongside 94 others — read 9 September 2026
ДЕВОПСИНА | DevOps | Linux
@devopsina · 23,569
Telegram ranks this channel #25 of 90 here — alongside 89 others — read 18 September 2026
Типичный Сисадмин
@sysodmins · 40,818
Telegram ranks this channel #30 of 93 here — alongside 92 others — read 31 August 2026
Bash Days | Linux | DevOps
@bashdays · 23,621
Telegram ranks this channel #41 of 94 here — alongside 93 others — read 18 September 2026
TechNews
@techlucker · 42,607
Telegram ranks this channel #62 of 79 here — alongside 78 others — read 28 August 2026
Информация опасносте
@alexmakus · 18,748
Telegram ranks this channel #68 of 85 here — alongside 84 others — read 5 October 2026
Linux для чайника
@os_linux_ru · 19,536
Telegram ranks this channel #69 of 87 here — alongside 86 others — read 1 October 2026
Библиотека Go-разработчика | Golang
@goproglib · 23,896
Telegram ranks this channel #80 of 91 here — alongside 90 others — read 17 September 2026
Серверная Админа | Компьютерные сети
@school_network · 26,411
Telegram ranks this channel #81 of 85 here — alongside 84 others — read 12 September 2026

This channel appears in 22 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Мониторим ИТ” (@monitorim_it), 8,568 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/monitorim_it.

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.