|
|
zabbix.com.rss_rdf.xml - sfeed_tests - sfeed tests and RSS and Atom files |
|
|
 |
git clone git://git.codemadness.org/sfeed_tests (git://git.codemadness.org) |
|
|
 |
Log |
|
|
|
Files |
|
|
|
Refs |
|
|
|
README |
|
|
|
LICENSE |
|
|
|
--- |
|
|
|
zabbix.com.rss_rdf.xml (21143B) |
|
|
|
--- |
|
|
|
1 <?xml version="1.0" encoding="UTF-8"?> |
|
|
|
2 <!-- generator="FeedCreator 1.8" --> |
|
|
|
3 <?xml-stylesheet href="https://www.zabbix.com/documentation/current/lib/exe/css.php?s=feed" type="text/css"?> |
|
|
|
4 <rdf:RDF |
|
|
|
5 xmlns="http://purl.org/rss/1.0/" |
|
|
|
6 xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" |
|
|
|
7 xmlns:slash="http://purl.org/rss/1.0/modules/slash/" |
|
|
|
8 xmlns:dc="http://purl.org/dc/elements/1.1/"> |
|
|
|
9 <channel rdf:about="https://www.zabbix.com/documentation/current/feed.php"> |
|
|
|
10 <title>Zabbix Documentation 5.4</title> |
|
|
|
11 <description></description> |
|
|
|
12 <link>https://www.zabbix.com/documentation/current/</link> |
|
|
|
13 <image rdf:resource="https://www.zabbix.com/documentation/current/lib/tpl/zabbix/images/favicon.ico" /> |
|
|
|
14 <dc:date>2021-11-21T11:51:15+0000</dc:date> |
|
|
|
15 <items> |
|
|
|
16 <rdf:Seq> |
|
|
|
17 <rdf:li rdf:resource="https://www.zabbix.com/documentation/current/manual/api/reference/hostinterface/object?rev=1637082086&do=diff"/> |
|
|
|
18 <rdf:li rdf:resource="https://www.zabbix.com/documentation/current/manual/api/reference/hostinterface/create?rev=1637081029&do=diff"/> |
|
|
|
19 <rdf:li rdf:resource="https://www.zabbix.com/documentation/current/manual/xml_export_import/hosts?rev=1637061732&do=diff"/> |
|
|
|
20 <rdf:li rdf:resource="https://www.zabbix.com/documentation/current/manual/discovery/auto_registration?rev=1636989991&do=diff"/> |
|
|
|
21 <rdf:li rdf:resource="https://www.zabbix.com/documentation/current/manual/discovery/network_discovery/rule?rev=1636989234&do=diff"/> |
|
|
|
22 <rdf:li rdf:resource="https://www.zabbix.com/documentation/current/manual/encryption/using_certificates?rev=1636811731&do=diff"/> |
|
|
|
23 <rdf:li rdf:resource="https://www.zabbix.com/documentation/current/manual/encryption?rev=1636811552&do=diff"/> |
|
|
|
24 <rdf:li rdf:resource="https://www.zabbix.com/documentation/current/manual/config/secrets?rev=1636811433&do=diff"/> |
|
|
|
25 <rdf:li rdf:resource="https://www.zabbix.com/documentation/current/manual/config/tagging?rev=1636811285&do=diff"/> |
|
|
|
26 <rdf:li rdf:resource="https://www.zabbix.com/documentation/current/manual/config/items/itemtypes/odbc_checks/unixodbc_mssql?rev=1636811125&do=diff"/> |
|
|
|
27 <rdf:li rdf:resource="https://www.zabbix.com/documentation/current/manual/config/items/itemtypes/odbc_checks/unixodbc_postgresql?rev=1636810990&do=diff"/> |
|
|
|
28 <rdf:li rdf:resource="https://www.zabbix.com/documentation/current/manual/config/items/itemtypes/log_items?rev=1636810398&do=diff"/> |
|
|
|
29 <rdf:li rdf:resource="https://www.zabbix.com/documentation/current/manual/config/items/preprocessing/preprocessing_details?rev=1636810192&do=diff"/> |
|
|
|
30 <rdf:li rdf:resource="https://www.zabbix.com/documentation/current/manual/appendix/command_execution?rev=1636809999&do=diff"/> |
|
|
|
31 <rdf:li rdf:resource="https://www.zabbix.com/documentation/current/manual/appliance?rev=1636809579&do=diff"/> |
|
|
|
32 <rdf:li rdf:resource="https://www.zabbix.com/documentation/current/manual/appendix?rev=1636809224&do=diff"/> |
|
|
|
33 <rdf:li rdf:resource="https://www.zabbix.com/documentation/current/manual/installation/requirements/best_practices?rev=1636807071&do=diff"/> |
|
|
|
34 <rdf:li rdf:resource="https://www.zabbix.com/documentation/current/manual/appendix/items/proc_mem_notes?rev=1636711903&do=diff"/> |
|
|
|
35 <rdf:li rdf:resource="https://www.zabbix.com/documentation/current/manual/appendix/faq?rev=1636709671&do=diff"/> |
|
|
|
36 <rdf:li rdf:resource="https://www.zabbix.com/documentation/current/manual/appendix/suffixes?rev=1636649048&do=diff"/> |
|
|
|
37 </rdf:Seq> |
|
|
|
38 </items> |
|
|
|
39 </channel> |
|
|
|
40 <image rdf:about="https://www.zabbix.com/documentation/current/lib/tpl/zabbix/images/favicon.ico"> |
|
|
|
41 <title>Zabbix Documentation 5.4</title> |
|
|
|
42 <link>https://www.zabbix.com/documentation/current/</link> |
|
|
|
43 <url>https://www.zabbix.com/documentation/current/lib/tpl/zabbix/images/favicon.ico</url> |
|
|
|
44 </image> |
|
|
|
45 <item rdf:about="https://www.zabbix.com/documentation/current/manual/api/reference/hostinterface/object?rev=1637082086&do=diff"> |
|
|
|
46 <dc:format>text/html</dc:format> |
|
|
|
47 <dc:date>2021-11-16T17:01:26+0000</dc:date> |
|
|
|
48 <dc:creator>martins-v (martins-v@undisclosed.example.com)</dc:creator> |
|
|
|
49 <title>> Host interface object - 'community' is required for v1/v2, not merely used (ZBX-20198)</title> |
|
|
|
50 <link>https://www.zabbix.com/documentation/current/manual/api/reference/hostinterface/object?rev=1637082086&do=diff</link> |
|
|
|
51 <description>> Host interface object |
|
|
|
52 |
|
|
|
53 The following objects are directly related to the hostinterface API. |
|
|
|
54 |
|
|
|
55 Host interface |
|
|
|
56 |
|
|
|
57 The host interface object has the following properties. |
|
|
|
58 DNSDNS Property Type Description available integer (readonly) Availability of host interface.</description> |
|
|
|
59 </item> |
|
|
|
60 <item rdf:about="https://www.zabbix.com/documentation/current/manual/api/reference/hostinterface/create?rev=1637081029&do=diff"> |
|
|
|
61 <dc:format>text/html</dc:format> |
|
|
|
62 <dc:date>2021-11-16T16:43:49+0000</dc:date> |
|
|
|
63 <dc:creator>martins-v (martins-v@undisclosed.example.com)</dc:creator> |
|
|
|
64 <title>hostinterface.create - adding example for creating interface with snmp details (ZBX-20198)</title> |
|
|
|
65 <link>https://www.zabbix.com/documentation/current/manual/api/reference/hostinterface/create?rev=1637081029&do=diff</link> |
|
|
|
66 <description>hostinterface.create |
|
|
|
67 |
|
|
|
68 Description |
|
|
|
69 |
|
|
|
70 object hostinterface.create(object/array hostInterfaces) |
|
|
|
71 |
|
|
|
72 This method allows to create new host interfaces. |
|
|
|
73 AdminSuper adminUser roles |
|
|
|
74 Parameters |
|
|
|
75 |
|
|
|
76 (object/array) Host interfaces to create. The method accepts host interfaces with the</description> |
|
|
|
77 </item> |
|
|
|
78 <item rdf:about="https://www.zabbix.com/documentation/current/manual/xml_export_import/hosts?rev=1637061732&do=diff"> |
|
|
|
79 <dc:format>text/html</dc:format> |
|
|
|
80 <dc:date>2021-11-16T11:22:12+0000</dc:date> |
|
|
|
81 <dc:creator>martins-v (martins-v@undisclosed.example.com)</dc:creator> |
|
|
|
82 <title>3 Hosts - '0' delay for trapper item export (ZBX-20121)</title> |
|
|
|
83 <link>https://www.zabbix.com/documentation/current/manual/xml_export_import/hosts?rev=1637061732&do=diff</link> |
|
|
|
84 <description>3 Hosts |
|
|
|
85 |
|
|
|
86 Overview |
|
|
|
87 |
|
|
|
88 Hosts are exported with many related objects and object relations. |
|
|
|
89 |
|
|
|
90 Host export contains: |
|
|
|
91 |
|
|
|
92 * linked host groups |
|
|
|
93 * host data |
|
|
|
94 * template linkage |
|
|
|
95 * host group linkage |
|
|
|
96 * host interfaces |
|
|
|
97 * directly linked items |
|
|
|
98 * directly linked triggers</description> |
|
|
|
99 </item> |
|
|
|
100 <item rdf:about="https://www.zabbix.com/documentation/current/manual/discovery/auto_registration?rev=1636989991&do=diff"> |
|
|
|
101 <dc:format>text/html</dc:format> |
|
|
|
102 <dc:date>2021-11-15T15:26:31+0000</dc:date> |
|
|
|
103 <dc:creator>marinagen (marinagen@undisclosed.example.com)</dc:creator> |
|
|
|
104 <title>2 Active agent autoregistration - fixing syntax</title> |
|
|
|
105 <link>https://www.zabbix.com/documentation/current/manual/discovery/auto_registration?rev=1636989991&do=diff</link> |
|
|
|
106 <description>2 Active agent autoregistration |
|
|
|
107 |
|
|
|
108 Overview |
|
|
|
109 |
|
|
|
110 It is possible to allow active Zabbix agent autoregistration, after which the server can start monitoring them. This way new hosts can be added for monitoring without configuring them manually on the server.</description> |
|
|
|
111 </item> |
|
|
|
112 <item rdf:about="https://www.zabbix.com/documentation/current/manual/discovery/network_discovery/rule?rev=1636989234&do=diff"> |
|
|
|
113 <dc:format>text/html</dc:format> |
|
|
|
114 <dc:date>2021-11-15T15:13:54+0000</dc:date> |
|
|
|
115 <dc:creator>marinagen (marinagen@undisclosed.example.com)</dc:creator> |
|
|
|
116 <title>1 Configuring a network discovery rule - fixing syntax</title> |
|
|
|
117 <link>https://www.zabbix.com/documentation/current/manual/discovery/network_discovery/rule?rev=1636989234&do=diff</link> |
|
|
|
118 <description>1 Configuring a network discovery rule |
|
|
|
119 |
|
|
|
120 Overview |
|
|
|
121 |
|
|
|
122 To configure a network discovery rule used by Zabbix to discover hosts and services: |
|
|
|
123 |
|
|
|
124 * Go to Configuration → Discovery |
|
|
|
125 * Click on Create rule (or on the rule name to edit an existing one) |
|
|
|
126 * Edit the discovery rule attributes</description> |
|
|
|
127 </item> |
|
|
|
128 <item rdf:about="https://www.zabbix.com/documentation/current/manual/encryption/using_certificates?rev=1636811731&do=diff"> |
|
|
|
129 <dc:format>text/html</dc:format> |
|
|
|
130 <dc:date>2021-11-13T13:55:31+0000</dc:date> |
|
|
|
131 <dc:creator>marinagen (marinagen@undisclosed.example.com)</dc:creator> |
|
|
|
132 <title>1 Using certificates - fixing syntax</title> |
|
|
|
133 <link>https://www.zabbix.com/documentation/current/manual/encryption/using_certificates?rev=1636811731&do=diff</link> |
|
|
|
134 <description>1 Using certificates |
|
|
|
135 |
|
|
|
136 Overview |
|
|
|
137 |
|
|
|
138 Zabbix can use RSA certificates in PEM format, signed by a public or in-house certificate authority (CA). Certificate verification is done against a pre-configured CA certificate. Optionally certificate revocation lists (CRL) can be used. Each Zabbix component can have only one certificate configured.</description> |
|
|
|
139 </item> |
|
|
|
140 <item rdf:about="https://www.zabbix.com/documentation/current/manual/encryption?rev=1636811552&do=diff"> |
|
|
|
141 <dc:format>text/html</dc:format> |
|
|
|
142 <dc:date>2021-11-13T13:52:32+0000</dc:date> |
|
|
|
143 <dc:creator>marinagen (marinagen@undisclosed.example.com)</dc:creator> |
|
|
|
144 <title>17. Encryption - fixing syntax</title> |
|
|
|
145 <link>https://www.zabbix.com/documentation/current/manual/encryption?rev=1636811552&do=diff</link> |
|
|
|
146 <description>17. Encryption |
|
|
|
147 |
|
|
|
148 Overview |
|
|
|
149 |
|
|
|
150 Zabbix supports encrypted communications between Zabbix components using Transport Layer Security (TLS) protocol v.1.2 and 1.3 (depending on the crypto library). Certificate-based and pre-shared key-based encryption is supported.</description> |
|
|
|
151 </item> |
|
|
|
152 <item rdf:about="https://www.zabbix.com/documentation/current/manual/config/secrets?rev=1636811433&do=diff"> |
|
|
|
153 <dc:format>text/html</dc:format> |
|
|
|
154 <dc:date>2021-11-13T13:50:33+0000</dc:date> |
|
|
|
155 <dc:creator>marinagen (marinagen@undisclosed.example.com)</dc:creator> |
|
|
|
156 <title>13 Storage of secrets - fixing syntax</title> |
|
|
|
157 <link>https://www.zabbix.com/documentation/current/manual/config/secrets?rev=1636811433&do=diff</link> |
|
|
|
158 <description>13 Storage of secrets |
|
|
|
159 |
|
|
|
160 Overview |
|
|
|
161 |
|
|
|
162 It is possible to store some sensitive information secretly in HashiCorp Vault KV Secrets Engine - Version 2. Secrets can be saved for: |
|
|
|
163 |
|
|
|
164 * user macro values |
|
|
|
165 * database access credentials |
|
|
|
166 |
|
|
|
167 Zabbix provides read-only access to the secrets in Vault, assuming that secrets are managed by someone else.</description> |
|
|
|
168 </item> |
|
|
|
169 <item rdf:about="https://www.zabbix.com/documentation/current/manual/config/tagging?rev=1636811285&do=diff"> |
|
|
|
170 <dc:format>text/html</dc:format> |
|
|
|
171 <dc:date>2021-11-13T13:48:05+0000</dc:date> |
|
|
|
172 <dc:creator>marinagen (marinagen@undisclosed.example.com)</dc:creator> |
|
|
|
173 <title>6 Tagging - fixing syntax</title> |
|
|
|
174 <link>https://www.zabbix.com/documentation/current/manual/config/tagging?rev=1636811285&do=diff</link> |
|
|
|
175 <description>6 Tagging |
|
|
|
176 |
|
|
|
177 Overview |
|
|
|
178 |
|
|
|
179 There is an option to tag various entities in Zabbix. Tags can be defined for: |
|
|
|
180 |
|
|
|
181 * templates |
|
|
|
182 * hosts |
|
|
|
183 * items |
|
|
|
184 * web scenarios |
|
|
|
185 * triggers |
|
|
|
186 * template items and triggers |
|
|
|
187 * host, item and trigger prototypes |
|
|
|
188 |
|
|
|
189 Tags have several uses, most notably, to mark events. If entities are tagged, the corresponding new events get marked accordingly:</description> |
|
|
|
190 </item> |
|
|
|
191 <item rdf:about="https://www.zabbix.com/documentation/current/manual/config/items/itemtypes/odbc_checks/unixodbc_mssql?rev=1636811125&do=diff"> |
|
|
|
192 <dc:format>text/html</dc:format> |
|
|
|
193 <dc:date>2021-11-13T13:45:25+0000</dc:date> |
|
|
|
194 <dc:creator>marinagen (marinagen@undisclosed.example.com)</dc:creator> |
|
|
|
195 <title>4 Recommended UnixODBC settings for MSSQL - fixing syntax</title> |
|
|
|
196 <link>https://www.zabbix.com/documentation/current/manual/config/items/itemtypes/odbc_checks/unixodbc_mssql?rev=1636811125&do=diff</link> |
|
|
|
197 <description>4 Recommended UnixODBC settings for MSSQL |
|
|
|
198 |
|
|
|
199 Installation |
|
|
|
200 |
|
|
|
201 * Red Hat Enterprise Linux/CentOS: |
|
|
|
202 # yum -y install freetds unixODBC |
|
|
|
203 * Debian/Ubuntu: |
|
|
|
204 |
|
|
|
205 Please refer to FreeTDS user guide to download necessary database driver for the corresponding platform. |
|
|
|
206 |
|
|
|
207 For some additional information please refer to:</description> |
|
|
|
208 </item> |
|
|
|
209 <item rdf:about="https://www.zabbix.com/documentation/current/manual/config/items/itemtypes/odbc_checks/unixodbc_postgresql?rev=1636810990&do=diff"> |
|
|
|
210 <dc:format>text/html</dc:format> |
|
|
|
211 <dc:date>2021-11-13T13:43:10+0000</dc:date> |
|
|
|
212 <dc:creator>marinagen (marinagen@undisclosed.example.com)</dc:creator> |
|
|
|
213 <title>2 Recommended UnixODBC settings for PostgreSQL - fixing syntax</title> |
|
|
|
214 <link>https://www.zabbix.com/documentation/current/manual/config/items/itemtypes/odbc_checks/unixodbc_postgresql?rev=1636810990&do=diff</link> |
|
|
|
215 <description>2 Recommended UnixODBC settings for PostgreSQL |
|
|
|
216 |
|
|
|
217 Installation |
|
|
|
218 |
|
|
|
219 * Red Hat Enterprise Linux/CentOS: |
|
|
|
220 # yum install postgresql-odbc |
|
|
|
221 |
|
|
|
222 * Debian/Ubuntu: |
|
|
|
223 |
|
|
|
224 Please refer to PostgreSQL documentation to download necessary database driver for the corresponding platform. |
|
|
|
225 |
|
|
|
226 For some additional information please refer to:</description> |
|
|
|
227 </item> |
|
|
|
228 <item rdf:about="https://www.zabbix.com/documentation/current/manual/config/items/itemtypes/log_items?rev=1636810398&do=diff"> |
|
|
|
229 <dc:format>text/html</dc:format> |
|
|
|
230 <dc:date>2021-11-13T13:33:18+0000</dc:date> |
|
|
|
231 <dc:creator>marinagen (marinagen@undisclosed.example.com)</dc:creator> |
|
|
|
232 <title>6 Log file monitoring - fixing syntax</title> |
|
|
|
233 <link>https://www.zabbix.com/documentation/current/manual/config/items/itemtypes/log_items?rev=1636810398&do=diff</link> |
|
|
|
234 <description>6 Log file monitoring |
|
|
|
235 |
|
|
|
236 Overview |
|
|
|
237 |
|
|
|
238 Zabbix can be used for centralized monitoring and analysis of log files with/without log rotation support. |
|
|
|
239 |
|
|
|
240 Notifications can be used to warn users when a log file contains certain strings or string patterns. |
|
|
|
241 |
|
|
|
242 To monitor a log file you must have:</description> |
|
|
|
243 </item> |
|
|
|
244 <item rdf:about="https://www.zabbix.com/documentation/current/manual/config/items/preprocessing/preprocessing_details?rev=1636810192&do=diff"> |
|
|
|
245 <dc:format>text/html</dc:format> |
|
|
|
246 <dc:date>2021-11-13T13:29:52+0000</dc:date> |
|
|
|
247 <dc:creator>marinagen (marinagen@undisclosed.example.com)</dc:creator> |
|
|
|
248 <title>2 Preprocessing details - fixing syntax</title> |
|
|
|
249 <link>https://www.zabbix.com/documentation/current/manual/config/items/preprocessing/preprocessing_details?rev=1636810192&do=diff</link> |
|
|
|
250 <description>2 Preprocessing details |
|
|
|
251 |
|
|
|
252 Overview |
|
|
|
253 |
|
|
|
254 This section provides item value preprocessing details. Item value preprocessing allows to define and execute transformation rules for the received item values. |
|
|
|
255 |
|
|
|
256 Preprocessing is managed by a preprocessing manager process, which was added in Zabbix 3.4, along with preprocessing workers that perform the preprocessing steps. All values (with or without preprocessing) from different data gatherers pass through the preprocessing manager before being added to the h…</description> |
|
|
|
257 </item> |
|
|
|
258 <item rdf:about="https://www.zabbix.com/documentation/current/manual/appendix/command_execution?rev=1636809999&do=diff"> |
|
|
|
259 <dc:format>text/html</dc:format> |
|
|
|
260 <dc:date>2021-11-13T13:26:39+0000</dc:date> |
|
|
|
261 <dc:creator>marinagen (marinagen@undisclosed.example.com)</dc:creator> |
|
|
|
262 <title>10 Command execution - [Exit code checking] fixing syntax</title> |
|
|
|
263 <link>https://www.zabbix.com/documentation/current/manual/appendix/command_execution?rev=1636809999&do=diff</link> |
|
|
|
264 <description>10 Command execution |
|
|
|
265 |
|
|
|
266 Zabbix uses common functionality for external checks, user parameters, system.run items, custom alert scripts, remote commands and user scripts. |
|
|
|
267 |
|
|
|
268 Execution steps |
|
|
|
269 |
|
|
|
270 The command/script is executed similarly on both Unix and Windows platforms:</description> |
|
|
|
271 </item> |
|
|
|
272 <item rdf:about="https://www.zabbix.com/documentation/current/manual/appliance?rev=1636809579&do=diff"> |
|
|
|
273 <dc:format>text/html</dc:format> |
|
|
|
274 <dc:date>2021-11-13T13:19:39+0000</dc:date> |
|
|
|
275 <dc:creator>marinagen (marinagen@undisclosed.example.com)</dc:creator> |
|
|
|
276 <title>6. Zabbix appliance - removing table</title> |
|
|
|
277 <link>https://www.zabbix.com/documentation/current/manual/appliance?rev=1636809579&do=diff</link> |
|
|
|
278 <description>6. Zabbix appliance |
|
|
|
279 |
|
|
|
280 Overview |
|
|
|
281 |
|
|
|
282 As an alternative to setting up manually or reusing an existing server for Zabbix, users may download a Zabbix appliance or a Zabbix appliance installation CD image. |
|
|
|
283 |
|
|
|
284 Zabbix appliance and installation CD versions are based on CentOS 8 (x86_64).</description> |
|
|
|
285 </item> |
|
|
|
286 <item rdf:about="https://www.zabbix.com/documentation/current/manual/appendix?rev=1636809224&do=diff"> |
|
|
|
287 <dc:format>text/html</dc:format> |
|
|
|
288 <dc:date>2021-11-13T13:13:44+0000</dc:date> |
|
|
|
289 <dc:creator>marinagen (marinagen@undisclosed.example.com)</dc:creator> |
|
|
|
290 <title>21. Appendixes - adding section number</title> |
|
|
|
291 <link>https://www.zabbix.com/documentation/current/manual/appendix?rev=1636809224&do=diff</link> |
|
|
|
292 <description>21. Appendixes |
|
|
|
293 |
|
|
|
294 Please use the sidebar to access content in the Appendixes section.</description> |
|
|
|
295 </item> |
|
|
|
296 <item rdf:about="https://www.zabbix.com/documentation/current/manual/installation/requirements/best_practices?rev=1636807071&do=diff"> |
|
|
|
297 <dc:format>text/html</dc:format> |
|
|
|
298 <dc:date>2021-11-13T12:37:51+0000</dc:date> |
|
|
|
299 <dc:creator>marinagen (marinagen@undisclosed.example.com)</dc:creator> |
|
|
|
300 <title>Best practices for secure Zabbix setup - [ZBX-20185] Removing CSP policy until [ZBXNEXT-3692] </title> |
|
|
|
301 <link>https://www.zabbix.com/documentation/current/manual/installation/requirements/best_practices?rev=1636807071&do=diff</link> |
|
|
|
302 <description>Best practices for secure Zabbix setup |
|
|
|
303 |
|
|
|
304 Overview |
|
|
|
305 |
|
|
|
306 This section contains best practices that should be observed in order to set up Zabbix in a secure way. |
|
|
|
307 |
|
|
|
308 The practices contained here are not required for the functioning of Zabbix. They are recommended for better security of the system.</description> |
|
|
|
309 </item> |
|
|
|
310 <item rdf:about="https://www.zabbix.com/documentation/current/manual/appendix/items/proc_mem_notes?rev=1636711903&do=diff"> |
|
|
|
311 <dc:format>text/html</dc:format> |
|
|
|
312 <dc:date>2021-11-12T10:11:43+0000</dc:date> |
|
|
|
313 <dc:creator>marinagen (marinagen@undisclosed.example.com)</dc:creator> |
|
|
|
314 <title>9 Notes on memtype parameter in proc.mem items - changing footnotes format for conversion</title> |
|
|
|
315 <link>https://www.zabbix.com/documentation/current/manual/appendix/items/proc_mem_notes?rev=1636711903&do=diff</link> |
|
|
|
316 <description>9 Notes on memtype parameter in proc.mem items |
|
|
|
317 |
|
|
|
318 Overview |
|
|
|
319 |
|
|
|
320 The memtype parameter is supported on Linux, AIX, FreeBSD, and Solaris platforms. |
|
|
|
321 |
|
|
|
322 Three common values of 'memtype' are supported on all of these platforms: pmem, rss and vsize. Additionally, platform-specific 'memtype' values are supported on some platforms.</description> |
|
|
|
323 </item> |
|
|
|
324 <item rdf:about="https://www.zabbix.com/documentation/current/manual/appendix/faq?rev=1636709671&do=diff"> |
|
|
|
325 <dc:format>text/html</dc:format> |
|
|
|
326 <dc:date>2021-11-12T09:34:31+0000</dc:date> |
|
|
|
327 <dc:creator>marinagen (marinagen@undisclosed.example.com)</dc:creator> |
|
|
|
328 <title>1 Frequently asked questions / Troubleshooting - removing dead link</title> |
|
|
|
329 <link>https://www.zabbix.com/documentation/current/manual/appendix/faq?rev=1636709671&do=diff</link> |
|
|
|
330 <description>1 Frequently asked questions / Troubleshooting |
|
|
|
331 |
|
|
|
332 Frequently asked questions or FAQ. |
|
|
|
333 |
|
|
|
334 * Q: Can I flush/clear the queue (as depicted in Administration → Queue)? |
|
|
|
335 A: No. |
|
|
|
336 * Q: How do I migrate from one database to another? |
|
|
|
337 A: Dump data only (for MySQL, use flag -t or</description> |
|
|
|
338 </item> |
|
|
|
339 <item rdf:about="https://www.zabbix.com/documentation/current/manual/appendix/suffixes?rev=1636649048&do=diff"> |
|
|
|
340 <dc:format>text/html</dc:format> |
|
|
|
341 <dc:date>2021-11-11T16:44:08+0000</dc:date> |
|
|
|
342 <dc:creator>martins-v (martins-v@undisclosed.example.com)</dc:creator> |
|
|
|
343 <title>8 Unit symbols - time suffixes support only integer numbers (ZBX-20122)</title> |
|
|
|
344 <link>https://www.zabbix.com/documentation/current/manual/appendix/suffixes?rev=1636649048&do=diff</link> |
|
|
|
345 <description>8 Unit symbols |
|
|
|
346 |
|
|
|
347 Overview |
|
|
|
348 |
|
|
|
349 Having to use some large numbers, for example '86400' to represent the number of seconds in one day, is both difficult and error-prone. This is why you can use some appropriate unit symbols (or suffixes) to simplify Zabbix trigger expressions and item keys.</description> |
|
|
|
350 </item> |
|
|
|
351 </rdf:RDF> |
|