Channel
@sre_hamster
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
364subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001424143564 |
|---|---|
| Type | Channel |
| Username | @sre_hamster |
| Description | Personal channel where I will post interesting articles on RUS|ENG for sharing knowledge and information. Chats: @sre_hamster_tech @devops_sre_jobs @devops_ru @devops_jobs Channels: @sre_devops_jobs_rss Friends: @devops_jobs @devops_ru [In development] |
| Created | 17 June 2020 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/sre_hamster |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 11:00 | 364 | no change |
| 8 Aug 2026, 10:52 | 364 | first reading |
20 posts held, back to 26 July 2022 — 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 pageof 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 16 July 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
27 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 70.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 19 | 70.4% | |
| 🔥 | 7 | 25.9% | |
| 💩 | 1 | 3.70% |
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 10 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 27reactions 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 26 July 2022 to 16 July 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Контейнеры Kubernetes: процессы Linux под капотом 🔍 Ключевая концепция: Контейнеры — не виртуальные машины, а изолированные процессы Linux с ограниченными ресурсами. ▫️ Механизмы изоляции: - Namespaces (PID, сеть, IPC, mount) → виртуализация системных ресурсов - Cgroups → контроль CPU, памяти, дискового I/O - OverlayFS → эффективное управление слоями образов ▫️ Роль Kubernetes: - Абстракция над низкоуровневыми ком…
👍3💩1🔥1
🔥 SLA vs SLO: Главное, что путают даже профи ❌ Классическая ошибка: «Давайте сделаем SLA между командами!» — фраза, после которой SRE плачут в уголке. 🧩 Чем отличаются: - SLA (Service Level Agreement) — юридический договор с клиентом. Нарушил? Штрафы/компенсации 💸 - SLO (Service Level Objective) — внутренняя цель команды. Превысили? Заморозка релизов, но не суд 🎯 ⚡️ Пример: - *SLA*: «Простой >1 часа → возврат $10 …
👍6
The latest edition of Technology Radar — Volume 30 The themes are: - AI-assisted software development teams - Open-ish source licenses - Dragging pull requests closer to proper continuous integration - Emerging architecture patterns for large language models (LLMs) #study #radar
👍1
Defining clear Incident Severity levels is a key component to an efficient Incident Management process that helps Engineering teams quickly respond to outages and mitigate customer impact. Operating an online platform with multiple nines of availability is a complex task, modern websites depend on thousands to hundreds of thousands of individual moving parts all of which need to work correctly in order to provide a …
With the upcoming deprecation and subsequent removal of Pod Security Policies (PSPs) in Kubernetes, the time is near to find suitable alternatives. Those alternatives, it seems clear at present anyway, will need to be sourced from outside the Kubernetes project itself as there will be no replacement provided (edit: Pod Security Admission is the new, albeit incomplete, successor). The two leading CNCF projects which a…
Beyla is a vendor agnostic, eBPF-based, OpenTelemetry application auto-instrumentation tool, which lets you easily get started with Application Observability. eBPF is used to automatically inspect application executables and the OS networking layer, allowing us to capture essential application observability events for HTTP/S and gRPC services. From these captured eBPF events, we produce OpenTelemetry web transaction …
👍6
Robusta KRR (Kubernetes Resource Recommender) is a CLI tool for optimizing resource allocation in Kubernetes clusters. It gathers pod usage data from Prometheus and recommends requests and limits for CPU and memory. This reduces costs and improves performance. Link #observabilty #tools
🔥6
Slow Down! Rate Limiting Deep Dive Now, why should you care about rate limiting? Well, consider a situation where your API is hit with a massive number of requests in a short span. This could be due to a surge in user traffic, a glitch causing repeated requests, or even an attempt to overwhelm your system using DDOS attack. Without rate limiting, your system could get overwhelmed, leading to slow responses or, wors…
Best Practices for Java Apps on Kubernetes - Piotr's TechBlog In this article, you will read about the best practices for running Java apps on Kubernetes. Most of these recommendations will also be valid for other languages. However, I’m considering all the rules in the scope of Java characteristics and also showing solutions and tools available for JVM-based apps. Some of these Kubernetes recommendations are forced…
Grafana Beyla eBPF-based auto-instrumentation of HTTP/HTTPS/GRPC Go services, as well as HTTP/HTTPS services written in other languages (intercepting Kernel-level socket operations as well as OpenSSL invocations). #tools #beyla #observability
Technology Radar #29 The themes are: - AI-assisted software development - How productive is measuring productivity? - A large number of LLMs - Remote delivery workarounds mature Radar #radar
👍1
Technology Radar #28 The themes are: - The meteoric rise of practical AI - Accessible accessibility - Lambda quicksand - Engineering rigor meets analytics and AI - To declare or program? Radar #radar
Showing the 12 most recent of 20 posts we hold for @sre_hamster. 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“SRE Hamster” (@sre_hamster), 364 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/sre_hamster.
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.