Zabbix: monitoraggio ICT Piergiorgio Venuti

Zabbix: Web console for monitoring

An indispensable tool for keeping complex infrastructure controlled is a monitoring system. Cyberfero Web Console does just that: it offers the tools to control a network of machines and devices to verify its efficiency. Web Console is based on Zabbix, a scalable Open Source platform with huge capabilities.

Among the advantages of the Cyberfero Web Console, there are the possibility of using agent less under some circumstances the great possibility of customization. The platform offered allows scripting in various languages, including Python, Perl or directly in the shell, just to give examples.

Monitoring with Web Console and Zabbix

To collect data from the infrastructure, it is necessary to install so-called software agents for the machines to be monitored. These software use native processes and free from the need to have dedicated environments such as Java or .Net.

The data collected by the agents are sent to a server that collects all the metrics and provides them to the console. From here it is then possible to analyze them, manipulate them and set triggers of notifications or automations useful for management.

When communicating between the components of the Zabbix monitoring system, only authorized IPs are accepted. Since the other connections are not accepted, security is guaranteed during data transfers between the software.

Web Console functionality

Every aspect of the infrastructure can be monitored through the Web Console offered by Cyberfero. Even if it is not possible to install additional software, there is a limited control action without agents installed. This solution allows you to collect metrics on the responsiveness and availability of standard services, such as mail or web servers.

zabbix

Scalability of data collection

The Zabbix system offered by the Cyberfero Web Console is able to recover data and metrics from any device or software. Through the use of different control protocols, the available software agents are able to collect any type of data.

Monitoring supported

Through the Zabbix agents used, the data collected is complete and includes both hardware and software metrics.

For example, metrics from infrastructure network hardware are collected by SNMP agents. An optimal solution for network capacity management and planning. The measurements include the use of memory, CPU, RAM and the status of the logical ports of the controlled peripherals.

The controls include more levels of system complexity. Agents can collect information from:

– Hardware (CPU, fans, storage media, etc.)
– Network (ports used, memory usage, etc.)
– Operating systems (Unix, Windows, MacOs, etc.)
– Middleware software (Oracle, MySql, Apache, etc.)
– Web applications
– Cloud resources

Monitoring web services

The built-in system for monitoring web services is worthy of specific mention.

Through the use of this function, it is possible to define the sequential steps to be performed for the analysis of a website. It is possible to monitor the site response speed and downloads, for example. But also availability, as well as data relating to e-commerce portals and other web based applications.

Scalability ‘

Cyberfero Web Console is scalable and adaptable to the size of the infrastructure. From the small corporate IT network, to even very complex solutions from thousands of machines and devices. A single installation can support up to 3,000,000 checks per minute, collecting gigabytes of data per day.

Furthermore, through the use of proxy software components, it is possible to distribute the data collection and decentralize the calculation operations. In this way the control of ports and connections is more easily managed.

You can organize your network into sections where metrics are collected and calculated independently. The proxy in charge of the calculation will be the only connection outgoing from the subsystem.

Notifications and triggers

An efficient monitoring strategy provides not only the collection of data, but also a system for which any anomaly is reported in order to be able to intervene promptly.

The Cyberfero Web Console implements a customizable system of triggers and notifications to be always informed in case something is not going as it should.

Ideally, once the first data is collected, the thresholds of values considered “normal” are established. On the basis of these, a notification system is customized which immediately communicates the exceeding of a safety threshold of certain parameters.

The management of metrics is thus very lightened by an automatic verification of their values. When a parameter presents an anomalous value, one would be immediately informed.

The notification methods supported are: email, SMS, Jabber or through other methods customizable through scripting.

How to request and install Web Console

It is possible to request Cyberfero Web Console after a first initial meeting with our network architect. On that occasion, the computer perimeters of the network to be monitored and what the alarm notification modes are defined.

After this first step, our team will take care of installing all the software needed to collect metrics on the systems involved. Once these operations are completed, the system will be ready and accessible from a console in the cloud. The access data are provided only after the installation of the entire control system.

From the Web Console you will be able to check all monitored metrics, check performance and manage notifications.

Download the brochure or try a demo of the Web Console.

[btnsx id=”2931″]

Useful links:

ICT Monitoring Service

How to have your computer network under control

 

Share


RSS

More Articles…

Categories …

Tags

RSS feed: Unknown Feed Unknown Feed

RSS feed: Full Disclosure Full Disclosure

  • Apache Struts2 Core Arbitrary Code Execution via OGNL Sandbox Escape November 2, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 01Description Apache Struts2 Core version 7.4.0 and below attempt to prevent arbitrary code execution via Object-Graph Navigation Language (OGNL) through several different mechanisms but only in a cursory fashion -- the libraries only guard against immediate calls evaluated by the OGNL engine via `SecurityMemberAccess`, but an allowed […]
  • Apache Struts2 Core TokenHelper Token Cryptographic Timing Side-Channel November 2, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 01Description The Apache Struts2 Core 7.4.0 and below performs session token comparisons cryptographically insecure early-exit comparison functions (e.g., `!=`, `memcmp`, byte-by-byte loops with `break`) that return as soon as the first mismatched byte is encountered. The execution time of the comparison is therefore proportional to the number […]
  • Apache Struts2 Spring Plugin Uses a Previously Closed Resource November 2, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 01Description The Apache Struts2 Spring Plugin opens a Spring `ApplicationContex` via a try-with-resources block and, outside of said block, then continues to use the closed resource, resulting in an uncaught `IllegalStateException`. This particular issue prevents proper functionality and indicates poor code quality and code review standards and […]
  • Apache Struts2 Core Integer Overflow November 2, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 01Description Apache Struts2 Core version 7.4.0 and below fails to properly prevent integer overflows, causing wrap-arounds and other issues on a downstream forced casting into types smaller than `BigInteger`. Importantly, this finding underscores why all applications using Struts and other such platforms should perform their own input […]
  • Apache Struts2 Core Cross-Origin Protection Exemption Miskeyed to a Deployment-Wide Path November 2, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 01Description Apache Struts2 Core version 7.4.0 and below's `FetchMetadataInterceptor`, `CoepInterceptor`, and `CoopInterceptor` each compare their `exemptedPaths` configuration -- a per-interceptor-reference, administrator-supplied set of paths intended to exempt specific actions from the corresponding cross-origin protection -- against `HttpServletRequest.getContextPath()`. `getContextPath()` is fixed for the entire deployed web...
  • Apache Struts2 REST Plugin Fails to Properly Parse Chunked Requests November 2, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 01Description The Apache Struts2 REST Plugin's (version 7.4.0 and below) `ContentTypeInterceptor.intercept(ActionInvocation)` only deserialises a request body and enforces the `struts.rest.content.maxLength` bound when `HttpServletRequest#getContentLength()` returns a positive value. `getContentLength()` returns `-1` whenever the `Content-Length` header is absent, which normal and appropriate for any Hypertext Transfer Protocol (HTTP)...
  • Apache Struts2 REST Plugin Untrimmed `Accept` Header Tokens Break Content Negation Fallback November 2, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 01Description The Apache Struts2 REST Plugin's `DefaultContentTypeHandlerManager.getHandlerForResponse(HttpServletRequest, HttpServletResponse)` splits the `Accept` header on commas and passes each resulting token directly to `findHandler(String)` without trimming leading or trailing whitespace. `findHandler(String)` only retries a trimmed lookup when a token contains a semicolon (`;`), so a token that merely carries […]
  • Apache Struts2 JSON Plugin Insecure Deserialisation -- Object Deserialisation Element-Count Limit Bypass November 2, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 01As of the current versions of the Apache Struts2 JSON Plugin (e.g., version 7.4.0 and the 7.5.0 snapshot dated 28 October 2026), attackers can bypass the element-count limit purported to protect Object deserialisation added to said code as part of the WW-5618 and S2-072 "hardening controls". Please […]
  • [0day-rubbish] NETGEAR RAX120 V1.2.5.18 authenticated SOAP InstallApp OS command injection to root-configured web-stack execution (6.8 Medium; conditionally 7.2 High with management exposure) October 29, 2026
    Posted by disclosure via Fulldisclosure on Oct 280day Rubbish Research Team is publicly disclosing a vulnerability in NETGEAR RAX120 (Nighthawk AX12) firmware V1.2.5.18, the WiFi 6 consumer router from NETGEAR (United States), built on the Qualcomm IPQ8074 platform. The administrative web plane of this firmware generation is a lighttpd server fronting the vendor's DNI-framework CGI […]
  • [0day-rubbish] Raritan PX3 PDU G4 firmware 4.3.14 command injection in the ping and traceroute diagnostics through an inverted hostname-validation return check (8.8) October 29, 2026
    Posted by disclosure via Fulldisclosure on Oct 280day Rubbish Research Team is publicly disclosing a vulnerability in the Raritan PX3 PDU G4, firmware version 4.3.14, the intelligent rack power distribution unit from Raritan, a Legrand company (United States). A low-privilege authenticated session converts one diagnostics request into operating-system command execution in the product's web-service context, […]

Customers