Prática de Shadowing: An Introduction to Basic Zabbix Concepts. Part One - Hosts, Items, and Triggers - Aprenda a falar inglês com o YouTube

C2
Hosts, items, and triggers are the basic building blocks for data collection and problem detection in Zabbix.
⏸ Pausado
112 frases
Se as frases estiverem muito curtas ou longas, clique em Edit para ajustá-las.
1
Hosts, items, and triggers are the basic building blocks for data collection and problem detection in Zabbix.
2
Let's see how we can configure our first host and create a couple of items and triggers for it.
3
We will begin by creating a host.
4
Hosts represent our monitoring endpoints,
5
anything from servers, network hardware,
6
IoT devices, websites, applications, and any other type of endpoint.
7
Hosts needs to have a unique host name.
8
Host also must belong to at least a single host group.
9
Host groups are used for grouping and filtering and are essential for configuring Zabbix user access permissions.
10
A host can belong to an unlimited number of host groups.
11
For our first example, we will use the Cisco SNMP template to monitor our Cisco switch.
12
The template contains a pre-configured set of items and triggers,
13
and any changes made on the template will be applied on the hosts utilizing this template.
14
For SNMP checks to work,
15
we also need to define an SNMP interface.
16
An interface represents the endpoint address,
17
which the values will be polled at by Zabbix.
18
Zabbix has four types of interfaces,
19
Zabbix Agent, SNMP, IPMI, and JMX for the corresponding item types.
20
Not all items use interfaces,
21
but for these four item types, interfaces are mandatory.
22
Let's create an SNMP interface,
23
provide an address and port,
24
select the SNMP version, and provide an SNMP community.
25
There are various other settings that we can define for the host,
26
such as host-level macros, tags,
27
value maps, inventory, encryption, and IPMI settings.
28
I will add a tag for my host,
29
which will provide additional information about the host environment,
30
and skip the other settings.
31
Now let's add the host and navigate to monitoring latest data,
32
where we will be able to see the items and their values collected on this host.
33
Now let's create another host.
34
This time I will be creating a Linux host with an agent interface without any templates assigned to it.
35
Zabbix agent is already deployed on this host,
36
and we will create items and triggers for it manually.
37
Let's provide the agent interface information,
38
tag the host, and add it.
39
Now let's open host items and create our first item.
40
We will begin by creating a simple ping item to check our host availability.
41
Let's give our item a name and select its type, simple check.
42
Pings, port checks and other simple check items are executed directly by Zabbix server and do not require an agent.
43
Zabbix provides a variety of item types utilizing different data collection approaches,
44
but for now we will focus on simple check and agent items.
45
Let's select the ICMP ping key.
46
For most items, item keys are used to define what type of metric needs to be collected on a host a host.
47
For this key, all of the parameters are optional,
48
so we can remove them.
49
Items also requires selecting the correct type of information.
50
Zabbix will attempt to automatically select the correct type of information,
51
and in this case, it's numeric unsigned,
52
since the collected value will be equal either to 0 or 1.
53
The item will ping the selected host interface address.
54
Let's set the update interval to 1 minute.
55
This defines how often the ping value is collected.
56
History and trend storage periods are defined for how long do we wish to store the collected values and trends,
57
value hourly aggregates.
58
Let's also tag this item with component availability so we can use this tag to easier filter for the item value.
59
Let's add the item and proceed with adding our second item, CPU Utilization.
60
CPU Utilization on our Linux host can be retrieved by Zabbix Agent.
61
Let's select the Zabbix agent item type and select the System CPU util key.
62
This key also has various optional parameters.
63
We can click on the question mark next to the item
64
key to read more about their possible values in the Zabbix documentation.
65
Let's add the key without any parameters.
66
This way the item will use the parameter defaults to collect our values.
67
We will use the numeric float type of information,
68
since the item will collect CPU utilization in percent with fractional parts.
69
Next we will select our agent interface.
70
This will represent the address of the Zabbix agent,
71
which will be polled by Zabbix server to retrieve the item values.
72
Let's set the update interval to 30 seconds,
73
tag the item with component CPU, and create the item.
74
Now, if we navigate to latest data,
75
we can see that both of our items are successfully returning values.
76
Go back to data collection hosts and click on triggers next to our Linux server host.
77
Click Create Trigger in the top right corner of the page to create a trigger.
78
Let's create a trigger which reacts to our host being unreachable via ping.
79
Give the trigger a short name,
80
and now let's specify how the problem will be presented by configuring the EventName field.
81
I will use the builtin host.host macro in myEventName.
82
Using a built-in macro like this can be extremely useful when creating triggers on templates.
83
Instead of specifying a static event name,
84
the macro will be automatically resolved as the host name of the host on which the problem is detected.
85
Currently we're creating a trigger directly on a host,
86
so we could be using a static name here,
87
but I prefer to follow the best practice,
88
since in real life you will mostly be creating items and triggers on templates,
89
and then applying the templates on hosts.
90
Let's set the severity to high and press add to create our first trigger expression.
91
First, select the ping item,
92
then select the function which you wish to use for analyzing the collected values.
93
Zabbix provides a vast selection of functions for different kinds of use cases.
94
For our first example, we will use the last function,
95
reacting if the last collected value is equal to zero.
96
Let's insert the expression and add the trigger.
97
Now let's add our second trigger.
98
We will generate a problem if our CPU utilization is over 90%.
99
Populate the trigger and event name fields and set the severity.
100
Click Add to add the new expression.
101
Let's select the CPU utilization item and this time use the average function.
102
We will detect an issue if the average CPU utilization value over the last 5 minutes is over 90%.
103
Using the average function makes the trigger a lot less sensitive compared to using the last function.
104
Using functions fit for your use case is vital for reducing trigger flapping and preventing alert floods.
105
Let's finish the exercise by adding the trigger.
106
In total, we have created two hosts,
107
one for Cisco device monitoring via SNMP using the official Xabix template
108
and one for our Linux server with two items and triggers for ping and CPU monitoring created directly on the host.
109
But this is just the beginning.
110
Feel free to explore our documentation,
111
videos and blog articles to find more information about various types of items,
112
trigger function use cases and much more.

Baixar aplicativo

Pontuação por IA para cada frase que você fala

Escaneie para baixar
Escaneie para baixar
Download on theApp Store
Get it onGoogle Play
TRENDING

Populares

Sobre esta Aula

Nesta seção, você terá a oportunidade de praticar conceitos básicos essenciais para a coleta de dados e detecção de problemas no Zabbix. Vamos explorar as definições de hosts, itens e triggers, que são os componentes fundamentais dessa ferramenta. Através deste conteúdo, você aprenderá a configurar seu primeiro host, criar itens e triggers, além de entender a importância dos grupos de hosts. Essa prática ajudará não só na compreensão técnica, mas também no desenvolvimento da sua fluência em inglês técnico.

Vocabulário e Frases Chave

  • Hosts - Referem-se aos pontos de monitoramento, como servidores e dispositivos.
  • Items - Itens que coletam dados de um host.
  • Triggers - Mecanismos que alertam sobre problemas detectados.
  • SNMP - Protocolo usado para monitoramento de dispositivos de rede.
  • Interface - Endereço de onde os dados serão coletados.
  • Agente - Um tipo de interface que coleta dados diretamente do host.
  • Templates - Conjuntos pré-configurados de itens e triggers para facilitar a configuração.
  • Ping - Um tipo de verificação simples para checar a disponibilidade de um host.

Dicas de Prática

Para maximizar sua experiência de aprendizagem, sugerimos que você utilize a técnica de shadowing. Isso significa imitar a fala do apresentador enquanto assiste ao vídeo em um shadowing site. A velocidade moderada do locutor facilita a repetição, permitindo que você acompanhe o tom e a entonação corretos. Escute atentamente e pause o vídeo sempre que necessário para praticar cada frase, focando na pronúncia de termos técnicos como hosts, items e triggers. Essa prática ajuda a incorporar o vocabulário especializado em seu discurso.

Encorajamos você a explorar plataformas de shadowspeak para se familiarizar com a terminologia em questão. Ao repetir e praticar a shadow speech, você não só reforçará seu conhecimento técnico como também aprimorará sua fluência em inglês, uma habilidade essencial no ambiente tecnológico atual.

O que é a Técnica de Shadowing?

Shadowing é uma técnica de aprendizado de idiomas com base científica, originalmente desenvolvida para o treinamento de intérpretes profissionais. O método é simples, mas poderoso: você ouve áudio em inglês nativo e repete imediatamente em voz alta — como uma sombra seguindo o falante com 1-2 segundos de atraso. Pesquisas mostram melhora significativa na precisão da pronúncia, entonação, ritmo, sons conectados, compreensão auditiva e fluência na fala.

☕ Pague-nos um café