Zabbix 7.2 major version is now available!

Zabbix 7.2 introduces various new widgets and visualization features and adds new ways to improve your monitoring, automation, and alerting workflows.

#zabbix #monitoring

Zabbix 7.2 introduces the Top Items widget, replacing the Data Overview widget for a clearer and more customizable metric display. Use item patterns for detailed data selection and visualize your metrics with bars, indicators, or sparklines.

#zabbix #monitoring

Discover and track NVIDIA GPU performance metrics like utilization, power, and temperature. Zabbix Agent 2 now supports automatic discovery and monitoring* of NVIDIA GPUs on both Linux and Windows environments.

* Available in Zabbix 7.2.1 release

#zabbix #monitoring

Monitor network devices that rely on NETCONF with the new SSH subsystem support. Invoke remote commands and extend your monitoring capabilities to manage more complex network setups.

#zabbix #monitoring

Add context to your metrics with Sparkline charts. Supported in Item value, Top hosts and Top items widgets, sparklines provide an easy way to get new insights about your data.

#zabbix #monitoring

The Host Card widget provides a customizable host overview, including host and interface status, problem counts, inventory data, and more.

#zabbix #monitoring

#zabbix #monitoring

8. Event sourcing

The #event sourcing design #pattern is used in microservices when a developer wants to capture all changes in an entity’s state. Using event stores like Kafka or alternatives will help keep track of event changes and can even function as a message broker. A message broker helps with the communication between different microservices, #monitoring messages and ensuring communication is reliable and stable.

Step 1: Begin by evaluating your current #monolithic #application. Identify its components and determine which parts can be shifted to #microservices.

Step 2: Break down the monolith into specific #business functions. Each microservice should represent a distinct capability that aligns with your business needs.

Step 3: Implement the Strangler Pattern to gradually replace parts of the monolithic application with microservices. This method allows for a smooth migration without a complete transition at once.

Step 4: Establish clear #APIs and contracts for your microservices. This ensures they can communicate effectively and interact seamlessly.

Step 5: Create Continuous Integration and Continuous Deployment (CI/CD) pipelines. This automates testing and deployment, enabling faster and more reliable releases.

Step 6: Introduce mechanisms for #service discovery so that microservices can dynamically locate and communicate with each other, enhancing flexibility.

Step 7: Set up centralized logging and #monitoring tools. This provides insights into the #performance of your microservices, helping to identify and resolve issues quickly.

Step 8: Ensure consistent management of cross-cutting concerns, such as #security and authentication, across all microservices to maintain system integrity.

Step 9: Take an iterative approach to your microservices architecture. Continuously refine and expand your services based on feedback and changing requirements.

#Digital Experience #Monitoring (DEM)

Digital Experience Monitoring (#DEM) emphasizes the importance of understanding user behavior across diverse applications and networks. By leveraging advanced #network #monitoring tools, organizations can gain insights into #application performance and user experience, ensuring optimal responsiveness.

AI-Native Containers

Containers with #AI capabilities help automate #monitoring, resource optimization, and log analysis.

2. Sidecar Pattern 🚗

The Sidecar #Pattern introduces a secondary #container, known as a sidecar, alongside the main #application container. This sidecar container extends or enhances the functionality of the primary container without affecting its core logic. This pattern is valuable for tasks such as #logging 📝, #monitoring 📊, or handling additional responsibilities.