Pratica di Shadowing: An Introduction to Basic Zabbix Concepts. Part One - Hosts, Items, and Triggers - Impara a parlare inglese con i video

Caricamento...
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.

Informazioni su questa lezione

In questa lezione, ci concentreremo sui concetti di base di Zabbix, che includono host, elementi e trigger. Imparerai come configurare il tuo primo host e creare elementi e trigger, migliorando così la tua comprensione tecnica in inglese. Inoltre, questa lezione offre un'opportunità unica di pratica di conversazione in inglese, traducendo e ripetendo il contenuto per migliorare la tua fluency e comprensione.

Vocabolario e frasi chiave

  • Host: rappresenta i punti di monitoraggio.
  • Elementi: dati raccolti dai monitor.
  • Trigger: condizioni che attivano avvisi.
  • Interfaccia SNMP: il punto di indirizzo per il monitoraggio tramite SNMP.
  • Tag del host: informazioni aggiuntive sull'ambiente del host.
  • Esecuzione semplice: controllo della disponibilità del host tramite ping.
  • Agente Zabbix: software utilizzato per raccogliere dati dal host.
  • Template: set pre-configurato di elementi e trigger.

Consigli per la pratica

Durante la visione di questo video, ti incoraggio a utilizzare la tecnica del shadowing in inglese. Ascolta attentamente ogni porzione e prova a ripetere immediatamente quello che hai sentito. Questo esercizio non solo aiuterà a migliorare la pronuncia inglese, ma anche a renderti più familiare con il gergo tecnico e le strutture linguistiche specifiche. Considera che la preferenza del relatore potrebbe essere moderata, quindi inizia a praticare a un ritmo che ti sembra confortevole.

Ricorda di registrarti mentre pratichi; riascoltare le tue registrazioni ti aiuterà a identificare le aree in cui puoi migliorare. Utilizzare il shadowspeak per cercare di emulare l'intonazione e il ritmo del relatore è un approccio altamente efficace. Inoltre, interagire con un partner di pratica può rendere l'esperienza più dinamica e coinvolgente.

Cos'è la tecnica dello Shadowing?

Shadowing è una tecnica di apprendimento delle lingue supportata da studi scientifici, originariamente sviluppata per la formazione dei traduttori professionisti e resa popolare dal poliglotta Dr. Alexander Arguelles. Il metodo è semplice ma potente: ascolti un audio in inglese di madrelingua e lo ripeti immediatamente ad alta voce — come un'ombra che segue il parlante con un ritardo di solo 1–2 secondi. A differenza dell'ascolto passivo o degli esercizi di grammatica, lo shadowing costringe il tuo cervello e i muscoli della bocca a elaborare e riprodurre simultaneamente i modelli di discorso reale. La ricerca dimostra che migliora significativamente la precisione della pronuncia, l'intonazione, il ritmo, il discorso connesso, la comprensione dell'ascolto e la fluidità del parlato — rendendolo uno dei metodi più efficaci per la preparazione alla prova di speaking dell'IELTS e per la comunicazione reale in inglese.