Trying out ZABBIX Part 8

Good evening, this is Cardy.
Since I might use ZABBIX at work, I decided to try it out personally as well, and I plan to write about ZABBIX on my blog for a while.
I am planning for a total of 8 (+2) parts.

STEP 1 Installing ZABBIX AGENT
STEP 2 Configuring ZABBIX AGENT
STEP 3 Setting up ZABBIX Server with Docker
STEP 4 Server configuration
STEP 4.5 Handling DHCP environments
STEP 5 Monitoring the moment monitoring begins
STEP 6 Defining triggers
STEP 6.5 The red text issue displayed in system information
STEP 7 Alert settings & notifications
STEP 8 Summary ← This article is here

It seems I won't be proposing Zabbix anymore, but my impression is that I'm glad I wrote about it because I gained knowledge from the experience.
How did it appear to you, the readers? Regarding Zabbix, the official website is solid and there are articles by various experts, so this article might not be very helpful, but I intended to structure it so that you can understand everything from agent installation to server construction and alert settings, so I hope it was useful to someone.

STEP 1 to STEP 7 Summary

STEP 1

While introducing integrated monitoring that collects CPU/memory, etc., and notifies via thresholds, I created a procedure for installing Agent2 on Windows, setting the Server IP/DNS to 127.0.0.1, and confirming startup.

STEP 2

I indicated the location of zabbix_agent2.conf on Windows and explained basic settings such as Server/ServerActive/Hostname using 127.0.0.1 as an example.

STEP 3

Docker verification → created docker-compose.yml → started with docker compose up -d, and checked logs with logs -f. The active check host not found error will be handled next time.

STEP 4

Logged into WebUI and resolved the "active checks: host not found" error during host registration. I explained how to correct the Server=127.0.0.1 on the agent side to the correct IP and how monitoring is reflected.

STEP 4.5

DHCP To handle the issue where the IP changes, I explained the procedure to change Agent/Server settings from IP to hostname. I also tried mDNS (.local) but stumbled on DNS resolution, so I will avoid it with Active Agent next time.

STEP 5

Availability green means connection OK, and I confirmed monitoring started by the number of items in Latest data. Collected logs are categorized by TAGS, and trends are checked with Graphs. Problems are caused by default triggers.

STEP 6

I explained the location, severity, and recovery conditions of triggers, and demonstrated service stop → PROBLEM → recovery using an Expression example.

STEP 6.5

The red text warning that appears in Zabbix's "System Information" is caused by a DB character code mismatch. I explained the procedure to convert the DB/relevant tables to utf8mb4 in MySQL on Docker to resolve the warning.

STEP 7

Localization → Email (SMTP) settings → User creation (Super admin authority is recommended) → Trigger action settings. Trigger it by stopping the service, and check the history in the action log to see if the email arrived.

Points when writing

Value the story

When thinking about the overall structure, I first cared about whether the story was solid.
If there is no story and it feels jumbled, it is difficult to convey what the situation is even when reading it, so I set a goal for each step and was conscious of a structure where the overall picture becomes visible as you read on.

Convincingness through actual screens

I am the same, but there are many times when I don't know what is being referred to even if it is explained only in words. Although the screen layout may differ depending on the version, having a screen still greatly increases the convincingness of the explanation.
Although some characters are small, I included screenshots for important parts, so if you compare the screen and the explanation, I think the operation methods and such will be conveyed firmly...!

What I want to know = What the reader wants to know

Originally, it is a style of writing while researching what I wanted to know, so the premise is that what I want to know is equal to what the reader wants to know💦
The places where you stumble and get stuck are surely the same for everyone lol
In that sense, if I were to set up Zabbix on another PC again, I think I could build the same environment by reviewing from STEP 1, so if there is anyone who wants to build a Zabbix environment, I think it was a series that could be a reference.

Finally

I intended to finish writing all 8 parts in about a week, but it took more time than I expected.
Even so, I think it turned out to be a good article (self-praise lol)🙌

Thank you for staying with me until the end🙇
I would like to continue to send out various information on note, so please feel free to follow me.