In today’s topic let’s talk about section “Administration” => “Queue”.
Zabbix queue also called delayed metrics represents data that is currently missing inside the monitoring tool.
This topic is related to template development from scratch, bulk data input, and a lot of dependable items having different preprocessing steps each.
If these keywords resonate with you, keep reading.
In today’s class let’s talk about where the disk space goes. Which items and hosts objects consume the disk space the most.
In this lab, let’s practice to create an on-screen report of the data (most recent metrics) which is very important for us.
This post represents one technique how to advance from functionality under:
“Monitoring” => “Overview”.
In this lab, we will list all devices which are not reachable by a monitoring tool. This is good when we want to improve the overall monitoring experience and decrease the size queue (metrics which has not been arrived at the instance).
Today we are talking about a use case when it’s impossible to find a proper way to write a recovery expression for the Zabbix trigger. In other words, we know how to identify problems. But there is no good way to detect when the problem is gone.
In this lab we will use a bash environment and utilities ‘curl’ and ‘jq’ to perform Zabbix API calls, do some scripting.
Zabbix API calls can be used through the graphical user interface (GUI), no need to jump to scripting. An application to perform API calls is called Postman.
Have you ever wanted to automatically discover and monitor all your listening TCP ports for one machine? In this blog post, we will teach you another simple way to do it.
Today we will share knowledge on how to detect if time settings are off your Windows or Linux machine.