Acindar optimizes the monitoring of its IT infrastructure with Zabbix 7.0
CTL designed and implemented a centralized monitoring architecture using Zabbix 7.0 for Acindar, enabling the company to unify the observability of its distributed infrastructure, improve early incident detection, and build a scalable foundation for operational automation.
Context
Acindar operates a critical, distributed technology infrastructure that supports key business processes. As the environment grew in scale, diversity, and complexity, monitoring ceased to be merely an operational matter; it became a strategic necessity for maintaining availability, performance, and stability across various sites and services.
The challenge
Before the project, infrastructure monitoring was handled using multiple isolated tools, each associated with different types of devices. In practice, this required working with several platforms simultaneously to monitor switches, servers, UPS systems, and other critical components, without a consolidated view of the environment.
- Monitoring distributed across different tools depending on the hardware or technology.
- Lack of flexibility in configuring and tailoring monitoring to the actual needs of the IT department.
- Lack of a unified view to link infrastructure, services, and business impact.
- Difficulty scaling monitoring efforts in an increasingly broad, diverse, and critical environment.
- The need to improve performance without compromising operational continuity during the migration.
What Acindar needed to address
The need went beyond simply updating a platform. The goal was to centralize monitoring within a single system capable of providing end-to-end observability, correlating devices and services, simplifying day-to-day operations, and enabling a smooth transition toward automation and faster response times.
The initial situation
The underlying problem was a lack of situational clarity. When an alert was triggered in a specific component, it wasn’t always possible to quickly determine which other devices or services might be affected. In an industrial and distributed environment, this leads to greater operational friction, longer analysis times, and greater reliance on individual expertise.
The solution
CTL designed and implemented a new monitoring architecture based on Zabbix 7.0, optimized to manage large volumes of metrics and events. The project encompassed not only the technical deployment but also the need to build a platform that would be useful to the operations team from the outset and could evolve as the infrastructure grew.
Locations and operating environments
Servers, systems, and critical components located in different locations.
Distributed proxies
Collecting metrics locally to improve efficiency and maintain site-specific context.
Zabbix Central + MySQL
Unified management, dedicated storage, and a solid foundation for alerts, visualization, and automation.
Architectural components
- Central Zabbix server for comprehensive monitoring management.
- Dedicated MySQL database for storing metrics and events.
- Remote proxies for local data collection and central consolidation.
- Integration with Active Directory.
- Linux-based infrastructure (Ubuntu Server).
What this design achieved
- Consolidating monitoring into a single platform.
- Greater ability to represent heterogeneous infrastructure.
- Improved performance and management of large volumes of metrics.
- Platform ready for event correlation and new automations.
An approach designed for real-world adoption
According to feedback from the client following the implementation, one of the most important factors was the phased approach. Given the scale of the environment, moving forward incrementally allowed us to fine-tune models, adjust thresholds, and refine correlations without overwhelming operators with irrelevant alerts. This enabled the tool to demonstrate value early on and ensured a smooth adoption process.
Phased implementation
To mitigate risks and ensure a smooth transition, the project was carried out in clearly defined technical phases, from the initial analysis through to the validation of the environment and the contingency plan.
Requirements Analysis
We evaluated the number of hosts, the number of metrics, the network architecture, and performance requirements to define a platform capable of scaling.
Preparing the environment
Installation of MySQL, deployment of Zabbix 7.0, updating of Apache and PHP, and integration of the necessary libraries for the stack.
System Settings
Integration with existing infrastructure, proxy configuration, host setup, and parameter tuning to optimize performance.
Validation and testing
Monitoring, performance, stability, and metrics visualization tests were conducted to confirm the integration and operation of the environment.
Contingency plan
Snapshots of the existing environment were taken, and a rollback plan was established to minimize operational risks during the migration.
Project Approach
Beyond the technical implementation, one of the key strengths was avoiding a sudden rollout. The phased approach allowed us to manage the evolution of the monitoring process, minimize initial disruptions, and build a more solid operational foundation for the team.
What changed in the operation
With the new platform, Acindar moved from fragmented monitoring to an operation characterized by greater clarity, traceability, and responsiveness. The change was not merely visual or technological: it transformed the way incidents are interpreted, alerts are prioritized, and actions are taken in response to the environment.
Consolidating everything onto a single platform made it possible to create maps, dashboards, and graphical views showing the relationships between devices and services.
The alerts began delivering value early on, helping to detect issues before they escalated into major incidents.
The platform paved the way for automated remediation and a faster response to known incidents.
The architecture was set up to support greater coverage, increased automation, and new levels of observability.
Early detection and diagnosis
One of the most tangible changes highlighted by the client was the ability to receive timely and accurate alerts, backed by clear evidence, enabling them to take action before issues impacted critical processes. This improved the speed of diagnosis and the team’s ability to respond with greater context and less uncertainty.
Automation and remediation
Another key feature was the implementation of automated remediation processes for certain services that were prone to outages or required manual restarts. This capability reduces recovery times, frees the team from repetitive tasks, and reduces reliance on specialists for simple but urgent incidents.
The customer's perspective
The post-project interview makes one thing clear: the value of the implementation lay not only in modernizing a tool, but in changing the very logic of monitoring. The client describes a shift from a fragmented and reactive approach to a platform capable of providing true observability, operational context, and a solid foundation for automation.
Before the project, monitoring was carried out using multiple isolated tools, which required working with several platforms simultaneously, without a consolidated view of the infrastructure.
The lack of flexibility and configurability made it impossible to link devices, create maps, and understand the actual impact of a failure on business processes.
One of the main objectives was to achieve real-time observability across the entire technology infrastructure, linking devices and services to enable end-to-end monitoring.
Centralizing monitoring made it possible to receive timely and accurate alerts, facilitating the early detection of faults that might previously have gone unnoticed.
The creation of maps, dashboards, and graphical views improved the immediate understanding of the overall status of the environment and made daily operations more efficient.
Monitoring ceased to be merely reactive and began to evolve toward anticipation and intelligent automation, with more integrations and an ever-expanding scope.
Impact on daily operations
With the platform now up and running, the team can anticipate problems before they disrupt operations, respond more quickly, and make technical decisions based on more accurate information. The impact is evident both in day-to-day operations and in the department’s operational maturity.
- Improved interpretation of alerts thanks to standardization and consistent criteria.
- Shorter learning curve for operators.
- Greater ability to respond to incidents without always having to rely on technical escalation.
- Dashboards and automated reports to identify patterns and early warning signs.
- Transition from a reactive approach to a proactive model based on continuous monitoring.
Why CTL
In the interview, the client also highlights the value of the partner. They didn’t just choose a tool; they chose a team that understood Zabbix and, at the same time, the operational realities of the IT department. The phased approach, smooth technical communication, and the ability to tailor the platform to specific needs were key differentiators in the project.
Next steps
The project doesn't end with the initial implementation. The platform continues to evolve as the number and variety of monitored devices grow. This growth enables new levels of observability, greater automation, and increasingly proactive operations.
Prioritization of alerts
Automation and classification by severity, channel, and responsible team.
Integrations
Integration with incident and request management systems to automatically log events.
Wider coverage
Exploring new levels of monitoring for specific devices and applications.
Scalable IT monitoring with Zabbix for mission-critical environments
We design centralized monitoring architectures for organizations that need real visibility, improved performance, and a solid foundation for automating their operations.