Series: “Vezha story week by week” • Issue dated 04/13/2026
In issue #098, we talk about Vezha on the topic “New feature of port/script scanning and CRM-reaction detection”: what exactly the team changed this week and what practical effect it had in production.
The Public Release and First Weeks of Scale phase required discipline: delivering value every week, but without losing stability. This is how the neemle team prioritized issue #098.
Context of the week
For issue #098, the key was to work on the “New feature of port/script scanning and CRM-reaction detection” topic without too much noise: less declarations, more proven improvements that the team experienced in daily scenarios.
We checked each change with a simple criterion: did it become easier for the operator to work already this week. In the context of “New port/script scanning and CRM-reaction detection feature”, this helped weed out solutions that look good in the demo but are not useful in practice.
What has changed in the product
- [vezha] added parsing
access.login real time without waiting for batch processing. - [vezha] introduced operational load metrics:
RPS,error rateanderror rate %for a quick assessment of the service status. - [vezha] strengthened the response script: when the pattern looks like a pick, the case immediately takes priority in the team’s workflow.
The key idea of the week was simple: not to multiply individual alerts, but to give the operator a short and readable picture of what is happening in the traffic right now.
Architectural vector
In this cycle, we strengthened the boundaries between platform components. In the topic “New port/script scanning and CRM reaction detection feature”, this means more predictable updates of individual parts and fewer side effects.
Operationally, this gave a clear effect: fewer unnecessary returns to already closed tasks, faster localization of problems and a smoother release rhythm. For the block “New detection function of port/script scanning and CRM-reaction” this is critically important.
Product conclusions of the week
This week proved a simple thing: stability and clear communication between teams is more beneficial than a “perfect” feature in isolation. In the topic “New detection function of port/script scanning and CRM-reaction” this became the determining factor.
For scalability, we removed several small but painful points in daily processes. In the topic “New port/script scanning and CRM reaction detection feature” this gave a noticeably smoother operation.
New functionality: real-time access.log parsing and CRM reaction
This week we brought processing into production focus access.log in live mode. This made it possible to see anomalies not after the fact, but in the moment: jumps RPS, growth error rate and the percentage of errors in a short time window.
In practice, this produced an important result: several incidents that previously appeared to be “noise” were classified as recruitment attempts. The team then ran the agreed CRM scenario with the customer faster and reduced the time to a controlled response.
What’s next?
For the next week in the direction of “New feature of port/script scanning and CRM-reaction detection”, the plan is simple: to establish stability, remove residual points of friction and confirm quality on real customer scenarios.
The operational view: what it means for customers
The changes were evaluated operationally: whether it is easier for the person on duty to make a decision and whether there is less manual work at a critical moment. For “New port/script scanning and CRM reaction detection function” this is the main quality criterion.
When the signal is stable and the context is sufficient, the team moves from discussions to action. This week, in the task “New function of detecting port/script scanning and CRM-reaction”, we worked precisely to make such “hangs” in the process become less.
What we do not disclose publicly and why
In the public part, we keep the focus on the practical effect: what has changed for the user, how it affected the operational process and what still needs to be proven in “The new detection function of port/script scanning and CRM reaction”.
In each issue, especially #098, we keep an honest tone: we show the actual state of the New port/script scanning and CRM reaction detection feature and the solutions that really affect the work of teams.
Practical summary of the week
Summary of issue #098 dated 2026-04-13: New port/script scanning and CRM reaction detection feature, we took a step towards a more predictable and manageable experience without unnecessary complexity.
Хочете перевірити Vezha на вашій інфраструктурі? Перейдіть на vezha.io та надішліть запит на демо.