Monitoring system - Zabbix Piergiorgio Venuti

Monitoring system, an overview

Zabbix is a monitoring system suitable for different IT components, including networks, servers, virtual machines (VMs) and cloud services. Zabbix provides metrics such as network usage, CPU load, and disk space consumption. The software monitors operations on Linux, Hewlett Packard Unix (HP-UX), Mac OS X, Solaris, and other operating systems (OS);however, Windows monitoring is only possible through specific agents. SOD offers you the service based on your needs. Once a first contact has been established, the customer is followed throughout the process of defining the perimeter and applying the monitoring system. Alert and control level are defined in accordance with the needs.

Monitoring system with and without agents

Zabbix can be used both with agents and without agents (software dedicated to collecting information in a system). Agents are optionally installed on IT components to monitor performance and collect data. The agent then responds to a centralized management server. This information is included in the reports or presented visually in the web-based graphical interface. If there is a problem with what is being monitored, the system sends a notification or warning to the user. Agentless monitoring performs the same type of monitoring by using existing resources in a system or device to emulate an agent. The Zabbix web-based graphical interface allows users to visualize their IT environment via customizable dashboards based on widgets, charts, network maps, slideshows and reports. For example, a user can customize a report to show metrics associated with both SLAs (Service Level Agreements) and KPIs (Key Performance Indicators) on CPU loads.
Map monitoring system

An example of a map of the monitoring system within a perimeter

The three discovery modes

The monitoring system offered works through three discovery mode options: – Network discovery periodically scans an IT environment and records device type, IP address, status, uptime and downtime. – Low-level discovery (LLD) automatically creates elements, triggers and graphs based on the discovered device. Low-level discovery can create metrics from Simple Network Management Protocol (SNMP) object identifiers, Windows services, Structured Query Language (SQL) queries, network interfaces, and more. – Auto-discovery automatically starts monitoring any device discovered using a Zabbix agent. With the distributed monitoring system, scripts run remotely collect data from multiple devices in distributed locations and combine them into a single dashboard or report, such as server availability across the country.
Monitoring system dashboard

The graphical interface offers data ranging from system health to error severity and location, as well as monitoring details

The system can send notifications via e-mail, sms, telephone calls, notifications via API based on predefined events in a user’s IT environment. Another way for users to stay updated on their IT environment is through vendor applications such as M7 Monitoring or applications of their own creation.

Agentless monitoring system

Zabbix offers several monitoring options in addition to agents. A simple check can verify the availability and responsiveness of a standard service, such as notifications. Java management extensions (JMX), web monitoring, and other methods are also alternatives to using agents. In the service offered, JMX can be used to monitor Java based applications. Web monitoring is used to check the availability of websites and supports HTTP and HTTPS. The system collects data relating to the average download speed of a scenario, errors and error messages, response times and more.

The Zabbix API

The system provides web-based APIs to create new applications, automate tasks and integrate with third-party software.The JavaScript Object Notation (JSON) format is used to use the API as a front-end web interface. The Zabbix API consists of many methods which are grouped into separate APIs, each of which performs a specific service. For example, one method to create a new host is host.create; the method to log in as administrator is user.login. Using the API, monitoring system users can create applications to work with and view desired information.

Template

Templates are custom add-ons that extend the functionality of the monitoring system offered. Some models are made by Zabbix and come packaged with ready-to-use software, while others are built by users. Templates allow Zabbix users to monitor network devices from vendors such as Cisco, Dell, HP and Juniper. Other models can be used to monitor IBM, HP and Super Micro servers. Templates for application-based services include Microsoft Exchange and Exchange Server, Zenoss, PowerDNS, Authoritative Server Stats, and more. Templates can be created to monitor operating systems as well.

Conclusions

Cyberfero provides an advanced monitoring system service that will allow you to keep your entire IT infrastructure under control. The monitoring possibilities are very wide and we have covered them in another article. The web interface facilitates the management and control for your perimeter, adding the possibility to set customized alarms and specific templates for every need. If you are interested in the service, you can test it and see it working in our demo. Registration is required but no payment. Contact us for further questions or request a consultation, we are at your disposal. Useful links:

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