Reading Time: < 1 minuteСерія: «Історія Vezha тиждень за тижнем» • Випуск від 18.05.2026 У #103 ми прибрали типову точку помилок під час підключення […]
Reading Time: < 1 minuteSeries: “Vezha story week by week” • Issue dated 05/18/2026 In #103, we removed a common source of onboarding errors:
Reading Time: < 1 minuteСерія: «Історія Vezha тиждень за тижнем» • Випуск від 11.05.2026 У #102 ми доробили фундамент web-телеметрії: тепер Vezha знаходить access-логи
Reading Time: < 1 minuteSeries: “Vezha story week by week” • Issue dated 05/11/2026 In #102, we strengthened the web telemetry foundation: Vezha now
Reading Time: < 1 minuteSeries: “Vezha story week by week” • Issue dated 05/04/2026 In #101, we focused on file-system integrity control. Vezha now
Reading Time: < 1 minuteSeries: “Vezha story week by week” • Issue dated 04/27/2026 In #100, we closed a real gap in web monitoring:
Reading Time: 6 minutesVezha Weekly Entry #099: 7-day forensic PDF report on error IP appeared in web-stats. A release shortens the path from a traffic anomaly to concerted action by operations and security teams.
Reading Time: 3 minutesVezha Weekly Entry #098: Real-time parsing of access.log, RPS metrics, and error rate/error rate % and how it helped detect pick-up attempts and respond faster through the CRM process.
Reading Time: 3 minutesIssue #097 about Vezha: “Reliable Change Delivery”. Briefly about the changes of the week, their impact on the daily work of the teams and the next practical steps.
Reading Time: 3 minutesIssue #096 of 2026-03-30: “Public Release: What Worked” at Vezha. About the decision of the week without unnecessary theory – only the practical result and the next focus.
Reading Time: 3 minutes#095 (2026-03-23) on the Vezha blog: “Operational discipline after going public”, operational impact of updates, and next iteration priorities.
Reading Time: 3 minutesVezha Issue #094: “Reliable Change Delivery”. What did the team change this week, what effect did it have in production and what are we doing next.