en-us	 ##### Web monitoring data  |Item key|<|<|<| |--|--|------|------| |Description|Return value|Parameters|Comments| |**web.page.get**\[host,<path>,<port>\]|<|<|<| |Get content of web page.|Web page source as text (including headers)|**host** - hostname or URL (as `scheme://host:port/path`, where only *host* is mandatory).<br>Allowed URL schemes: *http*, *https*^**[4](#footnotes)**^. Missing scheme will be treated as *http*. If URL is specified `path` and `port` must be empty. Specifying user name/password when connecting to servers that require authentication, for example: `http://user:password@www.example.com` is only possible with cURL support ^**[4](#footnotes)**^.<br>[Punycode](https://en.wikipedia.org/wiki/Punycode) is supported in hostnames.<br>**path** - path to HTML document (default is /)<br>**port** - port number (default is 80 for HTTP)|This item turns unsupported if the resource specified in `host` does not exist or is unavailable.<br><br>`host` can be hostname, domain name, IPv4 or IPv6 address. But for IPv6 address Zabbix agent must be compiled with IPv6 support enabled.<br><br>Example:<br>=> web.page.get\[www.example.com,index.php,80\]<br>=> web.page.get\[https://www.example.com\]<br>=> web.page.get\[https://blog.example.com/?s=zabbix\]<br>=> web.page.get\[localhost:80\]<br>=> web.page.get\["\[::1\]/server-status"\]| |**web.page.perf**\[host,<path>,<port>\]|<|<|<| |Loading time of full web page (in seconds).|Float|**host** - hostname or URL (as `scheme://host:port/path`, where only *host* is mandatory).<br>Allowed URL schemes: *http*, *https*^**[4](#footnotes)**^. Missing scheme will be treated as *http*. If URL is specified `path` and `port` must be empty. Specifying user name/password when connecting to servers that require authentication, for example: `http://user:password@www.example.com` is only possible with cURL support ^**[4](#footnotes)**^.<br>[Punycode](https://en.wikipedia.org/wiki/Punycode) is supported in hostnames.<br>**path** - path to HTML document (default is /)<br>**port** - port number (default is 80 for HTTP)|This item turns unsupported if the resource specified in `host` does not exist or is unavailable.<br><br>`host` can be hostname, domain name, IPv4 or IPv6 address. But for IPv6 address Zabbix agent must be compiled with IPv6 support enabled.<br><br>Example:<br>=> web.page.perf\[www.example.com,index.php,80\]<br>=> web.page.perf\[https://www.example.com\]| |**web.page.regexp**\[host,<path>,<port>,regexp,<length>,<output>\]|<|<|<| |Find string on a web page.|The matched string, or as specified by the optional `output` parameter|**host** - hostname or URL (as `scheme://host:port/path`, where only *host* is mandatory).<br>Allowed URL schemes: *http*, *https*^**[4](#footnotes)**^. Missing scheme will be treated as *http*. If URL is specified `path` and `port` must be empty. Specifying user name/password when connecting to servers that require authentication, for example: `http://user:password@www.example.com` is only possible with cURL support ^**[4](#footnotes)**^.<br>[Punycode](https://en.wikipedia.org/wiki/Punycode) is supported in hostnames.<br>**path** - path to HTML document (default is /)<br>**port** - port number (default is 80 for HTTP)<br>**regexp** - regular [expression](/manual/regular_expressions#overview) describing the required pattern<br>**length** - maximum number of characters to return<br>**output** - an optional output formatting template. The **\\0** escape sequence is replaced with the matched part of text (from the first character where match begins until the character where match ends) while an **\\N** (where N=1...9) escape sequence is replaced with Nth matched group (or an empty string if the N exceeds the number of captured groups).|This item turns unsupported if the resource specified in `host` does not exist or is unavailable.<br><br>`host` can be hostname, domain name, IPv4 or IPv6 address. But for IPv6 address Zabbix agent must be compiled with IPv6 support enabled.<br><br>Content extraction using the `output` parameter takes place on the agent.<br><br>The `output` parameter is supported from version 2.2.<br><br>Example:<br>=> web.page.regexp\[www.example.com,index.php,80,OK,2\]<br>=> web.page.regexp\[https://www.example.com,,,OK,2\]|
fa	 ##### داده های نظارت بر وب  |کلید مورد|<|<|<| |--|--|------|------| |توضیحات|مقدار بازگشتی|پارامترها|نظرات| |**web.page.get**\[host,<path>,<port>\]|<|<|<| |محتوای صفحه وب را دریافت کنید.|منبع صفحه وب به عنوان متن (شامل سرصفحه)|**میزبان** - نام میزبان یا URL (به عنوان `scheme://host:port/path`، که در آن فقط *میزبان* اجباری است). <br>طرح‌های URL مجاز: *http*، *https*^**[4](#footnotes)**^. طرح گم شده به عنوان *http* در نظر گرفته می شود. اگر URL مشخص شده باشد، «مسیر» و «پورت» باید خالی باشد. تعیین نام کاربری/رمز عبور هنگام اتصال به سرورهایی که نیاز به احراز هویت دارند، برای مثال: «http://user:password@www.example.com» فقط با پشتیبانی از cURL امکان پذیر است ^**[4](#footnotes)**^ .<br>[Punycode](https://en.wikipedia.org/wiki/Punycode) در نام‌های میزبان پشتیبانی می‌شود.<br>**مسیر** - مسیر سند HTML (پیش‌فرض /) است<br>** پورت** - شماره پورت (پیش‌فرض برای HTTP 80 است)|اگر منبع مشخص‌شده در «میزبان» وجود نداشته باشد یا در دسترس نباشد، این مورد پشتیبانی نمی‌شود.<br><br>«میزبان» می‌تواند نام میزبان، نام دامنه، IPv4 باشد. یا آدرس IPv6 اما برای آدرس IPv6 عامل Zabbix باید با پشتیبانی از IPv6 فعال باشد.<br><br>مثال:<br>=> web.page.get\[www.example.com,index.php,80\]<br> => web.page.get\[https://www.example.com\]<br>=> web.page.get\[https://blog.example.com/?s=zabbix\]<br >=> web.page.get\[localhost:80\]<br>=> web.page.get\["\[::1\]/server-status"\]| |**web.page.perf**\[host,<path>,<port>\]|<|<|<| |زمان بارگیری صفحه وب کامل (در ثانیه).|Float|**host** - نام میزبان یا URL (به عنوان 'scheme://host:port/path'، که در آن فقط *host* اجباری است).<br> طرح‌های URL مجاز: *http*، *https*^**[4](#footnotes)**^. طرح گم شده به عنوان *http* در نظر گرفته می شود. اگر URL مشخص شده باشد، «مسیر» و «پورت» باید خالی باشد. تعیین نام کاربری/رمز عبور هنگام اتصال به سرورهایی که نیاز به احراز هویت دارند، برای مثال: «http://user:password@www.example.com» فقط با پشتیبانی از cURL امکان پذیر است ^**[4](#footnotes)**^ .<br>[Punycode](https://en.wikipedia.org/wiki/Punycode) در نام‌های میزبان پشتیبانی می‌شود.<br>**مسیر** - مسیر سند HTML (پیش‌فرض /) است<br>** پورت** - شماره پورت (پیش‌فرض برای HTTP 80 است)|اگر منبع مشخص‌شده در «میزبان» وجود نداشته باشد یا در دسترس نباشد، این مورد پشتیبانی نمی‌شود.<br><br>«میزبان» می‌تواند نام میزبان، نام دامنه، IPv4 باشد. یا آدرس IPv6 اما برای آدرس IPv6 عامل Zabbix باید با پشتیبانی از IPv6 فعال باشد.<br><br>مثال:<br>=> web.page.perf\[www.example.com,index.php,80\]<br> => web.page.perf\[https://www.example.com\]| |**web.page.regexp**\[host,<path>,<port>,regexp,<length>,<output>\]|<|<|<| |رشته را در یک صفحه وب بیابید.|رشته منطبق، یا همانطور که توسط پارامتر اختیاری «output» مشخص شده است|**host** - نام میزبان یا URL (به عنوان `scheme://host:port/path`، که در آن فقط * میزبان* اجباری است.<br>طرح های URL مجاز: *http*، *https*^**[4](#footnotes)**^. طرح گم شده به عنوان *http* در نظر گرفته می شود. اگر URL مشخص شده باشد، «مسیر» و «پورت» باید خالی باشد. تعیین نام کاربری/رمز عبور هنگام اتصال به سرورهایی که نیاز به احراز هویت دارند، برای مثال: «http://user:password@www.example.com» فقط با پشتیبانی از cURL امکان پذیر است ^**[4](#footnotes)**^ .<br>[Punycode](https://en.wikipedia.org/wiki/Punycode) در نام‌های میزبان پشتیبانی می‌شود.<br>**مسیر** - مسیر سند HTML (پیش‌فرض /) است<br>** پورت** - شماره پورت (پیش‌فرض برای HTTP 80 است)<br>**regexp** - عادی [عبارت](/manual/regular_expressions#overview) که الگوی مورد نیاز را توصیف می‌کند<br>**طول** - حداکثر تعداد کاراکترهایی برای بازگشت<br>**خروجی** - یک قالب قالب بندی خروجی اختیاری. دنباله **\\0** با قسمت منطبق متن جایگزین می شود (از اولین کاراکتر که در آن مطابقت شروع می شود تا کاراکتری که مطابقت به پایان می رسد) در حالی که یک **\\N** (که در آن N=1... 9) دنباله فرار با Nامین گروه منطبق جایگزین می شود (یا یک رشته خالی اگر N از تعداد گروه های گرفته شده بیشتر باشد).|اگر منبع مشخص شده در "میزبان" وجود نداشته باشد یا در دسترس نباشد، این مورد پشتیبانی نمی شود.<br><br><br><br><br> br>`host` می تواند نام میزبان، نام دامنه، آدرس IPv4 یا IPv6 باشد. اما برای آدرس IPv6 عامل Zabbix باید با پشتیبانی از IPv6 فعال باشد.<br><br>استخراج محتوا با استفاده از پارامتر "output" در عامل انجام می شود.<br><br>پارامتر "output" از نسخه 2.2 پشتیبانی می شود. .<br><br>مثال:<br>=> web.page.regexp\[www.example.com,index.php,80,OK,2\]<br>=> web.page.regexp\[ https://www.example.com,,,OK,2\]|

en-us	#### Web scenario  In a [web scenario](/manual/web_monitoring) configuration, user macros can be used in the following fields:  |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |-|------------------------------|----------| |Name|<|yes| |Update interval|<|no| |Agent|<|yes| |HTTP proxy|<|yes| |Variables (values only)|<|yes| |Headers (names and values)|<|yes| |*Steps*|<|<| | |Name|yes| |^|URL^[3](supported_by_location_user#footnotes)^|yes| |^|Variables (values only)|yes| |^|Headers (names and values)|yes| |^|Timeout|no| |^|Required string|yes| |^|Required status codes|no| |*Authentication*|<|<| | |User|yes| |^|Password|yes| |^|SSL certificate|yes| |^|SSL key file|yes| |^|SSL key password|yes| |*Tags*^[2](supported_by_location_user#footnotes)^|<|<| | |Tag names|yes| |^|Tag values|yes|
fa	#### سناریوی وب  در پیکربندی [سناریو وب](/manual/web_monitoring)، ماکروهای کاربر می تواند در زمینه های زیر استفاده شود:  |موقعیت|<|چند ماکرو/میکس با متن^[1](پشتیبانی_شده توسط_location_user#footnotes)^| |-|-----------------------------|----------| |نام|<|بله| |فاصله به روز رسانی|<|نه| |نماینده|<|بله| |پراکسی HTTP|<|بله| |متغیرها (فقط مقادیر)|<|بله| |سرصفحه ها (نام ها و مقادیر)|<|بله| |*مراحل*|<|<| | |نام|بله| |^|URL^[3](supported_location_user#footnotes)^|بله| |^|متغیرها (فقط مقادیر)|بله| |^|سرصفحه ها (نام ها و مقادیر)|بله| |^|تایم پایان|نه| |^|رشته مورد نیاز|بله| |^|کدهای وضعیت مورد نیاز|خیر| |*احراز هویت*|<|<| | |کاربر|بله| |^|رمز عبور|بله| |^|گواهی SSL|بله| |^|فایل کلید SSL|بله| |^|رمز عبور کلید SSL|بله| |*برچسب ها*^[2](پشتیبانی_شده توسط_location_user#footnotes)^|<|<| | |اسامی برچسب|بله| |^|مقادیر برچسب|بله|

en-us	# > Web scenario object  The following objects are directly related to the `webcheck` API.
fa	# > آبجکت وب سناریو  The following objects are directly related to the `webcheck` API.

en-us	### Web scenario tag  The web scenario tag object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**tag**<br>(required)|string|Web scenario tag name.| |value|string|Web scenario tag value.|
fa	### تگ وب سناریو   The web scenario tag object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**tag**<br>(required)|string|Web scenario tag name.| |value|string|Web scenario tag value.|

en-us	# Web scenario  This class is designed to work with web scenarios.  Object references:\  -   [Web scenario](/manual/api/reference/httptest/object#web_scenario) -   [Scenario step](/manual/api/reference/httptest/object#scenario_step)  Available methods:\  -   [httptest.create](/manual/api/reference/httptest/create) - creating     new web scenarios -   [httptest.delete](/manual/api/reference/httptest/delete) - deleting     web scenarios -   [httptest.get](/manual/api/reference/httptest/get) - retrieving web     scenarios -   [httptest.update](/manual/api/reference/httptest/update) - updating     web scenarios
fa	# وب سناریو   This class is designed to work with web scenarios.  Object references:\  -   [Web scenario](/manual/api/reference/httptest/object#web_scenario) -   [Scenario step](/manual/api/reference/httptest/object#scenario_step)  Available methods:\  -   [httptest.create](/manual/api/reference/httptest/create) - creating     new web scenarios -   [httptest.delete](/manual/api/reference/httptest/delete) - deleting     web scenarios -   [httptest.get](/manual/api/reference/httptest/get) - retrieving web     scenarios -   [httptest.update](/manual/api/reference/httptest/update) - updating     web scenarios

en-us	##### What can be exported/imported  Objects that can be exported/imported are:  -   [host groups](/manual/xml_export_import/groups) (*through Zabbix API     only*) -   [templates](/manual/xml_export_import/templates) -   [hosts](/manual/xml_export_import/hosts) -   [network maps](/manual/xml_export_import/maps) -   [media types](/manual/xml_export_import/media) -   images
fa	##### چه چیزی را می توان صادر/وارد کرد  اشیایی که می توانند صادر یا وارد شوند عبارتند از:  - [گروه‌های میزبان](/manual/xml_export_import/groups) (*از طریق Zabbix API     فقط*) - [قالب‌ها](/دستی/xml_export_import/templates) - [hosts](/manual/xml_export_import/hosts) - [نقشه های شبکه](/manual/xml_export_import/maps) - [انواع رسانه] (/دستی/xml_export_import/media) -   تصاویر

en-us	#### Whitespace  Whitespace (space, tab characters) can be freely used in bracket notation segments and expressions, for example, `$[ 'a' ][ 0 ][ ?( $.b == 'c' ) ][ : -1 ].first( )`.
fa	#### فضای سفید  فضای خالی (فضا، کاراکترهای برگه) را می توان آزادانه در براکت استفاده کرد به عنوان مثال، بخش ها و عبارات نمادگذاری، `$[ 'a' ][ 0 ][ ?( $.b == 'c' ) ][ : -1 ].first( )».

en-us	# Zabbix API changes in 6.0
fa	# تغییرات Zabbix API در نسخه 6.0 

en-us	#### Zabbix configuration
fa	#### پیکربندی Zabbix

en-us	#### - Zabbix configuration  Zabbix appliance setup has the following passwords and configuration changes:
fa	#### - پیکربندی Zabbix  راه اندازی دستگاه Zabbix دارای رمز عبور و پیکربندی زیر است تغییرات:

en-us	# Zabbix documentation 6.0  These pages contain official Zabbix documentation.  Use the sidebar navigation to browse documentation pages.  To be able to watch pages, log in with your [Zabbix forums](http://www.zabbix.com/forum/) username and password.
fa	# مستندات Zabbix 6.0  این صفحات حاوی اسناد رسمی Zabbix هستند.  از پیمایش نوار کناری برای مرور صفحات اسناد استفاده کنید.  برای اینکه بتوانید صفحات را تماشا کنید، با [Zabbix] خود وارد شوید forums](http://www.zabbix.com/forum/) نام کاربری و رمز عبور.

en-us	##### Zabbix frontend  A *Frontend URL* parameter should be set to enable communication between Zabbix frontend and Zabbix web service:  -   Proceed to the *Administration → General → Other parameters* frontend menu section -   Specify the full URL of the Zabbix web interface in the *Frontend URL* parameter.  ![frontend\_url.png](../../../../assets/en/manual/appendix/install/frontend_url.png)  ::: notetip  Once the setup procedure is completed, you may want to configure and send a [test report](/manual/config/reports#testing) to make sure everything works correctly.  :::
fa	##### فرانت اند Zabbix  یک پارامتر *Frontend URL* باید تنظیم شود تا ارتباط بین زاببیکس و سرویس وب Zabbix فعال شود:  - به بخش منوی جلویی *Administration → General → Other Parameters* بروید - URL کامل رابط وب Zabbix را در پارامتر *Frontend URL* مشخص کنید.  ![frontend\_url.png](../../../../assets/en/manual/appendix/install/frontend_url.png)  ::: یادداشت  پس از تکمیل مراحل نصب، ممکن است بخواهید یک [گزارش آزمایش] (/manual/config/reports#testing) پیکربندی و ارسال کنید تا مطمئن شوید همه چیز به درستی کار می کند. :::

en-us	# Zabbix manpages  These are Zabbix manpages for Zabbix processes.
fa	# صفحات راهنمای زبیکس صفحات راهنمای جاری مربوط به فرایند های زبیکس می باشند.

en-us	# Zabbix Manual  Welcome to the user manual for Zabbix software. These pages are created to help users successfully manage their monitoring tasks with Zabbix, from the simple to the more complex ones.
fa	# دفترچه راهنمای Zabbix  به راهنمای کاربر نرم افزار Zabbix خوش آمدید. این صفحات ایجاد شده اند تا به کاربران کمک کند وظایف مانیتورینگ خود را با Zabbix، از ساده تا پیچیده، با موفقیت مدیریت کنند.

en-us	 ##### Zabbix metrics  |Item key|<|<|<| |--|--|------|------| |Description|Return value|Parameters|Comments| |**agent.hostmetadata**|<|<|<| |Agent host metadata.|String||Returns the value of HostMetadata or HostMetadataItem parameters, or empty string if none are defined.<br><br>Supported since Zabbix 6.0.| |**agent.hostname**|<|<|<| |Agent host name.|String| |Returns:<br>As passive check - the name of the first host listed in the Hostname parameter of the agent configuration file;<br>As active check - the name of the current hostname.| |**agent.ping**|<|<|<| |Agent availability check.|Nothing - unavailable<br><br>1 - available| |Use the **nodata()** trigger function to check for host unavailability.| |**agent.variant**|<|<|<| |Variant of Zabbix agent (Zabbix agent or Zabbix agent 2).|Integer| |Example of returned value:<br>1 - Zabbix agent<br>2 - Zabbix agent 2| |**agent.version**|<|<|<| |Version of Zabbix agent.|String| |Example of returned value:<br>6.0.3| |**zabbix.stats**\[<ip>,<port>\]|<|<|<| |Return a set of Zabbix server or proxy internal metrics remotely.|JSON object|**ip** - IP/DNS/network mask list of servers/proxies to be remotely queried (default is 127.0.0.1)<br>**port** - port of server/proxy to be remotely queried (default is 10051)|Note that the stats request will only be accepted from the addresses listed in the 'StatsAllowedIP' [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) parameter on the target instance.<br><br>A selected set of internal metrics is returned by this item. For details, see [Remote monitoring of Zabbix stats](/manual/appendix/items/remote_stats#exposed_metrics).| |**zabbix.stats**\[<ip>,<port>,queue,<from>,<to>\]|<|<|<| |Return number of monitored items in the queue which are delayed on Zabbix server or proxy remotely.|JSON object|**ip** - IP/DNS/network mask list of servers/proxies to be remotely queried (default is 127.0.0.1)<br>**port** - port of server/proxy to be remotely queried (default is 10051)<br>**queue** - constant (to be used as is)<br>**from** - delayed by at least (default is 6 seconds)<br>**to** - delayed by at most (default is infinity)|Note that the stats request will only be accepted from the addresses listed in the 'StatsAllowedIP' [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) parameter on the target instance.|
fa	 ##### معیارهای Zabbix  |کلید مورد|<|<|<| |--|--|------|------| |توضیحات|مقدار بازگشتی|پارامترها|نظرات| |**agent.hostmetadata**|<|<|<| |فراداده میزبان عامل.|رشته||مقدار پارامترهای HostMetadata یا HostMetadataItem یا اگر هیچ کدام تعریف نشده باشد، رشته خالی را برمی گرداند.<br><br>پشتیبانی شده از Zabbix 6.0.| |**agent.hostname**|<|<|<| |نام میزبان عامل.|رشته| |برمی‌گرداند:<br>به‌عنوان بررسی غیرفعال - نام اولین میزبان فهرست شده در پارامتر Hostname فایل پیکربندی عامل؛<br>به‌عنوان بررسی فعال - نام میزبان فعلی.| |**عامل.پینگ**|<|<|<| |بررسی در دسترس بودن نماینده.|هیچ چیز - در دسترس نیست<br><br>1 - موجود| |برای بررسی در دسترس نبودن هاست، از تابع تریگر **nodata()** استفاده کنید.| |**agent.variant**|<|<|<| |نوع عامل Zabbix (عامل Zabbix یا عامل Zabbix 2).|عدد صحیح| |نمونه ای از مقدار برگشتی:<br>1 - عامل Zabbix<br>2 - عامل Zabbix 2| |**agent.version**|<|<|<| |نسخه عامل Zabbix.|رشته| |نمونه مقدار برگشتی:<br>6.0.3| |**zabbix.stats**\[<ip>,<port>\]|<|<|<| | مجموعه‌ای از معیارهای داخلی سرور Zabbix یا پراکسی را از راه دور برگردانید.|شیء JSON|**ip** - فهرست IP/DNS/ماسک شبکه از سرورها/پراکسی‌هایی که باید از راه دور درخواست شوند (پیش‌فرض 127.0.0.1 است)<br>** پورت** - پورت سرور/پراکسی که باید از راه دور درخواست شود (پیش‌فرض 10051 است)|توجه داشته باشید که درخواست آمار فقط از آدرس‌های فهرست شده در 'StatsAllowedIP' [سرور] (/manual/appendix/config/zabbix_server) پذیرفته می‌شود. پارامتر /[proxy](/manual/appendix/config/zabbix_proxy) در نمونه مورد نظر.<br><br>مجموعه‌ای از معیارهای داخلی انتخاب شده توسط این مورد برگردانده می‌شود. برای جزئیات، [نظارت از راه دور آمار Zabbix](/manual/appendix/items/remote_stats#exposed_metrics) را ببینید.| |**zabbix.stats**\[<ip>,<port>,queue,<from>,<to>\]|<|<|<| |تعداد موارد نظارت شده در صف را که روی سرور Zabbix یا پراکسی از راه دور تأخیر دارند، برگردانید.|شیء JSON|**ip** - فهرست IP/DNS/ماسک شبکه از سرورها/پراکسی هایی که باید از راه دور درخواست شوند (پیش فرض 127.0.0.1 است. )<br>**پورت** - پورت سرور/پراکسی که باید از راه دور جستجو شود (پیش‌فرض 10051 است)<br>**صف** - ثابت (برای استفاده همانطور که هست)<br>**از** - با حداقل تاخیر (پیش‌فرض 6 ثانیه است)<br>**تا** - حداکثر با تأخیر (پیش‌فرض بی‌نهایت است)|توجه داشته باشید که درخواست آمار فقط از آدرس‌های فهرست شده در "StatsAllowedIP" [سرور] پذیرفته می‌شود. (/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) پارامتر روی نمونه مورد نظر.|

en-us	##### Zabbix server and frontend  Zabbix server configuration file draft with parameters to be updated:      ### Option: HistoryStorageURL     # History storage HTTP[S] URL.     #     # Mandatory: no     # Default:     # HistoryStorageURL=      ### Option: HistoryStorageTypes     # Comma separated list of value types to be sent to the history storage.     #     # Mandatory: no     # Default:     # HistoryStorageTypes=uint,dbl,str,log,text  Example parameter values to fill the Zabbix server configuration file with:      HistoryStorageURL=http://test.elasticsearch.lan:9200     HistoryStorageTypes=str,log,text  This configuration forces Zabbix Server to store history values of numeric types in the corresponding database and textual history data in Elasticsearch.  Elasticsearch supports the following item types:      uint,dbl,str,log,text  Supported item type explanation:  |   |   |   | |---|---|---| |**Item value type**|**Database table**|**Elasticsearch type**| |Numeric (unsigned)|history\_uint|uint| |Numeric (float)|history|dbl| |Character|history\_str|str| |Log|history\_log|log| |Text|history\_text|text|  Zabbix frontend configuration file (`conf/zabbix.conf.php`) draft with parameters to be updated:      // Elasticsearch url (can be string if same url is used for all types).     $HISTORY['url']   = [           'uint' => 'http://localhost:9200',           'text' => 'http://localhost:9200'     ];     // Value types stored in Elasticsearch.     $HISTORY['types'] = ['uint', 'text'];  Example parameter values to fill the Zabbix frontend configuration file with:      $HISTORY['url']   = 'http://test.elasticsearch.lan:9200';     $HISTORY['types'] = ['str', 'text', 'log'];  This configuration forces to store `Text`, `Character` and `Log` history values in Elasticsearch.  It is also required to make $HISTORY global in `conf/zabbix.conf.php` to ensure everything is working properly (see `conf/zabbix.conf.php.example` for how to do it):      // Zabbix GUI configuration file.     global $DB, $HISTORY;
fa	##### سرور Zabbix و frontend  پیش نویس فایل پیکربندی سرور Zabbix با پارامترهایی که باید به روز شوند:      ### گزینه: HistoryStorageURL     # نشانی وب HTTP[S] ذخیره سازی سابقه.     #     # اجباری: خیر     # پیش فرض:     # HistoryStorageURL=     ### گزینه: HistoryStorageTypes     # فهرست انواع مقادیر جدا شده با کاما برای ارسال به ذخیره‌سازی تاریخچه.     #     # اجباری: خیر     # پیش فرض:     # HistoryStorageTypes=uint,dbl,str,log,text  مقادیر پارامتر نمونه برای پر کردن فایل پیکربندی سرور Zabbix با:      HistoryStorageURL=http://test.elasticsearch.lan:9200     HistoryStorageTypes=str,log,text  این پیکربندی سرور Zabbix را مجبور می‌کند تا مقادیر تاریخچه را ذخیره کند انواع عددی در پایگاه داده مربوطه و داده های تاریخ متنی در Elasticsearch.  Elasticsearch انواع موارد زیر را پشتیبانی می کند:      uint,dbl,str,log,text  توضیح نوع مورد پشتیبانی شده:  | | | | |---|---|---| |**نوع مقدار مورد**|**جدول پایگاه**|**نوع Elasticsearch**| |عددی (بدون امضا)|history\_uint|unint| |عددی (شناور)|تاریخچه|dbl| |شخصیت|تاریخ\_str|خیابان| |گزارش|تاریخچه\_log|log| |متن|تاریخ\_متن|متن|  پیش نویس فایل پیکربندی ظاهری Zabbix (`conf/zabbix.conf.php`) با پارامترهایی که باید به روز شوند:      // url Elasticsearch (اگر از همان URL برای همه انواع استفاده شود، می تواند رشته ای باشد).     $HISTORY['url'] = [           'uint' => 'http://localhost:9200'،           'text' => 'http://localhost:9200'     ]؛     // انواع مقادیر ذخیره شده در Elasticsearch.     $HISTORY['types'] = ['unint', 'text'];  مقادیر پارامتر نمونه برای پر کردن فایل پیکربندی frontend Zabbix با:      $HISTORY['url'] = 'http://test.elasticsearch.lan:9200';     $HISTORY['types'] = ['str', 'text', 'log'];  این پیکربندی مجبور به ذخیره تاریخچه «متن»، «شخصیت» و «Log» می‌شود مقادیر در Elasticsearch  همچنین لازم است $HISTORY در «conf/zabbix.conf.php» جهانی شود. اطمینان حاصل کنید که همه چیز به درستی کار می کند (نگاه کنید به «conf/zabbix.conf.php.example» برای نحوه انجام آن):      // فایل پیکربندی رابط کاربری گرافیکی Zabbix.     جهانی $DB، $HISTORY;

en-us	#### Zabbix server/proxy configuration  Secure connections to the database can be configured with the respective parameters in the Zabbix [server](/manual/appendix/config/zabbix_server) and/or [proxy](/manual/appendix/config/zabbix_proxy) configuration file.  |Configuration|Result| |--|--| |None|Connection to the database without encryption.| |1\. Set DBTLSConnect=required|Server/proxy make a TLS connection to the database. An unencrypted connection is not allowed.| |1\. Set DBTLSConnect=verify\_ca<br>2. Set DBTLSCAFile - specify the TLS certificate authority file|Server/proxy make a TLS connection to the database after verifying the database certificate.| |1\. Set DBTLSConnect=verify\_full<br>2. Set DBTLSCAFile - specify TLS certificate authority file|Server/proxy make a TLS connection to the database after verifying the database certificate and the database host identity.| |1\. Set DBTLSCAFile - specify TLS certificate authority file<br>2. Set DBTLSCertFile - specify the client public key certificate file<br>3. Set DBTLSKeyFile - specify the client private key file|Server/proxy provide a client certificate while connecting to the database.| |1\. Set DBTLSCipher - the list of encryption ciphers that the client permits for connections using TLS protocols up to TLS 1.2<br><br>or DBTLSCipher13 - the list of encryption ciphers that the client permits for connections using TLS 1.3 protocol|(MySQL) TLS connection is made using a cipher from the provided list.<br>(PostgreSQL) Setting this option will be considered as an error.|
fa	#### پیکربندی سرور/پراکسی Zabbix  اتصالات امن به پایگاه داده را می توان با مربوطه پیکربندی کرد پارامترهای موجود در Zabbix [سرور] (/manual/appendix/config/zabbix_server) و/یا فایل پیکربندی [proxy](/manual/appendix/config/zabbix_proxy).  |پیکربندی|نتیجه| |--|--| |هیچ|اتصال به پایگاه داده بدون رمزگذاری.| |1\. DBTLSConnect=required|سرور/پراکسی یک اتصال TLS به پایگاه داده را تنظیم کنید. اتصال رمزگذاری نشده مجاز نیست.| |1\. DBTLSConnect=verify\_ca<br>2 را تنظیم کنید. تنظیم DBTLSCAFile - فایل مرجع گواهی TLS را مشخص کنید|سرور/پراکسی پس از تأیید گواهی پایگاه داده، یک اتصال TLS به پایگاه داده ایجاد می کند.| |1\. DBTLSConnect=verify\_full<br>2 را تنظیم کنید. DBTLSCAFile را تنظیم کنید - فایل مرجع گواهی TLS را مشخص کنید|سرور/پراکسی پس از تأیید گواهی پایگاه داده و هویت میزبان پایگاه داده، یک اتصال TLS به پایگاه داده ایجاد می کند.| |1\. DBTLSCAFile را تنظیم کنید - فایل مرجع گواهی TLS را مشخص کنید<br>2. تنظیم DBTLSCertFile - فایل گواهی کلید عمومی مشتری را مشخص کنید<br>3. تنظیم DBTLSKeyFile - فایل کلید خصوصی کلاینت را مشخص کنید|سرور/پراکسی هنگام اتصال به پایگاه داده گواهی مشتری ارائه می دهد.| |1\. تنظیم DBTLSCipher - لیستی از رمزهای رمزگذاری که مشتری برای اتصالات با استفاده از پروتکل های TLS تا TLS 1.2<br><br><br>یا DBTLSCipher13 اجازه می دهد - لیستی از رمزهای رمزگذاری که سرویس گیرنده برای اتصالات با استفاده از پروتکل TLS 1.3 مجوز می دهد|(MySQL) TLS اتصال با استفاده از یک رمز از لیست ارائه شده انجام می شود.<br>(PostgreSQL) تنظیم این گزینه به عنوان یک خطا در نظر گرفته می شود.|

en-us	##### Zabbix server  The following parameters in Zabbix server configuration file need to be updated: *WebServiceURL* and *StartReportWriters*.  **WebServiceURL**  This parameter is required to enable communication with the web service. The URL should be in the format `<host:port>/report`.  -   By default, the web service listens on port 10053. A different port can be specified in the web service [configuration file](/manual/appendix/config/zabbix_web_service). -   Specifying the `/report` path is mandatory (the path is hardcoded and cannot be changed).  Example:      WebServiceURL=http://localhost:10053/report  **StartReportWriters**  This parameter determines how many report writer processes should be started. If it is not set or equals 0, report generation is disabled. Based on the number and frequency of reports required, it is possible to enable from 1 to 100 report writer processes.  Example:      StartReportWriters=3
fa	##### سرور Zabbix  پارامترهای زیر در فایل پیکربندی سرور Zabbix باید به روز شوند: *WebServiceURL* و *StartReportWriters*.  **WebServiceURL**  این پارامتر برای فعال کردن ارتباط با وب سرویس مورد نیاز است. URL باید در قالب «<host:port>/report» باشد.  - به طور پیش فرض، وب سرویس در پورت 10053 گوش می دهد. یک پورت متفاوت را می توان در وب سرویس [فایل پیکربندی] (/manual/appendix/config/zabbix_web_service) مشخص کرد. - تعیین مسیر `/گزارش` الزامی است (مسیر هاردکد است و قابل تغییر نیست).  مثال:      WebServiceURL=http://localhost:10053/report  **StartReportWriters**  این پارامتر تعیین می کند که چند فرآیند گزارش نویس باید شروع شود. اگر تنظیم نشده باشد یا برابر با 0 باشد، تولید گزارش غیرفعال است. بر اساس تعداد و فراوانی گزارش‌های مورد نیاز، می‌توان از 1 تا 100 فرآیند گزارش‌نویس را فعال کرد.  مثال:      StartReportWriters=3

en-us	###     
fa	###    

en-us	# 11 Time zones
fa	# 11 منطقه زمانی

en-us	# 14. Configuration export/import
fa	# 14. وارد کردن یا خروجی گرفتن از تنظیمات  

en-us	# 1 Menu
fa	# 1 منو

en-us	# 4 Zabbix agent 2 (UNIX)
fa	# Zabbix Agent 2 (یونیکس)

en-us	# 9. Web monitoring
fa	مانیتورینگ وب 

en-us	# action.create
fa	# ساخت اکشن 

en-us	# action.delete
fa	#پاک کردن اکشن 

en-us	# action.get
fa	# دریافت اکشن

en-us	# > Action object  The following objects are directly related to the `action` API.
fa	# > آبجکت اکشن   اشیاء زیر مستقیماً با API «action» مرتبط هستند.

en-us	# Action  This class is designed to work with actions.  Object references:\  -   [Action](/manual/api/reference/action/object#action) -   [Action     condition](/manual/api/reference/action/object#action_condition) -   [Action     operation](/manual/api/reference/action/object#action_operation)  Available methods:\  -   [action.create](/manual/api/reference/action/create) - create new     actions -   [action.delete](/manual/api/reference/action/delete) - delete     actions -   [action.get](/manual/api/reference/action/get) - retrieve actions -   [action.update](/manual/api/reference/action/update) - update     actions
fa	# اکشن   این کلاس برای کار با اکشن ها طراحی شده است.  ارجاعات شیء:\  - [Action](/manual/api/reference/action/object#action) -   [عمل     شرط](/دستی/api/reference/action/object#action_condition) -   [عمل     عملیات](/دستی/api/reference/action/object#action_operation)  روش های موجود:\  - [action.create](/manual/api/reference/action/create) - ایجاد جدید     اقدامات - [action.delete](/manual/api/reference/action/delete) - حذف     اقدامات - [action.get](/manual/api/reference/action/get) - بازیابی اقدامات - [action.update](/manual/api/reference/action/update) - به روز رسانی     اقدامات

en-us	# action.update
fa	# action.update

en-us	# alert.get
fa	# alert.get

en-us	# > Alert object  The following objects are directly related to the `alert` API.
fa	# > آبجکت  هشدار  اشیاء زیر مستقیماً با API «هشدار» مرتبط هستند.

en-us	# Alert  This class is designed to work with alerts.  Object references:\  -   [Alert](/manual/api/reference/alert/object#alert)  Available methods:\  -   [alert.get](/manual/api/reference/alert/get) - retrieve alerts
fa	#هشدار  این کلاس برای کار با هشدار طراحی شده است.  ارجاعات شیء:\  - [هشدار](/دستی/api/reference/alert/object#alert)  روش های موجود:\  - [alert.get](/manual/api/reference/alert/get) - هشدارها را بازیابی کنید

en-us	# API info  This class is designed to retrieve meta information about the API.  Available methods:\  -   [apiinfo.version](/manual/api/reference/apiinfo/version) -     retrieving the version of the Zabbix API
fa	# اطلاعات API  این کلاس برای بازیابی اطلاعات متا در مورد API طراحی شده است.  روش های موجود:\  - [apiinfo.version](/manual/api/reference/apiinfo/version) -     بازیابی نسخه Zabbix API

en-us	# apiinfo.version
fa	# apiinfo.version

en-us	# Appendix 1. Reference commentary
fa	# ضمیمه 1. تفسیر مرجع

en-us	# auditlog.get
fa	# auditlog.get

en-us	# > Audit log object  The following objects are directly related to the `auditlog` API.
fa	# > شئ گزارش حسابرسی  اشیاء زیر مستقیماً با API «auditlog» مرتبط هستند.

en-us	# Audit log  This class is designed to work with audit log.  Object references:\  -   [Audit log object](/manual/api/reference/auditlog/object)  Available methods:\  -   [auditlog.get](/manual/api/reference/auditlog/get) - retrieve audit     log records
fa	# گزارش حسابرسی  این کلاس برای کار با گزارش حسابرسی طراحی شده است.  ارجاعات آبجکت:\  - [آبجکت گزارش حسابرسی](/manual/api/reference/auditlog/object)  روش های موجود:\  - [auditlog.get](/manual/api/reference/auditlog/get) - بازیابی رکوردهای گزارش ممیزی

en-us	# authentication.get
fa	دریافت احرازهویت

en-us	# > Authentication object  The following objects are directly related to the `authentication` API.
fa	# > شیء احراز هویت  اشیاء زیر مستقیماً با API «احراز هویت» مرتبط هستند.

en-us	# Authentication  This class is designed to work with authentication settings.  Object references:\  -   [Authentication](/manual/api/reference/authentication/object#authentication)  Available methods:\  -   [authentication.get](/manual/api/reference/authentication/get) -     retrieve authentication -   [authentication.update](/manual/api/reference/authentication/update) -     update authentication
fa	# احراز هویت  این کلاس برای کار با تنظیمات احراز هویت طراحی شده است.  مراجع شیء:\  - [احراز هویت](/دستی/api/reference/authentication/object#authentication)  روش های موجود:\  - [authentication.get](/manual/api/reference/authentication/get) -     بازیابی احراز هویت - [authentication.update](/manual/api/reference/authentication/update) -     به روز رسانی احراز هویت

en-us	# authentication.update
fa	به روز رسانی احرازهویت

en-us	## AUTHOR  Alexei Vladishev <<alex@zabbix.com>>  ------------------------------------------------------------------------  [ ]{#index}
fa	## نویسنده  Zabbix LLC  ------------------------------------------------ ----------------------  [ ]{#فهرست مطالب}

en-us	## AUTHOR  Alexei Vladishev <<alex@zabbix.com>>  ------------------------------------------------------------------------  [ ]{#index}
fa	## نویسنده  الکسی ولادیشف <<alex@zabbix.com>>  ------------------------------------------------ ----------------------  [ ]{#فهرست مطالب}

en-us	## AUTHOR  Alexei Vladishev <<alex@zabbix.com>>  ------------------------------------------------------------------------  [ ]{#index}
fa	## نویسنده  الکسی ولادیشف <<alex@zabbix.com>>  ------------------------------------------------ ----------------------  [ ]{#فهرست مطالب}

en-us	## AUTHOR  Zabbix LLC  ------------------------------------------------------------------------  [ ]{#index}
fa	## نویسنده  Zabbix LLC  ------------------------------------------------ ----------------------  [ ]{#فهرست مطالب}

en-us	## AUTHOR  Zabbix LLC  ------------------------------------------------------------------------  [ ]{#index}
fa	## نویسنده  Zabbix LLC  ------------------------------------------------ ----------------------  [ ]{#فهرست مطالب}

en-us	# autoregistration.get
fa	دریافت ثبت  خودکار

en-us	# > Autoregistration object  The following objects are directly related to the `autoregistration` API.
fa	# > شیء احراز هویت  اشیاء زیر مستقیماً با API «احراز هویت» مرتبط هستند.

en-us	# Autoregistration  This class is designed to work with autoregistration.  Object references:\  -   [Autoregistration](/manual/api/reference/autoregistration/object#autoregistration)  Available methods:\  -   [autoregistration.get](/manual/api/reference/autoregistration/get) -     retrieve autoregistration -   [autoregistration.update](/manual/api/reference/autoregistration/update) -     update autoregistration
fa	# احراز هویت  این کلاس برای کار با تنظیمات احراز هویت طراحی شده است.  مراجع شیء:\  - [احراز هویت](/دستی/api/reference/authentication/object#authentication)  روش های موجود:\  - [authentication.get](/manual/api/reference/authentication/get) -     بازیابی احراز هویت - [authentication.update](/manual/api/reference/authentication/update) -     به روز رسانی احراز هویت

en-us	# autoregistration.update
fa	دریافت ثبت  خودکار

en-us	##### Collapsed menu  When the menu is collapsed to icons only, a full menu reappears as soon as the mouse cursor is placed upon it. Note that it reappears over page content; to move page content to the right you have to click on the expand button. If the mouse cursor again is placed outside the full menu, the menu will collapse again after two seconds.  You can also make a collapsed menu reappear fully by hitting the Tab key. Hitting the Tab key repeatedly will allow to focus on the next menu element.
fa	##### Collapsed menu  When the menu is collapsed to icons only, a full menu reappears as soon as the mouse cursor is placed upon it. Note that it reappears over page content; to move page content to the right you have to click on the expand button. If the mouse cursor again is placed outside the full menu, the menu will collapse again after two seconds.  You can also make a collapsed menu reappear fully by hitting the Tab key. Hitting the Tab key repeatedly will allow to focus on the next menu element.

en-us	# configuration.export
fa	خروجی گرفتن از تنظیمات 

en-us	# configuration.import
fa	وارد کردن تنظیمات 

en-us	# configuration.importcompare
fa	مقایسه  تنظیمات وارد شده 

en-us	#### Configuring authentication  The **Authentication** tab allows you to configure scenario authentication options. A green dot next to the tab name indicates that some type of HTTP authentication is enabled.  ![](../../assets/en/manual/config/scenario_d.png)  Authentication parameters:  |Parameter|Description| |--|--------| |*Authentication*|Authentication options.<br>**None** - no authentication used.<br>**Basic** - basic authentication is used.<br>**NTLM** - NTLM ([Windows NT LAN Manager)](http://en.wikipedia.org/wiki/NTLM) authentication is used.<br>**Kerberos** - Kerberos authentication is used. See also: [Configuring Kerberos with Zabbix](/manual/appendix/items/kerberos).<br>**Digest** - Digest authentication is used.<br>Selecting an authentication method will provide two additional fields for entering a user name and password.<br>User macros can be used in user and password fields.| |*SSL verify peer*|Mark the checkbox to verify the SSL certificate of the web server.<br>The server certificate will be automatically taken from system-wide certificate authority (CA) location. You can override the location of CA files using Zabbix server or proxy configuration parameter [SSLCALocation](/manual/appendix/config/zabbix_server).<br>This sets the [CURLOPT\_SSL\_VERIFYPEER](http://curl.haxx.se/libcurl/c/CURLOPT_SSL_VERIFYPEER.html) cURL option.| |*SSL verify host*|Mark the checkbox to verify that the *Common Name* field or the *Subject Alternate Name* field of the web server certificate matches.<br>This sets the [CURLOPT\_SSL\_VERIFYHOST](http://curl.haxx.se/libcurl/c/CURLOPT_SSL_VERIFYHOST.html) cURL option.| |*SSL certificate file*|Name of the SSL certificate file used for client authentication. The certificate file must be in PEM^1^ format. If the certificate file contains also the private key, leave the *SSL key file* field empty. If the key is encrypted, specify the password in *SSL key password* field. The directory containing this file is specified by Zabbix server or proxy configuration parameter [SSLCertLocation](/manual/appendix/config/zabbix_server).<br>`HOST.*` macros and user macros can be used in this field.<br>This sets the [CURLOPT\_SSLCERT](http://curl.haxx.se/libcurl/c/CURLOPT_SSLCERT.html) cURL option.| |*SSL key file*|Name of the SSL private key file used for client authentication. The private key file must be in PEM^1^ format. The directory containing this file is specified by Zabbix server or proxy configuration parameter [SSLKeyLocation](/manual/appendix/config/zabbix_server).<br>`HOST.*` macros and user macros can be used in this field.<br>This sets the [CURLOPT\_SSLKEY](http://curl.haxx.se/libcurl/c/CURLOPT_SSLKEY.html) cURL option.| |*SSL key password*|SSL private key file password.<br>User macros can be used in this field.<br>This sets the [CURLOPT\_KEYPASSWD](http://curl.haxx.se/libcurl/c/CURLOPT_KEYPASSWD.html) cURL option.|  ::: noteimportant  \[1\] Zabbix supports certificate and private key files in PEM format only. In case you have your certificate and private key data in PKCS \#12 format file (usually with extension \*.p12 or \*.pfx) you may generate the PEM file from it using the following commands:      openssl pkcs12 -in ssl-cert.p12 -clcerts -nokeys -out ssl-cert.pem     openssl pkcs12 -in ssl-cert.p12 -nocerts -nodes  -out ssl-cert.key   :::  ::: noteclassic  Zabbix server picks up changes in certificates without a restart.  :::  ::: noteclassic  If you have client certificate and private key in a single file just specify it in a "SSL certificate file" field and leave "SSL key file" field empty. The certificate and key must still be in PEM format. Combining certificate and key is easy:      cat client.crt client.key > client.pem   :::
fa	#### تنظیم احراز هویت   The **Authentication** tab allows you to configure scenario authentication options. A green dot next to the tab name indicates that some type of HTTP authentication is enabled.  ![](../../assets/en/manual/config/scenario_d.png)  Authentication parameters:  |Parameter|Description| |--|--------| |*Authentication*|Authentication options.<br>**None** - no authentication used.<br>**Basic** - basic authentication is used.<br>**NTLM** - NTLM ([Windows NT LAN Manager)](http://en.wikipedia.org/wiki/NTLM) authentication is used.<br>**Kerberos** - Kerberos authentication is used. See also: [Configuring Kerberos with Zabbix](/manual/appendix/items/kerberos).<br>**Digest** - Digest authentication is used.<br>Selecting an authentication method will provide two additional fields for entering a user name and password.<br>User macros can be used in user and password fields.| |*SSL verify peer*|Mark the checkbox to verify the SSL certificate of the web server.<br>The server certificate will be automatically taken from system-wide certificate authority (CA) location. You can override the location of CA files using Zabbix server or proxy configuration parameter [SSLCALocation](/manual/appendix/config/zabbix_server).<br>This sets the [CURLOPT\_SSL\_VERIFYPEER](http://curl.haxx.se/libcurl/c/CURLOPT_SSL_VERIFYPEER.html) cURL option.| |*SSL verify host*|Mark the checkbox to verify that the *Common Name* field or the *Subject Alternate Name* field of the web server certificate matches.<br>This sets the [CURLOPT\_SSL\_VERIFYHOST](http://curl.haxx.se/libcurl/c/CURLOPT_SSL_VERIFYHOST.html) cURL option.| |*SSL certificate file*|Name of the SSL certificate file used for client authentication. The certificate file must be in PEM^1^ format. If the certificate file contains also the private key, leave the *SSL key file* field empty. If the key is encrypted, specify the password in *SSL key password* field. The directory containing this file is specified by Zabbix server or proxy configuration parameter [SSLCertLocation](/manual/appendix/config/zabbix_server).<br>`HOST.*` macros and user macros can be used in this field.<br>This sets the [CURLOPT\_SSLCERT](http://curl.haxx.se/libcurl/c/CURLOPT_SSLCERT.html) cURL option.| |*SSL key file*|Name of the SSL private key file used for client authentication. The private key file must be in PEM^1^ format. The directory containing this file is specified by Zabbix server or proxy configuration parameter [SSLKeyLocation](/manual/appendix/config/zabbix_server).<br>`HOST.*` macros and user macros can be used in this field.<br>This sets the [CURLOPT\_SSLKEY](http://curl.haxx.se/libcurl/c/CURLOPT_SSLKEY.html) cURL option.| |*SSL key password*|SSL private key file password.<br>User macros can be used in this field.<br>This sets the [CURLOPT\_KEYPASSWD](http://curl.haxx.se/libcurl/c/CURLOPT_KEYPASSWD.html) cURL option.|  ::: noteimportant  \[1\] Zabbix supports certificate and private key files in PEM format only. In case you have your certificate and private key data in PKCS \#12 format file (usually with extension \*.p12 or \*.pfx) you may generate the PEM file from it using the following commands:      openssl pkcs12 -in ssl-cert.p12 -clcerts -nokeys -out ssl-cert.pem     openssl pkcs12 -in ssl-cert.p12 -nocerts -nodes  -out ssl-cert.key   :::  ::: noteclassic  Zabbix server picks up changes in certificates without a restart.  :::  ::: noteclassic  If you have client certificate and private key in a single file just specify it in a "SSL certificate file" field and leave "SSL key file" field empty. The certificate and key must still be in PEM format. Combining certificate and key is easy:      cat client.crt client.key > client.pem   :::

en-us	#### Configuring tags  The **Tags** tab allows to define scenario-level [tags](/manual/config/tagging).  ![](../../assets/en/manual/config/scenario_c.png)  Tagging allows to filter web scenarios and web monitoring [items](/manual/web_monitoring/items).
fa	#### تنظیم تگ ها   The **Tags** tab allows to define scenario-level [tags](/manual/config/tagging).  ![](../../assets/en/manual/config/scenario_c.png)  Tagging allows to filter web scenarios and web monitoring [items](/manual/web_monitoring/items).

en-us	# correlation.create
fa	# ایجاد همبستگی 

en-us	# correlation.delete
fa	# correlation.delete

en-us	# correlation.get
fa	# correlation.get

en-us	# > Correlation object  The following objects are directly related to the `correlation` API.
fa	# > آبجکت همبستگی   اشیاء زیر مستقیماً با API «همبستگی» مرتبط هستند.

en-us	# Correlation  This class is designed to work with correlations.  Object references:\  -   [Correlation](/manual/api/reference/correlation/object#correlation)  Available methods:\  -   [correlation.create](/manual/api/reference/correlation/create) -     creating new correlations -   [correlation.delete](/manual/api/reference/correlation/delete) -     deleting correlations -   [correlation.get](/manual/api/reference/correlation/get) -     retrieving correlations -   [correlation.update](/manual/api/reference/correlation/update) -     updating correlations
fa	# همبستگی  این کلاس برای کار با همبستگی طراحی شده است.  ارجاعات شیء:\  - [همبستگی] (/ دستی / api / مرجع / همبستگی / شی # همبستگی)  روش های موجود:\  - [correlation.create](/manual/api/reference/correlation/create) -     ایجاد همبستگی های جدید - [correlation.delete](/manual/api/reference/correlation/delete) -     حذف همبستگی ها - [correlation.get](/manual/api/reference/correlation/get) -     بازیابی همبستگی ها - [correlation.update](/manual/api/reference/correlation/update) -     به روز رسانی همبستگی ها

en-us	# correlation.update
fa	# correlation.update

en-us	# dashboard.create
fa	ساخت داشبورد

en-us	# dashboard.delete
fa	حذف داشبورد

en-us	# dashboard.get
fa	# دریافت داشبورد

en-us	# > Dashboard object  The following objects are directly related to the `dashboard` API.
fa	# > شی داشبورد   آبجکت های زیر مستقیما به API داشبورد مرتبط می شوند .

en-us	# Dashboard  This class is designed to work with dashboards.  Object references:\  -   [Dashboard](/manual/api/reference/dashboard/object#dashboard) -   [Dashboard     page](/manual/api/reference/dashboard/object#dashboard_page) -   [Dashboard     widget](/manual/api/reference/dashboard/object#dashboard_widget) -   [Dashboard widget     field](/manual/api/reference/dashboard/object#dashboard_widget_field) -   [Dashboard     user](/manual/api/reference/dashboard/object#dashboard_user) -   [Dashboard user     group](/manual/api/reference/dashboard/object#dashboard_user_group)  Available methods:\  -   [dashboard.create](/manual/api/reference/dashboard/create) -     creating new dashboards -   [dashboard.delete](/manual/api/reference/dashboard/delete) -     deleting dashboards -   [dashboard.get](/manual/api/reference/dashboard/get) - retrieving     dashboards -   [dashboard.update](/manual/api/reference/dashboard/update) -     updating dashboards
fa	# داشبورد  This class is designed to work with dashboards.  Object references:\  -   [Dashboard](/manual/api/reference/dashboard/object#dashboard) -   [Dashboard     page](/manual/api/reference/dashboard/object#dashboard_page) -   [Dashboard     widget](/manual/api/reference/dashboard/object#dashboard_widget) -   [Dashboard widget     field](/manual/api/reference/dashboard/object#dashboard_widget_field) -   [Dashboard     user](/manual/api/reference/dashboard/object#dashboard_user) -   [Dashboard user     group](/manual/api/reference/dashboard/object#dashboard_user_group)  Available methods:\  -   [dashboard.create](/manual/api/reference/dashboard/create) -     creating new dashboards -   [dashboard.delete](/manual/api/reference/dashboard/delete) -     deleting dashboards -   [dashboard.get](/manual/api/reference/dashboard/get) - retrieving     dashboards -   [dashboard.update](/manual/api/reference/dashboard/update) -     updating dashboards

en-us	# dashboard.update
fa	به روز رسانی  داشبورد

en-us	# dcheck.get
fa	# dcheck.get

en-us	### Description  `string apiinfo.version(array)`  This method allows to retrieve the version of the Zabbix API.  ::: noteimportant This method is only available to unauthenticated users and must be called without the `auth` parameter in the JSON-RPC request. :::
fa	### شرح  `string apiinfo.version(array)`  این روش امکان بازیابی نسخه Zabbix API را فراهم می کند.  ::: نکته مهم این روش فقط برای غیر احراز هویت در دسترس است کاربران و باید بدون پارامتر «auth» در JSON-RPC فراخوانی شوند درخواست. :::

en-us	## DESCRIPTION  **zabbix\_agent2** is an application for monitoring parameters of various services.\ \ [ ]{#lbAE}
fa	## شرح  **zabbix\_agent2** یک برنامه کاربردی برای نظارت بر پارامترهای است خدمات مختلف.\ \ [ ]{#lbAE}

en-us	## DESCRIPTION  **zabbix\_agentd** is a daemon for monitoring various server parameters. [ ]{#lbAE}
fa	## شرح  **zabbix\_agentd** دیمونی برای نظارت بر پارامترهای مختلف سرور است. [ ]{#lbAE}

en-us	## DESCRIPTION  **zabbix\_get** is a command line utility for getting data from Zabbix agent. [ ]{#lbAE}
fa	## شرح  **zabbix\_get** یک ابزار خط فرمان برای دریافت داده از عامل Zabbix است. [ ]{#lbAE}

en-us	## DESCRIPTION  **zabbix\_js** is a command line utility that can be used for embedded script testing. [ ]{#lbAE}
fa	## شرح  **zabbix\_js** یک ابزار خط فرمان است که می تواند برای جاسازی استفاده شود تست اسکریپت [ ]{#lbAE}

en-us	## DESCRIPTION  **zabbix\_proxy** is a daemon that collects monitoring data from devices and sends it to Zabbix server. [ ]{#lbAE}
fa	## شرح  **zabbix\_proxy** دیمونی است که داده های نظارتی را از دستگاه ها جمع آوری می کند و آن را به سرور Zabbix ارسال می کند. [ ]{#lbAE}

en-us	## DESCRIPTION  **zabbix\_sender** is a command line utility for sending monitoring data to Zabbix server or proxy. On the Zabbix server an item of type **Zabbix trapper** should be created with corresponding key. Note that incoming values will only be accepted from hosts specified in **Allowed hosts** field for this item. [ ]{#lbAE}
fa	## شرح  **zabbix\_sender** یک ابزار خط فرمان برای ارسال داده های نظارت است به سرور یا پروکسی Zabbix. در سرور Zabbix موردی از نوع **Zabbix trapper** باید با کلید مربوطه ایجاد شود. توجه داشته باشید که ورودی مقادیر فقط از میزبان های مشخص شده در **میزبان های مجاز** پذیرفته می شود. فیلد برای این مورد [ ]{#lbAE}

en-us	## DESCRIPTION  **zabbix\_server** is the core daemon of Zabbix software. [ ]{#lbAE}
fa	## شرح  **zabbix\_server** دیمون اصلی نرم افزار Zabbix است. [ ]{#lbAE}

en-us	## DESCRIPTION  **zabbix\_web\_service** is an application for providing web services to Zabbix components. [ ]{#lbAE}
fa	## شرح  **zabbix\_web\_service** اپلیکیشنی برای ارائه خدمات وب به اجزای Zabbix [ ]{#lbAE}

en-us	#### Details about export  -   All supported elements are exported in one file. -   Host and template entities (items, triggers, graphs, discovery     rules) that are inherited from linked templates are not exported.     Any changes made to those entities on a host level (such as changed     item interval, modified regular expression or added prototypes to     the low-level discovery rule) will be lost when exporting; when     importing, all entities from linked templates are re-created as on     the original linked template. -   Entities created by low-level discovery and any entities depending     on them are not exported. For example, a trigger created for an     LLD-rule generated item will not be exported.
fa	#### جزئیات در مورد خروجی گرفتن   - تمام عناصر پشتیبانی شده در یک فایل صادر می شوند. - موجودیت های میزبان و قالب (اقلام، محرک ها، نمودارها، کشف     قوانین) که از الگوهای پیوندی به ارث رسیده اند صادر نمی شوند.     هر گونه تغییری که در آن نهادها در سطح میزبان ایجاد شود (مانند تغییر     فاصله آیتم، بیان منظم اصلاح شده یا نمونه های اولیه اضافه شده به     قانون کشف سطح پایین) هنگام صادرات از بین خواهد رفت. چه زمانی     با وارد کردن، همه موجودیت‌ها از قالب‌های پیوندی مجدداً ایجاد می‌شوند     الگوی لینک شده اصلی - موجودیت های ایجاد شده توسط اکتشاف سطح پایین و هر موجودیت وابسته     بر روی آنها صادر نمی شود. به عنوان مثال، یک ماشه ایجاد شده برای یک     مورد ایجاد شده با قانون LLD صادر نخواهد شد.

en-us	#### - Details  To avoid calculations with huge numbers, we consider the timestamp of the first value in specified period plus 1 ns as a new zero-time (current epoch time is of order 10^9^, epoch squared is 10^18^, double precision is about 10^-16^). 1 ns is added to provide all positive time values for *logarithmic* and *power* fits which involve calculating log(t). Time shift does not affect *linear*, *polynomial*, *exponential* (apart from easier and more precise calculations) but changes the shape of *logarithmic* and *power* functions.
fa	#### - Details  To avoid calculations with huge numbers we consider the timestamp of the first value in specified period plus 1 ns as a new zero-time (current epoch time is of order 10^9^, epoch squared is 10^18^, double precision is about 10^-16^). 1 ns is added to provide all positive time values for *logarithmic* and *power* fits which involve calculating log(t). Time shift does not affect *linear*, *polynomial*, *exponential* (apart from easier and more precise calculations) but changes the shape of *logarithmic* and *power* functions.

en-us	# dhost.get
fa	# dhost.get

en-us	### Discovered host  ::: noteclassic Discovered host are created by the Zabbix server and cannot be modified via the API. :::  The discovered host object contains information about a host discovered by a network discovery rule. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |dhostid|string|ID of the discovered host.| |druleid|string|ID of the discovery rule that detected the host.| |lastdown|timestamp|Time when the discovered host last went down.| |lastup|timestamp|Time when the discovered host last went up.| |status|integer|Whether the discovered host is up or down. A host is up if it has at least one active discovered service.<br><br>Possible values:<br>0 - host up;<br>1 - host down.|
fa	### هاست های پیدا شده   ::: noteclassic Discovered host are created by the Zabbix server and cannot be modified via the API. :::  The discovered host object contains information about a host discovered by a network discovery rule. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |dhostid|string|ID of the discovered host.| |druleid|string|ID of the discovery rule that detected the host.| |lastdown|timestamp|Time when the discovered host last went down.| |lastup|timestamp|Time when the discovered host last went up.| |status|integer|Whether the discovered host is up or down. A host is up if it has at least one active discovered service.<br><br>Possible values:<br>0 - host up;<br>1 - host down.|

en-us	# > Discovered host object  The following objects are directly related to the `dhost` API.
fa	# > آبجکت های هاست جست و جو شده   The following objects are directly related to the `dhost` API.

en-us	# Discovered host  This class is designed to work with discovered hosts.  Object references:\  -   [Discovered     host](/manual/api/reference/dhost/object#discovered_host)  Available methods:\  -   [dhost.get](/manual/api/reference/dhost/get) - retrieve discovered     hosts
fa	# هاست های پیدا شده   این کلاس برای کار با هاست های پیدا شده طراحی شده است .  Object references:\  -   [Discovered     host](/manual/api/reference/dhost/object#discovered_host)  Available methods:\  -   [dhost.get](/manual/api/reference/dhost/get) - retrieve discovered     hosts

en-us	### Discovered service  ::: noteclassic Discovered services are created by the Zabbix server and cannot be modified via the API. :::  The discovered service object contains information about a service discovered by a network discovery rule on a host. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |dserviceid|string|ID of the discovered service.| |dcheckid|string|ID of the discovery check used to detect the service.| |dhostid|string|ID of the discovered host running the service.| |dns|string|DNS of the host running the service.| |ip|string|IP address of the host running the service.| |lastdown|timestamp|Time when the discovered service last went down.| |lastup|timestamp|Time when the discovered service last went up.| |port|integer|Service port number.| |status|integer|Status of the service.<br><br>Possible values:<br>0 - service up;<br>1 - service down.| |value|string|Value returned by the service when performing a Zabbix agent, SNMPv1, SNMPv2 or SNMPv3 discovery check.|
fa	### سرویس جست و جو شده   ::: noteclassic Discovered services are created by the Zabbix server and cannot be modified via the API. :::  The discovered service object contains information about a service discovered by a network discovery rule on a host. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |dserviceid|string|ID of the discovered service.| |dcheckid|string|ID of the discovery check used to detect the service.| |dhostid|string|ID of the discovered host running the service.| |dns|string|DNS of the host running the service.| |ip|string|IP address of the host running the service.| |lastdown|timestamp|Time when the discovered service last went down.| |lastup|timestamp|Time when the discovered service last went up.| |port|integer|Service port number.| |status|integer|Status of the service.<br><br>Possible values:<br>0 - service up;<br>1 - service down.| |value|string|Value returned by the service when performing a Zabbix agent, SNMPv1, SNMPv2 or SNMPv3 discovery check.|

en-us	# > Discovered service object  The following objects are directly related to the `dservice` API.
fa	# > آبجکت سرویس جست و جو شده   The following objects are directly related to the `dservice` API.

en-us	# Discovered service  This class is designed to work with discovered services.  Object references:\  -   [Discovered     service](/manual/api/reference/dservice/object#discovered_service)  Available methods:\  -   [dservice.get](/manual/api/reference/dservice/get) - retrieve     discovered services
fa	# سرویس های جست وجو شده   This class is designed to work with discovered services.  Object references:\  -   [Discovered     service](/manual/api/reference/dservice/object#discovered_service)  Available methods:\  -   [dservice.get](/manual/api/reference/dservice/get) - retrieve     discovered services

en-us	# > Discovery check object  The following objects are directly related to the `dcheck` API.
fa	# > آبجکت های بررسی جست جو ها   The following objects are directly related to the `dcheck` API.

en-us	# Discovery check  This class is designed to work with discovery checks.  Object references:\  -   [Discovery     check](/manual/api/reference/dcheck/object#discovery_check)  Available methods:\  -   [dcheck.get](/manual/api/reference/dcheck/get) - retrieve discovery     checks
fa	# Discovery check  This class is designed to work with discovery checks.  Object references:\  -   [Discovery     check](/manual/api/reference/dcheck/object#discovery_check)  Available methods:\  -   [dcheck.get](/manual/api/reference/dcheck/get) - retrieve discovery     checks

en-us	 ##### Discovery of disabled systemd units  Since Zabbix 6.0.1 it is also possible to discover **disabled** systemd units. In this case  three macros are returned in the resulting JSON:   -    {#UNIT.PATH} -    {#UNIT.ACTIVESTATE} -    {#UNIT.UNITFILESTATE}.   ::: noteimportant To have items and triggers created from prototypes for disabled systemd units, make sure to  adjust (or remove) prohibiting LLD filters for {#UNIT.ACTIVESTATE} and {#UNIT.UNITFILESTATE}. :::
fa	##### Discovery of disabled systemd units  Since Zabbix 6.0.1 it is also possible to discover **disabled** systemd units. In this case  three macros are returned in the resulting JSON:   -    {#UNIT.PATH} -    {#UNIT.ACTIVESTATE} -    {#UNIT.UNITFILESTATE}.   ::: noteimportant To have items and triggers created from prototypes for disabled systemd units, make sure to  adjust (or remove) prohibiting LLD filters for {#UNIT.ACTIVESTATE} and {#UNIT.UNITFILESTATE}. :::

en-us	# discoveryrule.copy
fa	# کپی کردن قوانین جست وجو 

en-us	# discoveryrule.create
fa	# ساختن قوانین جست وجو 

en-us	# discoveryrule.delete
fa	# پاک کردن قوانین جست وجو 

en-us	# discoveryrule.get
fa	# گرفتن قوانین جست وجو 

en-us	# > Discovery rule object  The following objects are directly related to the `drule` API.
fa	# >آبجکت قانون جست و جو  The following objects are directly related to the `drule` API.

en-us	# Discovery rule  This class is designed to work with network discovery rules.  ::: notetip This API is meant to work with network discovery rules. For the low-level discovery rules see the [LLD rule API](discoveryrule). :::  Object references:\  -   [Discovery rule](/manual/api/reference/drule/object#discovery_rule)  Available methods:\  -   [drule.create](/manual/api/reference/drule/create) - create new     discovery rules -   [drule.delete](/manual/api/reference/drule/delete) - delete     discovery rules -   [drule.get](/manual/api/reference/drule/get) - retrieve discovery     rules -   [drule.update](/manual/api/reference/drule/update) - update     discovery rules
fa	# قانون جست و جو   This class is designed to work with network discovery rules.  ::: notetip This API is meant to work with network discovery rules. For the low-level discovery rules see the [LLD rule API](discoveryrule). :::  Object references:\  -   [Discovery rule](/manual/api/reference/drule/object#discovery_rule)  Available methods:\  -   [drule.create](/manual/api/reference/drule/create) - create new     discovery rules -   [drule.delete](/manual/api/reference/drule/delete) - delete     discovery rules -   [drule.get](/manual/api/reference/drule/get) - retrieve discovery     rules -   [drule.update](/manual/api/reference/drule/update) - update     discovery rules

en-us	# discoveryrule.update
fa	# به روز رسانی قوانین جست وجو 

en-us	# drule.create
fa	# ساختن

en-us	# drule.delete
fa	پاک کردن قانون جست وجو 

en-us	# drule.get
fa	دریافت حذف قانون جست و جو 

en-us	# drule.update
fa	# آپدیت قانون جست و جو

en-us	# dservice.get
fa	# دریافت سرویس جست و جو 

en-us	#### Element tags  Element tag values are explained in the table below.
fa	#### برچسب های عنصر  مقادیر تگ عنصر در جدول زیر توضیح داده شده است.

en-us	#### Element tags  Element tag values are explained in the table below.
fa	#### برچسب های عنصر  مقادیر تگ عنصر در جدول زیر توضیح داده شده است.

en-us	# event.acknowledge
fa	# تایید رویداد 

en-us	# event.get
fa	دریافت رخداد 

en-us	# > Event object  The following objects are directly related to the `event` API.
fa	# > آبکت رویداد   The following objects are directly related to the `event` API.

en-us	### Event tag  The event tag object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |tag|string|Event tag name.| |value|string|Event tag value.|
fa	### تگ رویداد  The event tag object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |tag|string|Event tag name.| |value|string|Event tag value.|

en-us	# Event  This class is designed to work with events.  Object references:\  -   [Event](/manual/api/reference/event/object#host)  Available methods:\  -   [event.get](/manual/api/reference/event/get) - retrieving events -   [event.acknowledge](/manual/api/reference/event/acknowledge) -     acknowledging events
fa	# رویداد  This class is designed to work with events.  Object references:\  -   [Event](/manual/api/reference/event/object#host)  Available methods:\  -   [event.get](/manual/api/reference/event/get) - retrieving events -   [event.acknowledge](/manual/api/reference/event/acknowledge) -     acknowledging events

en-us	### Example
fa	### مثال

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	### Examples
fa	### مثال ها

en-us	#### - Examples and dealing with errors  To get a warning when you are about to run out of free disk space on your host, you may use a trigger expression like this:      timeleft(/host/vfs.fs.size[/,free],1h,0)}<1h  However, error code -1 may come into play and put your trigger in a problem state. Generally it's good because you get a warning that your predictions don't work correctly and you should look at them more thoroughly to find out why. But sometimes it's bad because -1 can simply mean that there was no data about the host free disk space obtained in the last hour. If you are getting too many false positive alerts, consider using more complicated trigger expression [^5]:      timeleft(/host/vfs.fs.size[/,free],1h,0)<1h and timeleft(/host/vfs.fs.size[/,free],1h,0)<>-1  The situation is a bit more difficult with **forecast**. First of all, -1 may or may not put the trigger in a problem state depending on whether you have expression like `forecast(/host/item,(...))<...` or like `forecast(/host/item,(...))>...`  Furthermore, -1 may be a valid forecast if it's normal for the item value to be negative. But probability of this situation in the real world situation is negligible (see [how](/manual/config/triggers/expression) the operator **=** works). So add `... or forecast(/host/item,(...))=-1` or `... and forecast(/host/item,(...))<>-1` if you want or don't want to treat -1 as a problem respectively.  [^1]: For example, a simple trigger like     `timeleft(/host/item,1h,X) < 1h` may go into problem state when the     item value approaches X and then suddenly recover once value X is     reached. If the problem is item value being below X, use:     `last(/host/item) < X or timeleft(/host/item,1h,X) < 1h` If the     problem is item value being above X use:     `last(/host/item) > X or timeleft(/host/item,1h,X) < 1h`  [^2]: Polynomial degree can be from 1 to 6, *polynomial1* is equivalent     to *linear*. However, use higher degree polynomials [with     caution](https://en.wikipedia.org/wiki/Runge's_phenomenon). If the     evaluation period contains less points than needed to determine     polynomial coefficients, polynomial degree will be lowered (e.g.,     *polynomial5* is requested, but there are only 4 points, therefore     *polynomial3* will be fitted).  [^3]: For example, fitting *exponential* or *power* functions involves     calculating log() of item values. If data contains zeros or negative     numbers, you will get an error since log() is defined for positive     values only.  [^4]: For *linear*, *exponential*, *logarithmic* and *power* fits all     necessary calculations can be written explicitly. For *polynomial*     only *value* can be calculated without any additional steps.     Calculating *avg* involves computing polynomial antiderivative     (analytically). Computing *max*, *min* and *delta* involves     computing polynomial derivative (analytically) and finding its roots     (numerically). Solving f(t) = 0 involves finding polynomial roots     (numerically).  [^5]: But in this case -1 can cause your trigger to recover from the     problem state. To be fully protected use:     `timeleft(/host/vfs.fs.size[/,free],1h,0)<1h and ({TRIGGER.VALUE}=0 and timeleft(/host/vfs.fs.size[/,free],1h,0)<>-1 or {TRIGGER.VALUE}=1)`
fa	#### - Examples and dealing with errors  To get a warning when you are about to run out of free disk space on your host you may use a trigger expression like this:      timeleft(/host/vfs.fs.size[/,free],1h,0)}<1h  However, error code -1 may come into play and put your trigger in a problem state. Generally it's good because you get a warning that your predictions don't work correctly and you should look at them more thoroughly to find out why. But sometimes it's bad because -1 can simply mean that there was no data about the host free disk space obtained in the last hour. If you are getting too many false positive alerts consider using more complicated trigger expression [^5]:      timeleft(/host/vfs.fs.size[/,free],1h,0)<1h and timeleft(/host/vfs.fs.size[/,free],1h,0)<>-1  The situation is a bit more difficult with **forecast**. First of all, -1 may or may not put the trigger in a problem state depending on whether you have expression like `forecast(/host/item,(...))<...` or like `forecast(/host/item,(...))>...`  Furthermore, -1 may be a valid forecast if it's normal for the item value to be negative. But probability of this situation in the real world situation is negligible (see [how](/manual/config/triggers/expression) the operator **=** works). So add `... or forecast(/host/item,(...))=-1` or `... and forecast(/host/item,(...))<>-1` if you want or don't want to treat -1 as a problem respectively.  [^1]: For example, a simple trigger like     `timeleft(/host/item,1h,X) < 1h` may go into problem state when the     item value approaches X and then suddenly recover once value X is     reached. If the problem is item value being below X use:     `last(/host/item) < X or timeleft(/host/item,1h,X) < 1h` If the     problem is item value being above X use:     `last(/host/item) > X or timeleft(/host/item,1h,X) < 1h`  [^2]: Polynomial degree can be from 1 to 6, *polynomial1* is equivalent     to *linear*. However, use higher degree polynomials [with     caution](https://en.wikipedia.org/wiki/Runge's_phenomenon). If the     evaluation period contains less points than needed to determine     polynomial coefficients, polynomial degree will be lowered (e.g     *polynomial5* is requested, but there are only 4 points, therefore     *polynomial3* will be fitted).  [^3]: For example fitting *exponential* or *power* functions involves     calculating log() of item values. If data contains zeros or negative     numbers you will get an error since log() is defined for positive     values only.  [^4]: For *linear*, *exponential*, *logarithmic* and *power* fits all     necessary calculations can be written explicitly. For *polynomial*     only *value* can be calculated without any additional steps.     Calculating *avg* involves computing polynomial antiderivative     (analytically). Computing *max*, *min* and *delta* involves     computing polynomial derivative (analytically) and finding its roots     (numerically). Solving f(t) = 0 involves finding polynomial roots     (numerically).  [^5]: But in this case -1 can cause your trigger to recover from the     problem state. To be fully protected use:     `timeleft(/host/vfs.fs.size[/,free],1h,0)<1h and ({TRIGGER.VALUE}=0 and timeleft(/host/vfs.fs.size[/,free],1h,0)<>-1 or {TRIGGER.VALUE}=1)`

en-us	## EXAMPLES  **zabbix\_get -s 127.0.0.1 -p 10050 -k "system.cpu.load\[all,avg1\]"**\ **zabbix\_get -s 127.0.0.1 -p 10050 -k "system.cpu.load\[all,avg1\]" --tls-connect cert --tls-ca-file /home/zabbix/zabbix\_ca\_file --tls-agent-cert-issuer "CN=Signing CA,OU=IT operations,O=Example Corp,DC=example,DC=com" --tls-agent-cert-subject "CN=server1,OU=IT operations,O=Example Corp,DC=example,DC=com" --tls-cert-file /home/zabbix/zabbix\_get.crt --tls-key-file /home/zabbix/zabbix\_get.key\ zabbix\_get -s 127.0.0.1 -p 10050 -k "system.cpu.load\[all,avg1\]" --tls-connect psk --tls-psk-identity "PSK ID Zabbix agentd" --tls-psk-file /home/zabbix/zabbix\_agentd.psk** [ ]{#lbAH}
fa	## مثال ها  **zabbix\_get -s 127.0.0.1 -p 10050 -k "system.cpu.load\[all,avg1\]"**\ **zabbix\_get -s 127.0.0.1 -p 10050 -k "system.cpu.load\[all,avg1\]" --tls-connect Cert --tls-ca-file /home/zabbix/zabbix\_ca\_file --tls-agent-cert-issuer "CN=امضای عملیات CA,OU=IT,O=مثال Corp,DC=example,DC=com" --tls-agent-cert-subject "CN=server1,OU=IT عملیات,O=Example Corp,DC=example,DC=com" --tls-cert-file /home/zabbix/zabbix\_get.crt --tls-key-file /home/zabbix/zabbix\_get.key\ zabbix\_get -s 127.0.0.1 -p 10050 -k "system.cpu.load\[all,avg1\]" --tls-connect psk --tls-psk-identity "PSK ID Zabbix agentd" --tls-psk-file /home/zabbix/zabbix\_agentd.psk** [ ]{#lbAH}

en-us	## EXAMPLES  **zabbix\_js -s script-file.js -p example** [ ]{#lbAG}
fa	## مثال ها  **zabbix\_js -s script-file.js -p مثال** [ ]{#lbAG}

en-us	## EXAMPLES  **zabbix\_sender -c /etc/zabbix/zabbix\_agentd.conf -k mysql.queries -o 342.45**\     Send **342.45** as the value for **mysql.queries** item of monitored host. Use monitored host and Zabbix server defined in agent configuration file.  **zabbix\_sender -c /etc/zabbix/zabbix\_agentd.conf -s "Monitored Host" -k mysql.queries -o 342.45**\     Send **342.45** as the value for **mysql.queries** item of **Monitored Host** host using Zabbix server defined in agent configuration file.  \ **zabbix\_sender -z 192.168.1.113 -i data\_values.txt**     \ Send values from file **data\_values.txt** to Zabbix server with IP **192.168.1.113**. Host names and keys are defined in the file.  \ **echo "- hw.serial.number 1287872261 SQ4321ASDF" | zabbix\_sender -c /usr/local/etc/zabbix\_agentd.conf -T -i -**\     Send a timestamped value from the commandline to Zabbix server, specified in the agent configuration file. Dash in the input data indicates that hostname also should be used from the same configuration file.  \ **echo '"Zabbix server" trapper.item ""' | zabbix\_sender -z 192.168.1.113 -p 10000 -i -**\     Send empty value of an item to the Zabbix server with IP address **192.168.1.113** on port **10000** from the commandline. Empty values must be indicated by empty double quotes.  **zabbix\_sender -z 192.168.1.113 -s "Monitored Host" -k mysql.queries -o 342.45 --tls-connect cert --tls-ca-file /home/zabbix/zabbix\_ca\_file --tls-cert-file /home/zabbix/zabbix\_agentd.crt --tls-key-file /home/zabbix/zabbix\_agentd.key**\     Send **342.45** as the value for **mysql.queries** item in **Monitored Host** host to server with IP **192.168.1.113** using TLS with certificate.  **zabbix\_sender -z 192.168.1.113 -s "Monitored Host" -k mysql.queries -o 342.45 --tls-connect psk --tls-psk-identity "PSK ID Zabbix agentd" --tls-psk-file /home/zabbix/zabbix\_agentd.psk**\     Send **342.45** as the value for **mysql.queries** item in **Monitored Host** host to server with IP **192.168.1.113** using TLS with pre-shared key (PSK).  [ ]{#lbAI}
fa	## مثال ها  **zabbix\_sender -c /etc/zabbix/zabbix\_agentd.conf -k mysql.queries -o 342.45**\     ارسال **342.45** به عنوان مقدار برای **mysql.queries** مورد نظارت شده میزبان. از میزبان نظارت شده و سرور Zabbix تعریف شده در عامل استفاده کنید فایل پیکربندی.  **zabbix\_sender -c /etc/zabbix/zabbix\_agentd.conf -s "میزبان نظارت شده" -k mysql.queries -o 342.45**\     ارسال **342.45** به عنوان مقدار برای **mysql.queries** مورد **Monitored میزبان ** با استفاده از سرور Zabbix تعریف شده در فایل پیکربندی عامل.  \ **zabbix\_sender -z 192.168.1.113 -i data\_values.txt**     \ مقادیر را از فایل **data\_values.txt** به سرور Zabbix با IP ارسال کنید **192.168.1.113**. نام هاست و کلیدها در فایل تعریف شده است.  \ **echo "- hw.serial.number 1287872261 SQ4321ASDF" | zabbix\_sender -c /usr/local/etc/zabbix\_agentd.conf -T -i -**\     یک مقدار مهر زمانی از خط فرمان به سرور Zabbix ارسال کنید، در فایل پیکربندی عامل مشخص شده است. خط تیره در داده های ورودی نشان می دهد که نام میزبان نیز باید از همان پیکربندی استفاده شود فایل.  \ **echo '"سرور Zabbix" trapper.item ""' | zabbix\_sender -z 192.168.1.113 -p 10000 -i -**\     مقدار خالی یک مورد را با آدرس IP به سرور Zabbix ارسال کنید **192.168.1.113** در پورت **10000** از خط فرمان. ارزش های خالی باید با دو نقل قول خالی نشان داده شود.  **zabbix\_sender -z 192.168.1.113 -s "میزبان نظارت شده" -k mysql.queries -o 342.45 --tls-connect Cert --tls-ca-file /home/zabbix/zabbix\_ca\_file --tls-cert-file /home/zabbix/zabbix\_agentd.crt --tls-key-file /home/zabbix/zabbix\_agentd.key**\     ارسال **342.45** به عنوان مقدار مورد **mysql.queries** در **Monitored میزبان ** میزبان به سرور با IP **192.168.1.113** با استفاده از TLS با گواهی  **zabbix\_sender -z 192.168.1.113 -s "میزبان نظارت شده" -k mysql.queries -o 342.45 --tls-connect psk --tls-psk-identity "PSK ID Zabbix agent" --tls-psk-file /home/zabbix/zabbix\_agentd.psk**\     ارسال **342.45** به عنوان مقدار مورد **mysql.queries** در **Monitored میزبان ** میزبان به سرور با IP **192.168.1.113** با استفاده از TLS با کلید از پیش مشترک (PSK).  [ ]{#lbAI}

en-us	## EXIT STATUS  The exit status is 0 if the values were sent and all of them were successfully processed by server. If data was sent, but processing of at least one of the values failed, the exit status is 2. If data sending failed, the exit status is 1.  [ ]{#lbAH}
fa	## وضعیت خروج  اگر مقادیر ارسال شده باشند و همه آنها ارسال شده باشند، وضعیت خروج 0 است با موفقیت توسط سرور پردازش شد. اگر داده ها ارسال شد، اما پردازش در حداقل یکی از مقادیر ناموفق، وضعیت خروج 2 است. در صورت ارسال داده ها ناموفق، وضعیت خروج 1 است.  [ ]{#lbAH}

en-us	##### Export format  Data can be exported using the Zabbix web frontend or [Zabbix API](/manual/api/reference/configuration). Supported export formats are YAML, XML and JSON.
fa	##### فرمت صادرات  داده ها را می توان با استفاده از صفحه وب Zabbix یا [Zabbix صادر کرد API](/دستی/api/reference/configuration). فرمت های صادراتی پشتیبانی شده هستند YAML، XML و JSON.

en-us	#### Extended monitoring  Sometimes it is necessary to log received HTML page content. This is especially useful if some web scenario step fails. Debug level 5 (trace) serves that purpose. This level can be set in [server](/manual/appendix/config/zabbix_server) and [proxy](/manual/appendix/config/zabbix_proxy) configuration files or using a runtime control option (`-R log_level_increase="http poller,N"`, where N is the process number). The following examples demonstrate how extended monitoring can be started provided debug level 4 is already set:      Increase log level of all http pollers:     shell> zabbix_server -R log_level_increase="http poller"      Increase log level of second http poller:     shell> zabbix_server -R log_level_increase="http poller,2"  If extended web monitoring is not required it can be stopped using the `-R log_level_decrease` option.
fa	#### گسترش مانیتورینگ   Sometimes it is necessary to log received HTML page content. This is especially useful if some web scenario step fails. Debug level 5 (trace) serves that purpose. This level can be set in [server](/manual/appendix/config/zabbix_server) and [proxy](/manual/appendix/config/zabbix_proxy) configuration files or using a runtime control option (`-R log_level_increase="http poller,N"`, where N is the process number). The following examples demonstrate how extended monitoring can be started provided debug level 4 is already set:      Increase log level of all http pollers:     shell> zabbix_server -R log_level_increase="http poller"      Increase log level of second http poller:     shell> zabbix_server -R log_level_increase="http poller,2"  If extended web monitoring is not required it can be stopped using the `-R log_level_decrease` option.

en-us	## FILES  */usr/local/etc/zabbix\_agent2.conf*   Default location of Zabbix agent 2 configuration file (if not modified during compile time).  [ ]{#lbAH}
fa	## فایل ها  */usr/local/etc/zabbix\_agent2.conf* محل پیش‌فرض فایل پیکربندی عامل Zabbix 2 (در صورت عدم تغییر در طول زمان کامپایل).  [ ]{#lbAH}

en-us	## FILES  */usr/local/etc/zabbix\_agentd.conf*   Default location of Zabbix agent configuration file (if not modified during compile time).  [ ]{#lbAI}
fa	## فایل ها  */usr/local/etc/zabbix\_agent2.conf* محل پیش‌فرض فایل پیکربندی عامل Zabbix 2 (در صورت عدم تغییر در طول زمان کامپایل).  [ ]{#lbAH}

en-us	## FILES  */usr/local/etc/zabbix\_proxy.conf*   Default location of Zabbix proxy configuration file (if not modified during compile time).  [ ]{#lbAI}
fa	## فایل ها  */usr/local/etc/zabbix\_agent2.conf* محل پیش‌فرض فایل پیکربندی عامل Zabbix 2 (در صورت عدم تغییر در طول زمان کامپایل).  [ ]{#lbAH}

en-us	## FILES  */usr/local/etc/zabbix\_server.conf*   Default location of Zabbix server configuration file (if not modified during compile time).  [ ]{#lbAI}
fa	## فایل ها  */usr/local/etc/zabbix\_server.conf* محل پیش‌فرض فایل پیکربندی سرور Zabbix (در صورت عدم تغییر در طول زمان کامپایل).  [ ]{#lbAI}

en-us	## FILES  */usr/local/etc/zabbix\_web\_service.conf*   Default location of Zabbix web service configuration file (if not modified during compile time).  [ ]{#lbAG}
fa	## فایل ها  */usr/local/etc/zabbix\_web\_service.conf* محل پیش‌فرض فایل پیکربندی وب سرویس Zabbix (اگر نه در طول زمان کامپایل اصلاح شد).  [ ]{#lbAG}

en-us	### Float history  The float history object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |clock|timestamp|Time when that value was received.| |itemid|string|ID of the related item.| |ns|integer|Nanoseconds when the value was received.| |value|float|Received value.|
fa	### تاریخچه Float  The float history object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |clock|timestamp|Time when that value was received.| |itemid|string|ID of the related item.| |ns|integer|Nanoseconds when the value was received.| |value|float|Received value.|

en-us	##### Footnotes  ^**1**^ For string values, only the string will be exported (e.g. "EMAIL") without the numbering used in this table. The numbers for range values (corresponding to the API values) in this table is used for ordering only.
fa	##### پانویسها و منابع  ^**1**^ برای مقادیر رشته، فقط رشته صادر خواهد شد (به عنوان مثال. "ZABBIX\_ACTIVE") بدون شماره گذاری استفاده شده در این جدول. شماره برای مقادیر محدوده (مرتبط با مقادیر API) در این جدول استفاده شده است فقط برای سفارش

en-us	##### Footnotes  ^**1**^ For string values, only the string will be exported (e.g. "ZABBIX\_ACTIVE") without the numbering used in this table. The numbers for range values (corresponding to the API values) in this table is used for ordering only.
fa	##### پانویسها و منابع  ^**1**^ برای مقادیر رشته، فقط رشته صادر خواهد شد (به عنوان مثال. "ZABBIX\_ACTIVE") بدون شماره گذاری استفاده شده در این جدول. شماره برای مقادیر محدوده (مرتبط با مقادیر API) در این جدول استفاده شده است فقط برای سفارش

en-us	##### Footnotes  ^**1**^ For string values, only the string will be exported (e.g. "ZABBIX\_ACTIVE") without the numbering used in this table. The numbers for range values (corresponding to the API values) in this table is used for ordering only.
fa	##### پانویسها و منابع  ^**1**^ برای مقادیر رشته، فقط رشته صادر خواهد شد (به عنوان مثال. "ZABBIX\_ACTIVE") بدون شماره گذاری استفاده شده در این جدول. شماره برای مقادیر محدوده (مرتبط با مقادیر API) در این جدول استفاده شده است فقط برای سفارش

en-us	# graph.create
fa	ساخت گراف

en-us	# graph.delete
fa	# حذف گراف

en-us	# graph.get
fa	#دریافت گراف 

en-us	# graphitem.get
fa	# دریافت آیتم های گراف

en-us	# > Graph item object  The following objects are directly related to the `graphitem` API.
fa	# > آبجکت های آیتم گراف  The following objects are directly related to the `graphitem` API.

en-us	# Graph item  This class is designed to work with graph items.  Object references:\  -   [Graph item](/manual/api/reference/graphitem/object#graph_item)  Available methods:\  -   [graphitem.get](/manual/api/reference/graphitem/get) - retrieving     graph items
fa	# آیتم گراف  This class is designed to work with graph items.  Object references:\  -   [Graph item](/manual/api/reference/graphitem/object#graph_item)  Available methods:\  -   [graphitem.get](/manual/api/reference/graphitem/get) - retrieving     graph items

en-us	# > Graph object  The following objects are directly related to the `graph` API.
fa	# > آبجکت گراف  The following objects are directly related to the `graph` API.

en-us	# graphprototype.create
fa	# ساخت نمونه گراف 

en-us	# graphprototype.delete
fa	# حذف نمونه اولیه گراف 

en-us	# graphprototype.get
fa	# دریافت نمونه اولیه گراف 

en-us	# > Graph prototype object  The following objects are directly related to the `graphprototype` API.
fa	# > آبجکت نمونه اولیه گراف   The following objects are directly related to the `graphprototype` API.

en-us	# Graph prototype  This class is designed to work with graph prototypes.  Object references:\  -   [Graph     prototype](/manual/api/reference/graphprototype/object#graph_prototype)  Available methods:\  -   [graphprototype.create](/manual/api/reference/graphprototype/create) -     creating new graph prototypes -   [graphprototype.delete](/manual/api/reference/graphprototype/delete) -     deleting graph prototypes -   [graphprototype.get](/manual/api/reference/graphprototype/get) -     retrieving graph prototypes -   [graphprototype.update](/manual/api/reference/graphprototype/update) -     updating graph prototypes
fa	# نمونه اولیه گراف   This class is designed to work with graph prototypes.  Object references:\  -   [Graph     prototype](/manual/api/reference/graphprototype/object#graph_prototype)  Available methods:\  -   [graphprototype.create](/manual/api/reference/graphprototype/create) -     creating new graph prototypes -   [graphprototype.delete](/manual/api/reference/graphprototype/delete) -     deleting graph prototypes -   [graphprototype.get](/manual/api/reference/graphprototype/get) -     retrieving graph prototypes -   [graphprototype.update](/manual/api/reference/graphprototype/update) -     updating graph prototypes

en-us	# graphprototype.update
fa	# آپدیت نمونه اولیه گراف 

en-us	# Graph  This class is designed to work with graphs.  Object references:\  -   [Graph](/manual/api/reference/graph/object#graph)  Available methods:\  -   [graph.create](/manual/api/reference/graph/create) - creating new     graphs -   [graph.delete](/manual/api/reference/graph/delete) - deleting graphs -   [graph.get](/manual/api/reference/graph/get) - retrieving graphs -   [graph.update](/manual/api/reference/graph/update) - updating graphs
fa	# نمونه اولیه گراف   This class is designed to work with graph prototypes.  Object references:\  -   [Graph     prototype](/manual/api/reference/graphprototype/object#graph_prototype)  Available methods:\  -   [graphprototype.create](/manual/api/reference/graphprototype/create) -     creating new graph prototypes -   [graphprototype.delete](/manual/api/reference/graphprototype/delete) -     deleting graph prototypes -   [graphprototype.get](/manual/api/reference/graphprototype/get) -     retrieving graph prototypes -   [graphprototype.update](/manual/api/reference/graphprototype/update) -     updating graph prototypes

en-us	# graph.update
fa	# آپدیت گراف

en-us	# hanode.get
fa	# دریافت نود HA

en-us	##### Hidden menu  Even when the menu is hidden completely, a full menu is just one mouse click away, by clicking on the burger icon. Note that it reappears over page content; to move page content to the right you have to unhide the menu by clicking on the show sidebar button.
fa	##### Hidden menu  Even when the menu is hidden completely, a full menu is just one mouse click away, by clicking on the burger icon. Note that it reappears over page content; to move page content to the right you have to unhide the menu by clicking on the show sidebar button.

en-us	# > High availability node object  The following object is related to operating a High availability cluster of Zabbix servers.
fa	# > آبجکت نود HA  The following object is related to operating a High availability cluster of Zabbix servers.

en-us	# High availability node  This class is designed to work with server nodes that are part of a High availability cluster, or a standalone server instance.  Object references:\  -   [High availability node](/manual/api/reference/hanode/object#hanode)  Available methods:\  -   [hanode.get](/manual/api/reference/hanode/get) - retrieving nodes
fa	# نود HA  This class is designed to work with server nodes that are part of a High availability cluster, or a standalone server instance.  Object references:\  -   [High availability node](/manual/api/reference/hanode/object#hanode)  Available methods:\  -   [hanode.get](/manual/api/reference/hanode/get) - retrieving nodes

en-us	# history.clear
fa	#پاک کردن تاریخچه 

en-us	# history.get
fa	# گرفتن تاریخچه 

en-us	# > History object  The following objects are directly related to the `history` API.  ::: noteclassic History objects differ depending on the item's type of information. They are created by the Zabbix server and cannot be modified via the API. :::
fa	# > آبجکت تاریخچه   The following objects are directly related to the `history` API.  ::: noteclassic History objects differ depending on the item's type of information. They are created by the Zabbix server and cannot be modified via the API. :::

en-us	# History  This class is designed to work with history data.  Object references:\  -   [History](/manual/api/reference/history/object#history)  Available methods:\  -   [history.get](/manual/api/reference/history/get) - retrieving     history data.
fa	#تاریخچه  This class is designed to work with history data.  Object references:\  -   [History](/manual/api/reference/history/object#history)  Available methods:\  -   [history.get](/manual/api/reference/history/get) - retrieving     history data.

en-us	# host.create
fa	# ساخت هاست 

en-us	# host.delete
fa	#حذف هاست 

en-us	# host.get
fa	# دریافت هاست 

en-us	##### Host graph tags  |Element|Element property|Required|Type|Range^**[1](#footnotes)**^|Description| |--|--|-|--|----|--------| |graphs| |\-| | |Root element for graphs.| | |name|x|`string`| |Graph name.| | |width|\-|`integer`|20-65535 (default: 900)|Graph width, in pixels. Used for preview and for pie/exploded graphs.| | |height|\-|`integer`|20-65535 (default: 200)|Graph height, in pixels. Used for preview and for pie/exploded graphs.| | |yaxismin|\-|`double`|Default: 0|Value of Y axis minimum.<br><br>Used if 'ymin\_type\_1' is FIXED.| | |yaxismax|\-|`double`|Default: 0|Value of Y axis maximum.<br><br>Used if 'ymax\_type\_1' is FIXED.| | |show\_work\_period|\-|`string`|0 - NO<br>1 - YES (default)|Highlight non-working hours.<br><br>Used by normal and stacked graphs.| | |show\_triggers|\-|`string`|0 - NO<br>1 - YES (default)|Display simple trigger values as a line.<br><br>Used by normal and stacked graphs.| | |type|\-|`string`|0 - NORMAL (default)<br>1 - STACKED<br>2 - PIE<br>3 - EXPLODED|Graph type.| | |show\_legend|\-|`string`|0 - NO<br>1 - YES (default)|Display graph legend.| | |show\_3d|\-|`string`|0 - NO (default)<br>1 - YES|Enable 3D style.<br><br>Used by pie and exploded pie graphs.| | |percent\_left|\-|`double`|Default:0|Show the percentile line for left axis.<br><br>Used only for normal graphs.| | |percent\_right|\-|`double`|Default:0|Show the percentile line for right axis.<br><br>Used only for normal graphs.| | |ymin\_type\_1|\-|`string`|0 - CALCULATED (default)<br>1 - FIXED<br>2 - ITEM|Minimum value of Y axis.<br><br>Used by normal and stacked graphs.| | |ymax\_type\_1|\-|`string`|0 - CALCULATED (default)<br>1 - FIXED<br>2 - ITEM|Maximum value of Y axis.<br><br>Used by normal and stacked graphs.| |ymin\_item\_1| |\-| | |Individual item details.<br><br>Required if 'ymin\_type\_1' is ITEM.| | |host|x|`string`| |Item host.| | |key|x|`string`| |Item key.| |ymax\_item\_1| |\-| | |Individual item details.<br><br>Required if 'ymax\_type\_1' is ITEM.| | |host|x|`string`| |Item host.| | |key|x|`string`| |Item key.| |graph\_items| |x| | |Root element for graph items.| | |sortorder|\-|`integer`| |Draw order. The smaller value is drawn first. Can be used to draw lines or regions behind (or in front of) another.| | |drawtype|\-|`string`|0 - SINGLE\_LINE (default)<br>1 - FILLED\_REGION<br>2 - BOLD\_LINE<br>3 - DOTTED\_LINE<br>4 - DASHED\_LINE<br>5 - GRADIENT\_LINE|Draw style of the graph item.<br><br>Used only by normal graphs.| | |color|\-|`string`| |Element color (6 symbols, hex).| | |yaxisside|\-|`string`|0 - LEFT (default)<br>1 - RIGHT|Side of the graph where the graph item's Y scale will be drawn.<br><br>Used by normal and stacked graphs.| | |calc\_fnc|\-|`string`|1 - MIN<br>2 - AVG (default)<br>4 - MAX<br>7 - ALL (minimum, average and maximum; used only by simple graphs)<br>9 - LAST (used only by pie and exploded pie graphs)|Data to draw if more than one value exists for an item.| | |type|\-|`string`|0 - SIMPLE (default)<br>2 - GRAPH\_SUM (value of the item represents the whole pie; used only by pie and exploded pie graphs)|Graph item type.| |item| |x| | |Individual item.| | |host|x|`string`| |Item host.| | |key|x|`string`| |Item key.|
fa	##### تگ های گراف هاست ها   |Element|Element property|Required|Type|Range^**[1](#footnotes)**^|Description| |--|--|-|--|----|--------| |graphs| |\-| | |Root element for graphs.| | |name|x|`string`| |Graph name.| | |width|\-|`integer`|20-65535 (default: 900)|Graph width, in pixels. Used for preview and for pie/exploded graphs.| | |height|\-|`integer`|20-65535 (default: 200)|Graph height, in pixels. Used for preview and for pie/exploded graphs.| | |yaxismin|\-|`double`|Default: 0|Value of Y axis minimum.<br><br>Used if 'ymin\_type\_1' is FIXED.| | |yaxismax|\-|`double`|Default: 0|Value of Y axis maximum.<br><br>Used if 'ymax\_type\_1' is FIXED.| | |show\_work\_period|\-|`string`|0 - NO<br>1 - YES (default)|Highlight non-working hours.<br><br>Used by normal and stacked graphs.| | |show\_triggers|\-|`string`|0 - NO<br>1 - YES (default)|Display simple trigger values as a line.<br><br>Used by normal and stacked graphs.| | |type|\-|`string`|0 - NORMAL (default)<br>1 - STACKED<br>2 - PIE<br>3 - EXPLODED|Graph type.| | |show\_legend|\-|`string`|0 - NO<br>1 - YES (default)|Display graph legend.| | |show\_3d|\-|`string`|0 - NO (default)<br>1 - YES|Enable 3D style.<br><br>Used by pie and exploded pie graphs.| | |percent\_left|\-|`double`|Default:0|Show the percentile line for left axis.<br><br>Used only for normal graphs.| | |percent\_right|\-|`double`|Default:0|Show the percentile line for right axis.<br><br>Used only for normal graphs.| | |ymin\_type\_1|\-|`string`|0 - CALCULATED (default)<br>1 - FIXED<br>2 - ITEM|Minimum value of Y axis.<br><br>Used by normal and stacked graphs.| | |ymax\_type\_1|\-|`string`|0 - CALCULATED (default)<br>1 - FIXED<br>2 - ITEM|Maximum value of Y axis.<br><br>Used by normal and stacked graphs.| |ymin\_item\_1| |\-| | |Individual item details.<br><br>Required if 'ymin\_type\_1' is ITEM.| | |host|x|`string`| |Item host.| | |key|x|`string`| |Item key.| |ymax\_item\_1| |\-| | |Individual item details.<br><br>Required if 'ymax\_type\_1' is ITEM.| | |host|x|`string`| |Item host.| | |key|x|`string`| |Item key.| |graph\_items| |x| | |Root element for graph items.| | |sortorder|\-|`integer`| |Draw order. The smaller value is drawn first. Can be used to draw lines or regions behind (or in front of) another.| | |drawtype|\-|`string`|0 - SINGLE\_LINE (default)<br>1 - FILLED\_REGION<br>2 - BOLD\_LINE<br>3 - DOTTED\_LINE<br>4 - DASHED\_LINE<br>5 - GRADIENT\_LINE|Draw style of the graph item.<br><br>Used only by normal graphs.| | |color|\-|`string`| |Element color (6 symbols, hex).| | |yaxisside|\-|`string`|0 - LEFT (default)<br>1 - RIGHT|Side of the graph where the graph item's Y scale will be drawn.<br><br>Used by normal and stacked graphs.| | |calc\_fnc|\-|`string`|1 - MIN<br>2 - AVG (default)<br>4 - MAX<br>7 - ALL (minimum, average and maximum; used only by simple graphs)<br>9 - LAST (used only by pie and exploded pie graphs)|Data to draw if more than one value exists for an item.| | |type|\-|`string`|0 - SIMPLE (default)<br>2 - GRAPH\_SUM (value of the item represents the whole pie; used only by pie and exploded pie graphs)|Graph item type.| |item| |x| | |Individual item.| | |host|x|`string`| |Item host.| | |key|x|`string`| |Item key.|

en-us	# hostgroup.create
fa	# ساخت گروه هاست

en-us	# hostgroup.delete
fa	# حذف گروه هاست 

en-us	# hostgroup.get
fa	# دریافت گروه هاستی 

en-us	# hostgroup.massadd
fa	# اضافه کردن گروهی هاست ها 

en-us	# hostgroup.massremove
fa	# حذف گروهی هاست ها 

en-us	# hostgroup.massupdate
fa	# به روز رسانی گروهی هاست ها 

en-us	# > Host group object  The following objects are directly related to the `hostgroup` API.
fa	# > آیجکت گروه هاستی   The following objects are directly related to the `hostgroup` API.

en-us	# hostgroup.update
fa	# به روز رسانی گروه هاستی 

en-us	# hostinterface.create
fa	# ساخت اینترفیس هاست 

en-us	# hostinterface.delete
fa	# حذف اینترفیس هاست 

en-us	# hostinterface.get
fa	# دریافت اینترفیس هاست 

en-us	# hostinterface.massadd
fa	# اضافه کردن گروهی اینترفیس های هاست 

en-us	# hostinterface.massremove
fa	# حذف گروهی اینترفیس های هاست 

en-us	# > Host interface object  The following objects are directly related to the `hostinterface` API.
fa	# >آبجکت های اینترفیس هاست   The following objects are directly related to the `hostinterface` API.

en-us	# hostinterface.replacehostinterfaces
fa	# جایگزینی اینترفیس های هاست 

en-us	# Host interface  This class is designed to work with host interfaces.  Object references:\  -   [Host     interface](/manual/api/reference/hostinterface/object#host_interface)  Available methods:\  -   [hostinterface.create](/manual/api/reference/hostinterface/create) -     creating new host interfaces -   [hostinterface.delete](/manual/api/reference/hostinterface/delete) -     deleting host interfaces -   [hostinterface.get](/manual/api/reference/hostinterface/get) -     retrieving host interfaces -   [hostinterface.massadd](/manual/api/reference/hostinterface/massadd) -     adding host interfaces to hosts -   [hostinterface.massremove](/manual/api/reference/hostinterface/massremove) -     removing host interfaces from hosts -   [hostinterface.replacehostinterfaces](/manual/api/reference/hostinterface/replacehostinterfaces) -     replacing host interfaces on a host -   [hostinterface.update](/manual/api/reference/hostinterface/update) -     updating host interfaces
fa	# اینترفیس هاست   This class is designed to work with host interfaces.  Object references:\  -   [Host     interface](/manual/api/reference/hostinterface/object#host_interface)  Available methods:\  -   [hostinterface.create](/manual/api/reference/hostinterface/create) -     creating new host interfaces -   [hostinterface.delete](/manual/api/reference/hostinterface/delete) -     deleting host interfaces -   [hostinterface.get](/manual/api/reference/hostinterface/get) -     retrieving host interfaces -   [hostinterface.massadd](/manual/api/reference/hostinterface/massadd) -     adding host interfaces to hosts -   [hostinterface.massremove](/manual/api/reference/hostinterface/massremove) -     removing host interfaces from hosts -   [hostinterface.replacehostinterfaces](/manual/api/reference/hostinterface/replacehostinterfaces) -     replacing host interfaces on a host -   [hostinterface.update](/manual/api/reference/hostinterface/update) -     updating host interfaces

en-us	# hostinterface.update
fa	# به روز رسانی اینترفیس هاست ها 

en-us	### Host inventory  The host inventory object has the following properties.  ::: notetip Each property has it's own unique ID number, which is used to associate host inventory fields with items. :::  |ID|Property|[Type](/manual/api/reference_commentary#data_types)|Description|Maximum length| |-|--|-|-----|-----| |4|alias|string|Alias.|128 characters| |11|asset\_tag|string|Asset tag.|64 characters| |28|chassis|string|Chassis.|64 characters| |23|contact|string|Contact person.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |32|contract\_number|string|Contract number.|64 characters| |47|date\_hw\_decomm|string|HW decommissioning date.|64 characters| |46|date\_hw\_expiry|string|HW maintenance expiry date.|64 characters| |45|date\_hw\_install|string|HW installation date.|64 characters| |44|date\_hw\_purchase|string|HW purchase date.|64 characters| |34|deployment\_status|string|Deployment status.|64 characters| |14|hardware|string|Hardware.|255 characters| |15|hardware\_full|string|Detailed hardware.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |39|host\_netmask|string|Host subnet mask.|39 characters| |38|host\_networks|string|Host networks.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |40|host\_router|string|Host router.|39 characters| |30|hw\_arch|string|HW architecture.|32 characters| |33|installer\_name|string|Installer name.|64 characters| |24|location|string|Location.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |25|location\_lat|string|Location latitude.|16 characters| |26|location\_lon|string|Location longitude.|16 characters| |12|macaddress\_a|string|MAC address A.|64 characters| |13|macaddress\_b|string|MAC address B.|64 characters| |29|model|string|Model.|64 characters| |3|name|string|Name.|128 characters| |27|notes|string|Notes.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |41|oob\_ip|string|OOB IP address.|39 characters| |42|oob\_netmask|string|OOB host subnet mask.|39 characters| |43|oob\_router|string|OOB router.|39 characters| |5|os|string|OS name.|128 characters| |6|os\_full|string|Detailed OS name.|255 characters| |7|os\_short|string|Short OS name.|128 characters| |61|poc\_1\_cell|string|Primary POC mobile number.|64 characters| |58|poc\_1\_email|string|Primary email.|128 characters| |57|poc\_1\_name|string|Primary POC name.|128 characters| |63|poc\_1\_notes|string|Primary POC notes.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |59|poc\_1\_phone\_a|string|Primary POC phone A.|64 characters| |60|poc\_1\_phone\_b|string|Primary POC phone B.|64 characters| |62|poc\_1\_screen|string|Primary POC screen name.|64 characters| |68|poc\_2\_cell|string|Secondary POC mobile number.|64 characters| |65|poc\_2\_email|string|Secondary POC email.|128 characters| |64|poc\_2\_name|string|Secondary POC name.|128 characters| |70|poc\_2\_notes|string|Secondary POC notes.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |66|poc\_2\_phone\_a|string|Secondary POC phone A.|64 characters| |67|poc\_2\_phone\_b|string|Secondary POC phone B.|64 characters| |69|poc\_2\_screen|string|Secondary POC screen name.|64 characters| |8|serialno\_a|string|Serial number A.|64 characters| |9|serialno\_b|string|Serial number B.|64 characters| |48|site\_address\_a|string|Site address A.|128 characters| |49|site\_address\_b|string|Site address B.|128 characters| |50|site\_address\_c|string|Site address C.|128 characters| |51|site\_city|string|Site city.|128 characters| |53|site\_country|string|Site country.|64 characters| |56|site\_notes|string|Site notes.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |55|site\_rack|string|Site rack location.|128 characters| |52|site\_state|string|Site state.|64 characters| |54|site\_zip|string|Site ZIP/postal code.|64 characters| |16|software|string|Software.|255 characters| |18|software\_app\_a|string|Software application A.|64 characters| |19|software\_app\_b|string|Software application B.|64 characters| |20|software\_app\_c|string|Software application C.|64 characters| |21|software\_app\_d|string|Software application D.|64 characters| |22|software\_app\_e|string|Software application E.|64 characters| |17|software\_full|string|Software details.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |10|tag|string|Tag.|64 characters| |1|type|string|Type.|64 characters| |2|type\_full|string|Type details.|64 characters| |35|url\_a|string|URL A.|255 characters| |36|url\_b|string|URL B.|255 characters| |37|url\_c|string|URL C.|255 characters| |31|vendor|string|Vendor.|64 characters|
fa	### جست و جو هاست   The host inventory object has the following properties.  ::: notetip Each property has it's own unique ID number, which is used to associate host inventory fields with items. :::  |ID|Property|[Type](/manual/api/reference_commentary#data_types)|Description|Maximum length| |-|--|-|-----|-----| |4|alias|string|Alias.|128 characters| |11|asset\_tag|string|Asset tag.|64 characters| |28|chassis|string|Chassis.|64 characters| |23|contact|string|Contact person.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |32|contract\_number|string|Contract number.|64 characters| |47|date\_hw\_decomm|string|HW decommissioning date.|64 characters| |46|date\_hw\_expiry|string|HW maintenance expiry date.|64 characters| |45|date\_hw\_install|string|HW installation date.|64 characters| |44|date\_hw\_purchase|string|HW purchase date.|64 characters| |34|deployment\_status|string|Deployment status.|64 characters| |14|hardware|string|Hardware.|255 characters| |15|hardware\_full|string|Detailed hardware.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |39|host\_netmask|string|Host subnet mask.|39 characters| |38|host\_networks|string|Host networks.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |40|host\_router|string|Host router.|39 characters| |30|hw\_arch|string|HW architecture.|32 characters| |33|installer\_name|string|Installer name.|64 characters| |24|location|string|Location.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |25|location\_lat|string|Location latitude.|16 characters| |26|location\_lon|string|Location longitude.|16 characters| |12|macaddress\_a|string|MAC address A.|64 characters| |13|macaddress\_b|string|MAC address B.|64 characters| |29|model|string|Model.|64 characters| |3|name|string|Name.|128 characters| |27|notes|string|Notes.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |41|oob\_ip|string|OOB IP address.|39 characters| |42|oob\_netmask|string|OOB host subnet mask.|39 characters| |43|oob\_router|string|OOB router.|39 characters| |5|os|string|OS name.|128 characters| |6|os\_full|string|Detailed OS name.|255 characters| |7|os\_short|string|Short OS name.|128 characters| |61|poc\_1\_cell|string|Primary POC mobile number.|64 characters| |58|poc\_1\_email|string|Primary email.|128 characters| |57|poc\_1\_name|string|Primary POC name.|128 characters| |63|poc\_1\_notes|string|Primary POC notes.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |59|poc\_1\_phone\_a|string|Primary POC phone A.|64 characters| |60|poc\_1\_phone\_b|string|Primary POC phone B.|64 characters| |62|poc\_1\_screen|string|Primary POC screen name.|64 characters| |68|poc\_2\_cell|string|Secondary POC mobile number.|64 characters| |65|poc\_2\_email|string|Secondary POC email.|128 characters| |64|poc\_2\_name|string|Secondary POC name.|128 characters| |70|poc\_2\_notes|string|Secondary POC notes.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |66|poc\_2\_phone\_a|string|Secondary POC phone A.|64 characters| |67|poc\_2\_phone\_b|string|Secondary POC phone B.|64 characters| |69|poc\_2\_screen|string|Secondary POC screen name.|64 characters| |8|serialno\_a|string|Serial number A.|64 characters| |9|serialno\_b|string|Serial number B.|64 characters| |48|site\_address\_a|string|Site address A.|128 characters| |49|site\_address\_b|string|Site address B.|128 characters| |50|site\_address\_c|string|Site address C.|128 characters| |51|site\_city|string|Site city.|128 characters| |53|site\_country|string|Site country.|64 characters| |56|site\_notes|string|Site notes.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |55|site\_rack|string|Site rack location.|128 characters| |52|site\_state|string|Site state.|64 characters| |54|site\_zip|string|Site ZIP/postal code.|64 characters| |16|software|string|Software.|255 characters| |18|software\_app\_a|string|Software application A.|64 characters| |19|software\_app\_b|string|Software application B.|64 characters| |20|software\_app\_c|string|Software application C.|64 characters| |21|software\_app\_d|string|Software application D.|64 characters| |22|software\_app\_e|string|Software application E.|64 characters| |17|software\_full|string|Software details.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |10|tag|string|Tag.|64 characters| |1|type|string|Type.|64 characters| |2|type\_full|string|Type details.|64 characters| |35|url\_a|string|URL A.|255 characters| |36|url\_b|string|URL B.|255 characters| |37|url\_c|string|URL C.|255 characters| |31|vendor|string|Vendor.|64 characters|

en-us	##### Host low-level discovery rule tags  |Element|Element property|Required|Type|Range^**[1](#footnotes)**^|Description| |--|--|-|--|----|--------| |discovery\_rules| |\-| | |Root element for low-level discovery rules.| | |*For most of the element tag values, see element tag values for a regular item. Only the tags that are specific to low-level discovery rules, are described below.*| | | | | | |type|\-|`string`|0 - ZABBIX\_PASSIVE (default)<br>2 - TRAP<br>3 - SIMPLE<br>5 - INTERNAL<br>7 - ZABBIX\_ACTIVE<br>10 - EXTERNAL<br>11 - ODBC<br>12 - IPMI<br>13 - SSH<br>14 - TELNET<br>16 - JMX<br>18 - DEPENDENT<br>19 - HTTP\_AGENT<br>20 - SNMP\_AGENT|Item type.| | |lifetime|\-|`string`|Default: 30d|Time period after which items that are no longer discovered will be deleted. Seconds, time unit with suffix or user macro.| |filter| | | | |Individual filter.| | |evaltype|\-|`string`|0 - AND\_OR (default)<br>1 - AND<br>2 - OR<br>3 - FORMULA|Logic to use for checking low-level discovery rule filter conditions.| | |formula|\-|`string`| |Custom calculation formula for filter conditions.| |conditions| |\-| | |Root element for filter conditions.| | |macro|x|`string`| |Low-level discovery macro name.| | |value|\-|`string`| |Filter value: regular expression or global regular expression.| | |operator|\-|`string`|8 - MATCHES\_REGEX (default)<br>9 - NOT\_MATCHES\_REGEX|Condition operator.| | |formulaid|x|`character`| |Arbitrary unique ID that is used to reference a condition from the custom expression. Can only contain capital-case letters. The ID must be defined by the user when modifying filter conditions, but will be generated anew when requesting them afterward.| |lld\_macro\_paths| |\-| | |Root element for LLD macro paths.| | |lld\_macro|x|`string`| |Low-level discovery macro name.| | |path|x|`string`| |Selector for value which will be assigned to the corresponding macro.| |preprocessing| |\-| | |LLD rule value preprocessing.| |step| |\-| | |Individual LLD rule value preprocessing step.| | |*For most of the element tag values, see element tag values for a host item value preprocessing. Only the tags that are specific to low-level discovery value preprocessing, are described below.*| | | | | | |type|x|`string`|5 - REGEX<br>11 - XMLPATH<br>12 - JSONPATH<br>15 - NOT\_MATCHES\_REGEX<br>16 - CHECK\_JSON\_ERROR<br>17 - CHECK\_XML\_ERROR<br>20 - DISCARD\_UNCHANGED\_HEARTBEAT<br>21 - JAVASCRIPT<br>23 - PROMETHEUS\_TO\_JSON<br>24 - CSV\_TO\_JSON<br>25 - STR\_REPLACE<br>27 - XML\_TO\_JSON|Type of the item value preprocessing step.| |trigger\_prototypes| |\-| | |Root element for trigger prototypes.| | |*For trigger prototype element tag values, see regular [host trigger](/manual/xml_export_import/hosts#host_trigger_tags) tags.*| | | | | |graph\_prototypes| |\-| | |Root element for graph prototypes.| | |*For graph prototype element tag values, see regular [host graph](/manual/xml_export_import/hosts#host_graph_tags) tags.*| | | | | |host\_prototypes| |\-| | |Root element for host prototypes.| | |*For host prototype element tag values, see regular [host](/manual/xml_export_import/hosts#host_tags) tags.*| | | | | |item\_prototypes| |\-| | |Root element for item prototypes.| | |*For item prototype element tag values, see regular [host item](/manual/xml_export_import/hosts#host_item_tags) tags.*| | | | | |master\_item| |\-| | |Individual item prototype master item/item prototype data.| | |key|x|`string`| |Dependent item prototype master item/item prototype key value.<br><br>Required for a dependent item.|
fa	##### تگ های قوانین LLD هاست ها   |Element|Element property|Required|Type|Range^**[1](#footnotes)**^|Description| |--|--|-|--|----|--------| |discovery\_rules| |\-| | |Root element for low-level discovery rules.| | |*For most of the element tag values, see element tag values for a regular item. Only the tags that are specific to low-level discovery rules, are described below.*| | | | | | |type|\-|`string`|0 - ZABBIX\_PASSIVE (default)<br>2 - TRAP<br>3 - SIMPLE<br>5 - INTERNAL<br>7 - ZABBIX\_ACTIVE<br>10 - EXTERNAL<br>11 - ODBC<br>12 - IPMI<br>13 - SSH<br>14 - TELNET<br>16 - JMX<br>18 - DEPENDENT<br>19 - HTTP\_AGENT<br>20 - SNMP\_AGENT|Item type.| | |lifetime|\-|`string`|Default: 30d|Time period after which items that are no longer discovered will be deleted. Seconds, time unit with suffix or user macro.| |filter| | | | |Individual filter.| | |evaltype|\-|`string`|0 - AND\_OR (default)<br>1 - AND<br>2 - OR<br>3 - FORMULA|Logic to use for checking low-level discovery rule filter conditions.| | |formula|\-|`string`| |Custom calculation formula for filter conditions.| |conditions| |\-| | |Root element for filter conditions.| | |macro|x|`string`| |Low-level discovery macro name.| | |value|\-|`string`| |Filter value: regular expression or global regular expression.| | |operator|\-|`string`|8 - MATCHES\_REGEX (default)<br>9 - NOT\_MATCHES\_REGEX|Condition operator.| | |formulaid|x|`character`| |Arbitrary unique ID that is used to reference a condition from the custom expression. Can only contain capital-case letters. The ID must be defined by the user when modifying filter conditions, but will be generated anew when requesting them afterward.| |lld\_macro\_paths| |\-| | |Root element for LLD macro paths.| | |lld\_macro|x|`string`| |Low-level discovery macro name.| | |path|x|`string`| |Selector for value which will be assigned to the corresponding macro.| |preprocessing| |\-| | |LLD rule value preprocessing.| |step| |\-| | |Individual LLD rule value preprocessing step.| | |*For most of the element tag values, see element tag values for a host item value preprocessing. Only the tags that are specific to low-level discovery value preprocessing, are described below.*| | | | | | |type|x|`string`|5 - REGEX<br>11 - XMLPATH<br>12 - JSONPATH<br>15 - NOT\_MATCHES\_REGEX<br>16 - CHECK\_JSON\_ERROR<br>17 - CHECK\_XML\_ERROR<br>20 - DISCARD\_UNCHANGED\_HEARTBEAT<br>21 - JAVASCRIPT<br>23 - PROMETHEUS\_TO\_JSON<br>24 - CSV\_TO\_JSON<br>25 - STR\_REPLACE<br>27 - XML\_TO\_JSON|Type of the item value preprocessing step.| |trigger\_prototypes| |\-| | |Root element for trigger prototypes.| | |*For trigger prototype element tag values, see regular [host trigger](/manual/xml_export_import/hosts#host_trigger_tags) tags.*| | | | | |graph\_prototypes| |\-| | |Root element for graph prototypes.| | |*For graph prototype element tag values, see regular [host graph](/manual/xml_export_import/hosts#host_graph_tags) tags.*| | | | | |host\_prototypes| |\-| | |Root element for host prototypes.| | |*For host prototype element tag values, see regular [host](/manual/xml_export_import/hosts#host_tags) tags.*| | | | | |item\_prototypes| |\-| | |Root element for item prototypes.| | |*For item prototype element tag values, see regular [host item](/manual/xml_export_import/hosts#host_item_tags) tags.*| | | | | |master\_item| |\-| | |Individual item prototype master item/item prototype data.| | |key|x|`string`| |Dependent item prototype master item/item prototype key value.<br><br>Required for a dependent item.|

en-us	# host.massadd
fa	# اضافه کردن گروهی هاست ها 

en-us	# host.massremove
fa	# حذف گروهی هاست ها 

en-us	# host.massupdate
fa	# آپدیت گروهی هاست ها 

en-us	# > Host object  The following objects are directly related to the host API.
fa	# > آبجکت هاست  The following objects are directly related to the host API.

en-us	# hostprototype.create
fa	# ساخت هاست نمونه

en-us	# hostprototype.delete
fa	#حذف نمونه اولیه هاست 

en-us	# hostprototype.get
fa	# دریافت نمونه اولیه هاست 

en-us	# > Host prototype object  The following objects are directly related to the `hostprototype` API.
fa	# > آبجکت نمونه اولیه هاست   The following objects are directly related to the `hostprototype` API.

en-us	# Host prototype  This class is designed to work with host prototypes.  Object references:\  -   [Host     prototype](/manual/api/reference/hostprototype/object#host_prototype) -   [Host prototype     inventory](/manual/api/reference/hostprototype/object#host_prototype_inventory) -   [Group link](/manual/api/reference/hostprototype/object#group_link) -   [Group     prototype](/manual/api/reference/hostprototype/object#group_prototype)  Available methods:\  -   [hostprototype.create](/manual/api/reference/hostprototype/create) -     creating new host prototypes -   [hostprototype.delete](/manual/api/reference/hostprototype/delete) -     deleting host prototypes -   [hostprototype.get](/manual/api/reference/hostprototype/get) -     retrieving host prototypes -   [hostprototype.update](/manual/api/reference/hostprototype/update) -     updating host prototypes
fa	# نمونه اولیه هاست   This class is designed to work with host prototypes.  Object references:\  -   [Host     prototype](/manual/api/reference/hostprototype/object#host_prototype) -   [Host prototype     inventory](/manual/api/reference/hostprototype/object#host_prototype_inventory) -   [Group link](/manual/api/reference/hostprototype/object#group_link) -   [Group     prototype](/manual/api/reference/hostprototype/object#group_prototype)  Available methods:\  -   [hostprototype.create](/manual/api/reference/hostprototype/create) -     creating new host prototypes -   [hostprototype.delete](/manual/api/reference/hostprototype/delete) -     deleting host prototypes -   [hostprototype.get](/manual/api/reference/hostprototype/get) -     retrieving host prototypes -   [hostprototype.update](/manual/api/reference/hostprototype/update) -     updating host prototypes

en-us	# hostprototype.update
fa	# به روز رسانی نمونه اولیه هاست 

en-us	# Host  This class is designed to work with hosts.  Object references:\  -   [Host](/manual/api/reference/host/object#host) -   [Host inventory](/manual/api/reference/host/object#host_inventory)  Available methods:\  -   [host.create](/manual/api/reference/host/create) - creating new     hosts -   [host.delete](/manual/api/reference/host/delete) - deleting hosts -   [host.get](/manual/api/reference/host/get) - retrieving hosts -   [host.massadd](/manual/api/reference/host/massadd) - adding related     objects to hosts -   [host.massremove](/manual/api/reference/host/massremove) - removing     related objects from hosts -   [host.massupdate](/manual/api/reference/host/massupdate) - replacing     or removing related objects from hosts -   [host.update](/manual/api/reference/host/update) - updating hosts
fa	# هاست  This class is designed to work with hosts.  Object references:\  -   [Host](/manual/api/reference/host/object#host) -   [Host inventory](/manual/api/reference/host/object#host_inventory)  Available methods:\  -   [host.create](/manual/api/reference/host/create) - creating new     hosts -   [host.delete](/manual/api/reference/host/delete) - deleting hosts -   [host.get](/manual/api/reference/host/get) - retrieving hosts -   [host.massadd](/manual/api/reference/host/massadd) - adding related     objects to hosts -   [host.massremove](/manual/api/reference/host/massremove) - removing     related objects from hosts -   [host.massupdate](/manual/api/reference/host/massupdate) - replacing     or removing related objects from hosts -   [host.update](/manual/api/reference/host/update) - updating hosts

en-us	# host.update
fa	# آپدیت هاست 

en-us	# housekeeping.get
fa	# دریافت اطلاعات ذخیره شده 

en-us	# > Housekeeping object  The following objects are directly related to the `housekeeping` API.
fa	# > آبجکت نگهداری داده ها   The following objects are directly related to the `housekeeping` API.

en-us	# Housekeeping  This class is designed to work with housekeeping.  Object references:\  -   [Housekeeping](/manual/api/reference/housekeeping/object#housekeeping)  Available methods:\  -   [housekeeping.get](/manual/api/reference/housekeeping/get) -     retrieve housekeeping -   [housekeeping.update](/manual/api/reference/housekeeping/update) -     update housekeeping
fa	# ذخیره سازی  This class is designed to work with housekeeping.  Object references:\  -   [Housekeeping](/manual/api/reference/housekeeping/object#housekeeping)  Available methods:\  -   [housekeeping.get](/manual/api/reference/housekeeping/get) -     retrieve housekeeping -   [housekeeping.update](/manual/api/reference/housekeeping/update) -     update housekeeping

en-us	# housekeeping.update
fa	# آپدیت ذخیره سازی داده 

en-us	# httptest.create
fa	# ساخت Http تست

en-us	# httptest.delete
fa	# حذف Http تست 

en-us	# httptest.get
fa	# دریافت Http تست 

en-us	# httptest.update
fa	# به روز رسانی http

en-us	# iconmap.create
fa	# ساخت آیکون مپ 

en-us	# iconmap.delete
fa	# حذف آیکون مپ 

en-us	# iconmap.get
fa	# دریافت آیکون مپ 

en-us	# > Icon map object  The following objects are directly related to the `iconmap` API.
fa	# >آبجکت مپ ایکون  The following objects are directly related to the `iconmap` API.

en-us	# Icon map  This class is designed to work with icon maps.  Object references:\  -   [Icon map](/manual/api/reference/iconmap/object#icon_map) -   [Icon mapping](/manual/api/reference/iconmap/object#icon_mapping)  Available methods:\  -   [iconmap.create](/manual/api/reference/iconmap/create) - create new     icon maps -   [iconmap.delete](/manual/api/reference/iconmap/delete) - delete icon     maps -   [iconmap.get](/manual/api/reference/iconmap/get) - retrieve icon     maps -   [iconmap.update](/manual/api/reference/iconmap/update) - update icon     maps
fa	# آیکون مپ  This class is designed to work with icon maps.  Object references:\  -   [Icon map](/manual/api/reference/iconmap/object#icon_map) -   [Icon mapping](/manual/api/reference/iconmap/object#icon_mapping)  Available methods:\  -   [iconmap.create](/manual/api/reference/iconmap/create) - create new     icon maps -   [iconmap.delete](/manual/api/reference/iconmap/delete) - delete icon     maps -   [iconmap.get](/manual/api/reference/iconmap/get) - retrieve icon     maps -   [iconmap.update](/manual/api/reference/iconmap/update) - update icon     maps

en-us	# iconmap.update
fa	#دکمه آپدیت نقشه 

en-us	# image.create
fa	#ساخت Image

en-us	#### Installing locales  To list all installed languages, run:      locale -a  If some languages that are needed are not listed, open the */etc/locale.gen* file and uncomment the required locales. Since Zabbix uses UTF-8 encoding, you need to select locales with UTF-8 charset.  Now run:      locale-gen   Restart the web server.  The locales should now be installed. It may be required to reload Zabbix frontend page in browser using Ctrl + F5 for new languages to appear.
fa	#### Installing locales  To list all installed languages, run:      locale -a  If some languages that are needed are not listed, open the */etc/locale.gen* file and uncomment the required locales. Since Zabbix uses UTF-8 encoding, you need to select locales with UTF-8 charset.  Now, run:      locale-gen   Restart the web server.  The locales should now be installed. It may be required to reload Zabbix frontend page in browser using Ctrl + F5 for new languages to appear.

en-us	### Integer history  The integer history object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |clock|timestamp|Time when that value was received.| |itemid|string|ID of the related item.| |ns|integer|Nanoseconds when the value was received.| |value|integer|Received value.|
fa	### تاریخچه عدد صحیح   The integer history object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |clock|timestamp|Time when that value was received.| |itemid|string|ID of the related item.| |ns|integer|Nanoseconds when the value was received.| |value|integer|Received value.|

en-us	# > LLD rule object  The following objects are directly related to the `discoveryrule` API.
fa	# > آبجکت قانون LLD  The following objects are directly related to the `discoveryrule` API.

en-us	# LLD rule  This class is designed to work with low level discovery rules.  Object references:\  -   [LLD rule](/manual/api/reference/discoveryrule/object#lld_rule)  Available methods:\  -   [discoveryrule.copy](/manual/api/reference/discoveryrule/copy) -     copying LLD rules -   [discoveryrule.create](/manual/api/reference/discoveryrule/create) -     creating new LLD rules -   [discoveryrule.delete](/manual/api/reference/discoveryrule/delete) -     deleting LLD rules -   [discoveryrule.get](/manual/api/reference/discoveryrule/get) -     retrieving LLD rules -   [discoveryrule.update](/manual/api/reference/discoveryrule/update) -     updating LLD rules
fa	# قانون LLD   This class is designed to work with low level discovery rules.  Object references:\  -   [LLD rule](/manual/api/reference/discoveryrule/object#lld_rule)  Available methods:\  -   [discoveryrule.copy](/manual/api/reference/discoveryrule/copy) -     copying LLD rules -   [discoveryrule.create](/manual/api/reference/discoveryrule/create) -     creating new LLD rules -   [discoveryrule.delete](/manual/api/reference/discoveryrule/delete) -     deleting LLD rules -   [discoveryrule.get](/manual/api/reference/discoveryrule/get) -     retrieving LLD rules -   [discoveryrule.update](/manual/api/reference/discoveryrule/update) -     updating LLD rules

en-us	### Log history  The log history object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |id|string|ID of the history entry.| |clock|timestamp|Time when that value was received.| |itemid|string|ID of the related item.| |logeventid|integer|Windows event log entry ID.| |ns|integer|Nanoseconds when the value was received.| |severity|integer|Windows event log entry level.| |source|string|Windows event log entry source.| |timestamp|timestamp|Windows event log entry time.| |value|text|Received value.|
fa	### تاریخچه لاگ  The log history object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |id|string|ID of the history entry.| |clock|timestamp|Time when that value was received.| |itemid|string|ID of the related item.| |logeventid|integer|Windows event log entry ID.| |ns|integer|Nanoseconds when the value was received.| |severity|integer|Windows event log entry level.| |source|string|Windows event log entry source.| |timestamp|timestamp|Windows event log entry time.| |value|text|Received value.|

en-us	###      Log level control targets     *process-type*   All processes of specified type (active checks, collector, listener)     *process-type,N*   Process type and number (e.g., listener,3)     *pid*   Process identifier, up to 65535. For larger values specify target as "process-type,N"  ```{=html} <!-- --> ``` **-p**, **--print**   Print known items and exit. For each item either generic defaults are used, or specific defaults for testing are supplied. These defaults are listed in square brackets as item key parameters. Returned values are enclosed in square brackets and prefixed with the type of the returned value, separated by a pipe character. For user parameters type is always **t**, as the agent can not determine all possible return values. Items, displayed as working, are not guaranteed to work from the Zabbix server or zabbix\_get when querying a running agent daemon as permissions or environment may be different. Returned value types are:     d   Number with a decimal part.     m   Not supported. This could be caused by querying an item that only works in the active mode like a log monitoring item or an item that requires multiple collected values. Permission issues or incorrect user parameters could also result in the not supported state.     s   Text. Maximum length not limited.     t   Text. Same as **s**.     u   Unsigned integer.  **-t**, **--test** *item-key*   Test single item and exit. See **--print** for output description.  **-h**, **--help**   Display this help and exit.  **-V**, **--version**   Output version information and exit.  [ ]{#lbAH}
fa	###     اهداف کنترل سطح ورود به سیستم     *نوع فرآیند* همه فرآیندهای از نوع مشخص شده (چک‌های فعال، جمع‌آور، شنونده)     *نوع فرآیند، N* نوع و تعداد فرآیند (به عنوان مثال، شنونده، 3)     *پید* شناسه فرآیند، تا 65535. برای مقادیر بزرگتر، هدف را به عنوان مشخص کنید "نوع فرآیند، N"  ```{=html} <!---> ``` **-p**، **--چاپ** موارد شناخته شده را چاپ کنید و خارج شوید. برای هر مورد یکی از پیش فرض های عمومی است استفاده می شود، یا پیش فرض های خاصی برای آزمایش ارائه شده است. این پیش فرض ها هستند در پرانتز به عنوان پارامترهای کلیدی آیتم فهرست شده است. مقادیر برگشتی هستند محصور در پرانتز مربع و پیشوند با نوع بازگشتی مقدار، با یک کاراکتر لوله جدا شده است. برای پارامترهای کاربر نوع همیشه است **t**، زیرا عامل نمی تواند تمام مقادیر بازگشتی ممکن را تعیین کند. موارد، نمایش داده شده به عنوان کار، تضمین نمی شود که از سرور Zabbix کار کند یا zabbix\_get در هنگام پرس و جو از یک daemon عامل در حال اجرا به عنوان مجوز یا محیط ممکن است متفاوت باشد انواع ارزش برگشتی عبارتند از:     د عدد با قسمت اعشاری.     متر پشتیبانی نشده. این ممکن است به دلیل پرس و جو از موردی باشد که فقط کار می کند در حالت فعال مانند یک آیتم نظارت بر گزارش یا موردی که نیاز دارد چندین مقادیر جمع آوری شده مشکلات مجوز یا کاربر نادرست پارامترها همچنین می توانند منجر به حالت پشتیبانی نشده شوند.     س متن حداکثر طول محدود نیست.     تی متن همان **s**.     تو عدد صحیح بدون علامت  **-t**، **--تست** *کلید مورد* یک مورد را تست کنید و از آن خارج شوید. برای توضیحات خروجی **--print** را ببینید.  **-h**، **--راهنما** این راهنما را نمایش دهید و از آن خارج شوید.  **-V**، **--نسخه** اطلاعات نسخه خروجی و خروج.  [ ]{#lbAH}

en-us	##### Mass editing options  Buttons below the list offer some mass-editing options:  -   *Enable* - change trigger status to *Enabled*. -   *Disable* - change trigger status to *Disabled*. -   *Copy* - copy the triggers to other hosts or templates. -   *Mass update* - update several properties for a number of triggers     at once. -   *Delete* - delete the triggers.  To use these options, mark the checkboxes before the respective triggers, then click on the required button.
fa	##### Mass editing options  Buttons below the list offer some mass-editing options:  -   *Enable* - change trigger status to *Enabled* -   *Disable* - change trigger status to *Disabled* -   *Copy* - copy the triggers to other hosts or templates -   *Mass update* - update several properties for a number of triggers     at once -   *Delete* - delete the triggers  To use these options, mark the checkboxes before the respective triggers, then click on the required button.

en-us	##### - Modes  (**forecast** only)\ Every time a trigger function is evaluated, it gets data from the specified history period and fits a specified function to the data. So, if the data is slightly different, the fitted function will be slightly different. If we simply calculate the value of the fitted function at a specified time in the future, you will know nothing about how the analyzed item is expected to behave between now and that moment in the future. For some `fit` options (like *polynomial*) a simple value from the future may be misleading.  |`mode`|**forecast** result| |------|-------------------| |*value*|f(now + `time`)| |*max*|max~now\ <=\ t\ <=\ now\ +\ `time`~ f(t)| |*min*|min~now\ <=\ t\ <=\ now\ +\ `time`~ f(t)| |*delta*|*max* - *min*| |*avg*|average of f(t) (now <= t <= now + `time`) according to [definition](https://en.wikipedia.org/wiki/Mean_of_a_function)|
fa	##### - Modes  (**forecast** only)\ Every time a trigger function is evaluated it gets data from the specified history period and fits a specified function to the data. So, if the data is slightly different the fitted function will be slightly different. If we simply calculate the value of the fitted function at a specified time in the future you will know nothing about how the analyzed item is expected to behave between now and that moment in the future. For some `fit` options (like *polynomial*) a simple value from the future may be misleading.  |`mode`|**forecast** result| |------|-------------------| |*value*|f(now + `time`)| |*max*|max~now\ <=\ t\ <=\ now\ +\ `time`~ f(t)| |*min*|min~now\ <=\ t\ <=\ now\ +\ `time`~ f(t)| |*delta*|*max* - *min*| |*avg*|average of f(t) (now <= t <= now + `time`) according to [definition](https://en.wikipedia.org/wiki/Mean_of_a_function)|

en-us	## NAME  zabbix\_agent2 - Zabbix agent 2\ \ [ ]{#lbAC}
fa	## نام  zabbix\_agent2 - Zabbix agent 2\ \ [ ]{#lbAC}

en-us	## NAME  zabbix\_agentd - Zabbix agent daemon [ ]{#lbAC}
fa	ایجنت زبیکس -سرویس ایجنت زبیکس

en-us	## NAME  zabbix\_get - Zabbix get utility [ ]{#lbAC}
fa	## نام دستور  zabbix\_get - ابزار دریافت مقادیر Zabbix [ ]{#lbAC}

en-us	## NAME  zabbix\_js - Zabbix JS utility [ ]{#lbAC}
fa	## نام  zabbix\_js - ابزار Zabbix JS [ ]{#lbAC}

en-us	## NAME  zabbix\_proxy - Zabbix proxy daemon [ ]{#lbAC}
fa	## نام  zabbix\_js - ابزار Zabbix JS [ ]{#lbAC}

en-us	## NAME  zabbix\_sender - Zabbix sender utility [ ]{#lbAC}
fa	## نام  zabbix\_sender - ابزار ارسال کننده Zabbix [ ]{#lbAC}

en-us	## NAME  zabbix\_server - Zabbix server daemon [ ]{#lbAC}
fa	## نام  zabbix\_server - دیمون سرور Zabbix [ ]{#lbAC}

en-us	## NAME  zabbix\_web\_service - Zabbix web service [ ]{#lbAC}
fa	## نام  zabbix\_web\_service - وب سرویس Zabbix [ ]{#lbAC}

en-us	### Notation
fa	### نشانه گذاری

en-us	## OPTIONS  **-c**, **--config** *config-file*   Use the alternate *config-file* instead of the default one.  **-f**, **--foreground**   Run Zabbix agent in foreground.  **-R**, **--runtime-control** *runtime-option*   Perform administrative functions according to *runtime-option*.  [ ]{#lbAF}
fa	## گزینه ها  **-c**، **--config** *config-file* به جای فایل پیش فرض، از *config-file* جایگزین استفاده کنید.  **-R**، **--runtime-control** *runtime-option* عملکردهای اداری را مطابق *runtime-option* انجام دهید.

en-us	## OPTIONS  **-c**, **--config** *config-file*   Use the alternate *config-file* instead of the default one.  **-f**, **--foreground**   Run Zabbix proxy in foreground.  **-R**, **--runtime-control** *runtime-option*   Perform administrative functions according to *runtime-option*.  [ ]{#lbAF}
fa	## گزینه ها  **-c**، **--config** *config-file* به جای فایل پیش فرض، از *config-file* جایگزین استفاده کنید.  **-R**، **--runtime-control** *runtime-option* عملکردهای اداری را مطابق *runtime-option* انجام دهید.

en-us	## OPTIONS  **-c**, **--config** *config-file*   Use the alternate *config-file* instead of the default one.  **-h**, **--help**   Display this help and exit.  **-V**, **--version**   Output version information and exit.  [ ]{#lbAF}
fa	## گزینه ها  **-c**، **--config** *config-file* به جای فایل پیش فرض، از *config-file* جایگزین استفاده کنید.  **-h**، **--راهنما** این راهنما را نمایش دهید و از آن خارج شوید.  **-V**، **--نسخه** اطلاعات نسخه خروجی و خروج.  [ ]{#lbAF}

en-us	## OPTIONS  **-c**, **--config** *config-file*   Use the alternate *config-file* instead of the default one.  **-R**, **--runtime-control** *runtime-option*   Perform administrative functions according to *runtime-option*.
fa	## گزینه ها  **-c**، **--config** *config-file* به جای فایل پیش فرض، از *config-file* جایگزین استفاده کنید.  **-R**، **--runtime-control** *runtime-option* عملکردهای اداری را مطابق *runtime-option* انجام دهید.

en-us	 #### Options  |Parameter|Description| |---------|-----------| |-V --version|Print the plugin version and license information.| |-h --help|Print help information (shorthand).|
fa	#### Options  |Parameter|Description| |---------|-----------| |-V --version|Print the plugin version and license information.| |-h --help|Print help information (shorthand).|

en-us	## OPTIONS  **-s**, **--host** *host-name-or-IP*   Specify host name or IP address of a host.  **-p**, **--port** *port-number*   Specify port number of agent running on the host. Default is 10050.  **-I**, **--source-address** *IP-address*   Specify source IP address.  **-t**, **--timeout** *seconds*   Specify timeout. Valid range: 1-30 seconds (default: 30)  **-k**, **--key** *item-key*   Specify key of item to retrieve value for.  **--tls-connect** *value*   How to connect to agent. Values:  [ ]{#lbAF}
fa	## گزینه ها  **-s**، **--host** *host-name-or-IP* نام میزبان یا آدرس IP یک میزبان را مشخص کنید.  **-p**، **--پورت** *درگاه-شماره* شماره پورت عامل در حال اجرا بر روی هاست را مشخص کنید. پیش فرض 10050 است.  **-I**، **--منبع-آدرس** *آدرس IP* آدرس IP منبع را مشخص کنید.  **-t**، **--تایم اوت** *ثانیه* تایم اوت را مشخص کنید. محدوده معتبر: 1-30 ثانیه (پیش‌فرض: 30)  **-k**، **--کلید** *کلید مورد* کلید مورد را برای بازیابی مقدار مشخص کنید.  **--tls-connect** *value* نحوه اتصال به نماینده ارزش های:  [ ]{#lbAF}

en-us	## OPTIONS  **-s**, **--script** *script-file*   Specify the file name of the script to execute. If '-' is specified as file name, the script will be read from stdin.  **-p**, **--param** *input-param*   Specify the input parameter.  **-i**, **--input** *input-file*   Specify the file name of the input parameter. If '-' is specified as file name, the input will be read from stdin.  **-l**, **--loglevel** *log-level*   Specify the log level.  **-t**, **--timeout** *timeout*   Specify the timeout in seconds. Valid range: 1\-60 seconds (default: 10)  **-h**, **--help**   Display this help and exit.  **-V**, **--version**   Output version information and exit.  [ ]{#lbAF}
fa	## گزینه ها   **-s**، **--اسکریپت** *اسکریپت-فایل* نام فایل اسکریپت مورد نظر را برای اجرا مشخص کنید. اگر '-' به صورت مشخص شده باشد نام فایل، اسکریپت از stdin خوانده می شود.  **-p**، **--param** *input-param* پارامتر ورودی را مشخص کنید.  **-i**، **--ورودی** *ورودی-فایل* نام فایل پارامتر ورودی را مشخص کنید. اگر '-' به صورت مشخص شده باشد نام فایل، ورودی از stdin خوانده می شود.  **-l**، **--loglevel** *log-level* سطح گزارش را مشخص کنید.  **-t**، **--تایم اوت** *تایم اوت* تایم اوت را بر حسب ثانیه مشخص کنید.  **-h**، **--راهنما** این راهنما را نمایش دهید و از آن خارج شوید.  **-V**، **--نسخه** اطلاعات نسخه خروجی و خروج.  [ ]{#lbAF}

en-us	 ### Overview   In Zabbix 6.0, [service monitoring](/manual/it_services) functionality has been reworked significantly (see [What's new in Zabbix 6.0.0](https://www.zabbix.com/documentation/6.0/en/manual/introduction/whatsnew600#services) for the list of changes).   This page describes how services and SLAs, defined in earlier Zabbix versions, are changed during an upgrade to Zabbix 6.0 or newer.
fa	 ### Overview   In Zabbix 6.0, [service monitoring](/manual/it_services) functionality has been reworked significantly (see [What's new in Zabbix 6.0.0](https://www.zabbix.com/documentation/6.0/en/manual/introduction/whatsnew600#services) for the list of changes).   This page describes how services and SLAs defined in earlier Zabbix versions are changed during an upgrade to Zabbix 6.0 or newer.

en-us	#### Overview  Media types are [exported](/manual/xml_export_import) with all related objects and object relations.
fa	#### مرور  Media types are [exported](/manual/xml_export_import) with all related objects and object relations.

en-us	#### Overview  This section lists parameters supported in the Ceph Zabbix agent 2 plugin configuration file (ceph.conf).   Note that:  -   The default values reflect process defaults, not the values in the     shipped configuration files; -   Zabbix supports configuration files only in UTF-8 encoding without     [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); -   Comments starting with "\#" are only supported at the beginning of     the line.
fa	#### Overview  This section lists parameters supported in the Ceph Zabbix agent 2 plugin configuration file (ceph.conf). Note that:  -   The default values reflect process defaults, not the values in the     shipped configuration files; -   Zabbix supports configuration files only in UTF-8 encoding without     [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); -   Comments starting with "\#" are only supported at the beginning of     the line.

en-us	#### Overview  This section lists parameters supported in the Docker Zabbix agent 2 plugin configuration file (docker.conf).   Note that:  -   The default values reflect process defaults, not the values in the     shipped configuration files; -   Zabbix supports configuration files only in UTF-8 encoding without     [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); -   Comments starting with "\#" are only supported at the beginning of     the line.
fa	#### Overview  This section lists parameters supported in the Docker Zabbix agent 2 plugin configuration file (docker.conf). Note that:  -   The default values reflect process defaults, not the values in the     shipped configuration files; -   Zabbix supports configuration files only in UTF-8 encoding without     [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); -   Comments starting with "\#" are only supported at the beginning of     the line.

en-us	#### Overview  This section lists parameters supported in the Memcached Zabbix agent 2 plugin configuration file (memcached.conf).   Note that:  -   The default values reflect process defaults, not the values in the     shipped configuration files; -   Zabbix supports configuration files only in UTF-8 encoding without     [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); -   Comments starting with "\#" are only supported at the beginning of     the line.
fa	#### Overview  This section lists parameters supported in the Memcached Zabbix agent 2 plugin configuration file (memcached.conf). Note that:  -   The default values reflect process defaults, not the values in the     shipped configuration files; -   Zabbix supports configuration files only in UTF-8 encoding without     [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); -   Comments starting with "\#" are only supported at the beginning of     the line.

en-us	#### Overview  This section lists parameters supported in the Modbus Zabbix agent 2 plugin configuration file (modbus.conf).   Note that:  -   The default values reflect process defaults, not the values in the     shipped configuration files; -   Zabbix supports configuration files only in UTF-8 encoding without     [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); -   Comments starting with "\#" are only supported at the beginning of     the line.
fa	#### Overview  This section lists parameters supported in the Modbus Zabbix agent 2 plugin configuration file (modbus.conf). Note that:  -   The default values reflect process defaults, not the values in the     shipped configuration files; -   Zabbix supports configuration files only in UTF-8 encoding without     [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); -   Comments starting with "\#" are only supported at the beginning of     the line.

en-us	#### Overview  This section lists parameters supported in the MQTT Zabbix agent 2 plugin configuration file (mqtt.conf).   Note that:  -   The default values reflect process defaults, not the values in the     shipped configuration files; -   Zabbix supports configuration files only in UTF-8 encoding without     [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); -   Comments starting with "\#" are only supported at the beginning of     the line.
fa	#### Overview  This section lists parameters supported in the MQTT Zabbix agent 2 plugin configuration file (mqtt.conf). Note that:  -   The default values reflect process defaults, not the values in the     shipped configuration files; -   Zabbix supports configuration files only in UTF-8 encoding without     [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); -   Comments starting with "\#" are only supported at the beginning of     the line.

en-us	#### Overview  This section lists parameters supported in the MySQL Zabbix agent 2 plugin configuration file (mysql.conf).   Note that:  -   The default values reflect process defaults, not the values in the     shipped configuration files; -   Zabbix supports configuration files only in UTF-8 encoding without     [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); -   Comments starting with "\#" are only supported at the beginning of     the line.
fa	#### Overview  This section lists parameters supported in the MySQL Zabbix agent 2 plugin configuration file (mysql.conf). Note that:  -   The default values reflect process defaults, not the values in the     shipped configuration files; -   Zabbix supports configuration files only in UTF-8 encoding without     [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); -   Comments starting with "\#" are only supported at the beginning of     the line.

en-us	#### Overview  With escalations you can create custom scenarios for sending notifications or executing remote commands.  In practical terms it means that:  -   Users can be informed about new problems immediately. -   Notifications can be repeated until the problem is resolved. -   Sending a notification can be delayed. -   Notifications can be escalated to another "higher" user group. -   Remote commands can be executed immediately or when a problem is not     resolved for a lengthy period.  Actions are escalated based on the **escalation step**. Each step has a duration in time.  You can define both the default duration and a custom duration of an individual step. The minimum duration of one escalation step is 60 seconds.  You can start actions, such as sending notifications or executing commands, from any step. Step one is for immediate actions. If you want to delay an action, you can assign it to a later step. For each step, several actions can be defined.  The number of escalation steps is not limited.  Escalations are defined when [configuring an operation](operation#configuring_an_operation). Escalations are supported for problem operations only, not recovery.
fa	#### Overview  With escalations you can create custom scenarios for sending notifications or executing remote commands.  In practical terms it means that:  -   Users can be informed about new problems immediately -   Notifications can be repeated until the problem is resolved -   Sending a notification can be delayed -   Notifications can be escalated to another "higher" user group -   Remote commands can be executed immediately or when a problem is not     resolved for a lengthy period  Actions are escalated based on the **escalation step**. Each step has a duration in time.  You can define both the default duration and a custom duration of an individual step. The minimum duration of one escalation step is 60 seconds.  You can start actions, such as sending notifications or executing commands, from any step. Step one is for immediate actions. If you want to delay an action, you can assign it to a later step. For each step, several actions can be defined.  The number of escalation steps is not limited.  Escalations are defined when [configuring an operation](operation#configuring_an_operation). Escalations are supported for problem operations only, not recovery.

en-us	#### Overview  Zabbix agent is deployed on a monitoring target to actively monitor local resources and applications (hard drives, memory, processor statistics, etc.).  The agent gathers operational information locally and reports data to Zabbix server for further processing. In case of failures (such as a hard disk running full or a crashed service process), Zabbix server can actively alert the administrators of the particular machine that reported the failure.  Zabbix agents are extremely efficient because of use of native system calls for gathering statistical information.
fa	#### Overview  Zabbix agent is deployed on a monitoring target to actively monitor local resources and applications (hard drives, memory, processor statistics etc).  The agent gathers operational information locally and reports data to Zabbix server for further processing. In case of failures (such as a hard disk running full or a crashed service process), Zabbix server can actively alert the administrators of the particular machine that reported the failure.  Zabbix agents are extremely efficient because of use of native system calls for gathering statistical information.

en-us	### Parameters  `(array)` IDs of hosts to delete.
fa	### پارامتر ها  `(array)` IDs of hosts to delete.

en-us	### Parameters  `(array)` IDs of items to clear.
fa	### پارامتر ها   `(array)` IDs of items to clear.

en-us	### Parameters  `(array)` IDs of the actions to delete.
fa	### پارامترها  شناسه «(آرایه)» های اکشن  برای حذف کردن .

en-us	### Parameters  `(array)` IDs of the correlations to delete.
fa	### پارامتر ها   «(آرایه)» شناسه های همبستگی برای حذف.

en-us	### Parameters  `(array)` IDs of the dashboards to delete.
fa	### پارامتر ها   «(آرایه)» شناسه های همبستگی برای حذف.

en-us	### Parameters  `(array)` IDs of the discovery rules to delete.
fa	### پارامتر ها   «(آرایه)» شناسه های همبستگی برای حذف.

en-us	### Parameters  `(array)` IDs of the graph prototypes to delete.
fa	###پارامتر ها  `object graphprototype.delete(array graphPrototypeIds)`  This method allows to delete graph prototypes.  ::: noteclassic This method is only available to *Admin* and *Super admin* user types. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/administration/user_roles) for more information. :::

en-us	### Parameters  `(array)` IDs of the graphs to delete.
fa	### پارامتر ها   `(array)` IDs of the graphs to delete.

en-us	### Parameters  `(array)` IDs of the host groups to delete.
fa	###پارامتر ها   `(array)` IDs of the host groups to delete.

en-us	### Parameters  `(array)` IDs of the host interfaces to delete.
fa	### پارامتر ها   `(array)` IDs of the host interfaces to delete.

en-us	### Parameters  `(array)` IDs of the host prototypes to delete.
fa	### پارامتر ها   `(array)` IDs of the host prototypes to delete.

en-us	### Parameters  `(array)` IDs of the icon maps to delete.
fa	### پارامتر ها   `(array)` IDs of the icon maps to delete.

en-us	### Parameters  `(array)` IDs of the LLD rules to delete.
fa	### پارامتر ها   «(آرایه)» شناسه های همبستگی برای حذف.

en-us	### Parameters  `(array)` IDs of the web scenarios to delete.
fa	### پارامتر ها   `(array)` IDs of the web scenarios to delete.

en-us	### Parameters  `(array)` The method accepts an empty array.
fa	### پارامترها  `(آرایه)` این روش یک آرایه خالی را می پذیرد.

en-us	### Parameters  `(object/array)` Actions to create.  Additionally to the [standard action properties](object#action), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |filter|object|Action [filter](/manual/api/reference/action/object#action_filter) object for the action.| |operations|array|Action [operations](/manual/api/reference/action/object#action_operation) to create for the action.| |recovery\_operations|array|Action [recovery operations](/manual/api/reference/action/object#action_recovery_operation) to create for the action.| |update\_operations|array|Action [update operations](/manual/api/reference/action/object#action_update_operation) to create for the action.|
fa	### پارامتر ها   «(شیء/آرایه)» اقداماتی برای ساخت.  علاوه بر [ویژگی‌های اقدام استاندارد] (object#action)، متد پارامترهای زیر را می پذیرد.  |پارامتر|[نوع](/manual/api/reference_commentary#data_types)|توضیحات| |--|--|------| |filter|object|Action [filter](/manual/api/reference/action/object#action_filter) شیء برای اکشن.| |عملیات|آرایه|عملیات [عملیات](/manual/api/reference/action/object#action_operation) برای ایجاد اکشن.| |بازیابی\_عملیات|آرایه|عملیات [عملیات بازیابی](/manual/api/reference/action/object#action_recovery_operation) برای ایجاد اکشن.| |update\_operations|آرایه|عملیات [عملیات به‌روزرسانی](/manual/api/reference/action/object#action_update_operation) برای ایجاد عمل.|

en-us	### Parameters  `(object/array)` Correlation properties to be updated.  The `correlationid` property must be defined for each correlation, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  Additionally to the [standard correlation properties](object#correlation), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |filter|object|Correlation [filter](/manual/api/reference/correlation/object#correlation_filter) object to replace the current filter.| |operations|array|Correlation [operations](/manual/api/reference/correlation/object#correlation_operation) to replace existing operations.|
fa	### پارامتر ها   "(شیء/آرایه)" ویژگی های همبستگی به روز می شوند.  ویژگی "correlationid" باید برای هر همبستگی، همه تعریف شود سایر خواص اختیاری هستند. فقط خواص پاس شده خواهد بود به روز شده، بقیه بدون تغییر باقی خواهند ماند.  علاوه بر [همبستگی استاندارد خواص](object#correlation)، روش موارد زیر را می پذیرد مولفه های.  |پارامتر|[نوع](/manual/api/reference_commentary#data_types)|توضیحات| |--|--|------| |filter|object|Correlation [filter](/manual/api/reference/correlation/object#correlation_filter) شیء جایگزین فیلتر فعلی.| |عملیات|آرایه|همبستگی [عملیات](/manual/api/reference/correlation/object#correlation_operation) برای جایگزینی عملیات موجود.|

en-us	### Parameters  `(object/array)` Discovery rule properties to be updated.  The `druleid` property must be defined for each discovery rule, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  Additionally to the [standard discovery rule properties](object#discovery_rule), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |dchecks|array|Discovery [checks](/manual/api/reference/dcheck/object) to replace existing checks.|
fa	### پارامتر ها   `(object/array)` Discovery rule properties to be updated.  The `druleid` property must be defined for each discovery rule, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  Additionally to the [standard discovery rule properties](object#discovery_rule), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |dchecks|array|Discovery [checks](/manual/api/reference/dcheck/object) to replace existing checks.|

en-us	### Parameters  `(object/array)` Graph properties to be updated.  The `graphid` property must be defined for each graph, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  Additionally to the [standard graph properties](object#graph) the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |gitems|array|Graph [items](/manual/api/reference/graphitem/object) to replace existing graph items. If a graph item has the `gitemid` property defined it will be updated, otherwise a new graph item will be created.|
fa	### پارامتر ها   `(object/array)` Graph properties to be updated.  The `graphid` property must be defined for each graph, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  Additionally to the [standard graph properties](object#graph) the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |gitems|array|Graph [items](/manual/api/reference/graphitem/object) to replace existing graph items. If a graph item has the `gitemid` property defined it will be updated, otherwise a new graph item will be created.|

en-us	### Parameters  `(object/array)` Graph prototype properties to be updated.  The `graphid` property must be defined for each graph prototype, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  Additionally to the [standard graph prototype properties](object#graph_prototype), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |gitems|array|Graph [items](/manual/api/reference/graphitem/object) to replace existing graph items. If a graph item has the `gitemid` property defined it will be updated, otherwise a new graph item will be created.|
fa	### پارامتر ها   `(object/array)` Graph prototype properties to be updated.  The `graphid` property must be defined for each graph prototype, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  Additionally to the [standard graph prototype properties](object#graph_prototype), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |gitems|array|Graph [items](/manual/api/reference/graphitem/object) to replace existing graph items. If a graph item has the `gitemid` property defined it will be updated, otherwise a new graph item will be created.|

en-us	### Parameters  `(object/array)` [Host group properties](object#host_group) to be updated.  The `groupid` property must be defined for each host group, all other properties are optional. Only the given properties will be updated, all others will remain unchanged.
fa	### پارامتر ها   `(object/array)` [Host group properties](object#host_group) to be updated.  The `groupid` property must be defined for each host group, all other properties are optional. Only the given properties will be updated, all others will remain unchanged.

en-us	### Parameters  `(object/array)` [Host interface properties](object#host_interface) to be updated.  The `interfaceid` property must be defined for each host interface, all other properties are optional. Only the given properties will be updated, all others will remain unchanged.
fa	### پارامتر ها   `(object/array)` [Host interface properties](object#host_interface) to be updated.  The `interfaceid` property must be defined for each host interface, all other properties are optional. Only the given properties will be updated, all others will remain unchanged.

en-us	### Parameters  `(object/array)` Host properties to be updated.  The `hostid` property must be defined for each host, all other properties are optional. Only the given properties will be updated, all others will remain unchanged.  Note, however, that updating the host technical name will also update the host's visible name (if not given or empty) by the host's technical name value.  Additionally to the [standard host properties](object#host), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |groups|object/array|Host [groups](/manual/api/reference/hostgroup/object#host_group) to replace the current host groups the host belongs to.<br><br>The host groups must have the `groupid` property defined. All host groups that are not listed in the request will be unlinked.| |interfaces|object/array|Host [interfaces](/manual/api/reference/hostinterface/object) to replace the current host interfaces.<br><br>All interfaces that are not listed in the request will be removed.| |tags|object/array|Host [tags](/manual/api/reference/host/object#host_tag) to replace the current host tags.<br><br>All tags that are not listed in the request will be removed.| |inventory|object|Host [inventory](/manual/api/reference/host/object#host_inventory) properties.| |macros|object/array|[User macros](/manual/api/reference/usermacro/object) to replace the current user macros.<br><br>All macros that are not listed in the request will be removed.| |templates|object/array|[Templates](/manual/api/reference/template/object) to replace the currently linked templates. All templates that are not listed in the request will be only unlinked.<br><br>The templates must have the `templateid` property defined.| |templates\_clear|object/array|[Templates](/manual/api/reference/template/object) to unlink and clear from the host.<br><br>The templates must have the `templateid` property defined.|  ::: notetip As opposed to the Zabbix frontend, when `name` (visible host name) is the same as `host` (technical host name), updating `host` via API will not automatically update `name`. Both properties need to be updated explicitly. :::
fa	### پارامترها `(object/array)` Host properties to be updated.  The `hostid` property must be defined for each host, all other properties are optional. Only the given properties will be updated, all others will remain unchanged.  Note, however, that updating the host technical name will also update the host's visible name (if not given or empty) by the host's technical name value.  Additionally to the [standard host properties](object#host), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |groups|object/array|Host [groups](/manual/api/reference/hostgroup/object#host_group) to replace the current host groups the host belongs to.<br><br>The host groups must have the `groupid` property defined. All host groups that are not listed in the request will be unlinked.| |interfaces|object/array|Host [interfaces](/manual/api/reference/hostinterface/object) to replace the current host interfaces.<br><br>All interfaces that are not listed in the request will be removed.| |tags|object/array|Host [tags](/manual/api/reference/host/object#host_tag) to replace the current host tags.<br><br>All tags that are not listed in the request will be removed.| |inventory|object|Host [inventory](/manual/api/reference/host/object#host_inventory) properties.| |macros|object/array|[User macros](/manual/api/reference/usermacro/object) to replace the current user macros.<br><br>All macros that are not listed in the request will be removed.| |templates|object/array|[Templates](/manual/api/reference/template/object) to replace the currently linked templates. All templates that are not listed in the request will be only unlinked.<br><br>The templates must have the `templateid` property defined.| |templates\_clear|object/array|[Templates](/manual/api/reference/template/object) to unlink and clear from the host.<br><br>The templates must have the `templateid` property defined.|  ::: notetip As opposed to the Zabbix frontend, when `name` (visible host name) is the same as `host` (technical host name), updating `host` via API will not automatically update `name`. Both properties need to be updated explicitly. :::

en-us	### Parameters  `(object/array)` Icon map properties to be updated.  The `iconmapid` property must be defined for each icon map, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  Additionally to the [standard icon map properties](object#icon_map), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |mappings|array|[Icon mappings](/manual/api/reference/iconmap/object#icon_mapping) to replace the existing icon mappings.|
fa	### پارامترها   "(شیء/آرایه)" ویژگی های آیکون نقشه به روز می شود.  ویژگی "iconmapid" باید برای هر آیکون نقشه تعریف شود و بقیه ویژگی ها اختیاری هستند فقط ویژگی های تصویب شده به روز می شوند،  بقیه بدون تغییر باقی خواهند ماند.  علاوه بر [مشخصات استاندارد icon map] (object#icon_map)، متد پارامترهای زیر را می پذیرد.  |پارامتر|[نوع](/manual/api/reference_commentary#data_types)|توضیحات| |--|--|------| |mappings|آرایه|[Icon mappings](/manual/api/reference/iconmap/object#icon_mapping) برای جایگزینی نگاشت نمادهای موجود.|

en-us	### Parameters  `(object/array)` Scripts to create.  The method accepts scripts with the [standard script properties](/manual/api/reference/script/object#script).
fa	### پارامترها   اسکریپت هایی برای ایجاد `(شیء/آرایه).  این روش اسکریپت هایی را با [خواص اسکریپت استاندارد می پذیرد ](/دستی/api/reference/script/object#script).

en-us	### Parameters  `(object/array)` Web scenario properties to be updated.  The `httptestid` property must be defined for each web scenario, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  Additionally to the [standard web scenario properties](object#web_scenario), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |steps|array|Scenario [steps](/manual/api/reference/httptest/object#scenario_step) to replace existing steps.| |tags|array|Web scenario [tags](/manual/api/reference/httptest/object#web_scenario_tag).|
fa	### پارامتر ها  `(object/array)` Web scenario properties to be updated.  The `httptestid` property must be defined for each web scenario, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  Additionally to the [standard web scenario properties](object#web_scenario), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |steps|array|Scenario [steps](/manual/api/reference/httptest/object#scenario_step) to replace existing steps.| |tags|array|Web scenario [tags.](/manual/api/reference/httptest/object#web_scenario_tag)|

en-us	### Parameters  `(object)` Parameters defining the desired output.  The method supports only one parameter.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |output|query|This parameter being common for all `get` methods described in the [reference commentary](/manual/api/reference_commentary#common_get_method_parameters).|
fa	### پارامترها   `(شیء)` پارامترهای تعیین کننده خروجی مورد نظراست .  این روش تنها از یک پارامتر پشتیبانی می کند.  |پارامتر|[نوع](/manual/api/reference_commentary#data_types)|توضیحات| |--|--|------| |output|query|این پارامتر برای همه روش‌های «get» که در [تفسیر مرجع] توضیح داده شده مشترک است (/manual/api/reference_commentary#common_get_method_parameters).|

en-us	### Parameters  `(object)` Parameters defining the desired output.  The method supports only one parameter.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |output|query|This parameter being common for all `get` methods described in the [reference commentary](/manual/api/reference_commentary#common_get_method_parameters).|
fa	### پارامترها   `(شیء)` پارامترهای تعیین کننده خروجی مورد نظراست .  این روش تنها از یک پارامتر پشتیبانی می کند.  |پارامتر|[نوع](/manual/api/reference_commentary#data_types)|توضیحات| |--|--|------| |output|query|این پارامتر برای همه روش‌های «get» که در [تفسیر مرجع] توضیح داده شده مشترک است (/manual/api/reference_commentary#common_get_method_parameters).|

en-us	### Parameters  `(object)` Parameters defining the desired output.  The method supports only one parameter.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |output|query|This parameter being common for all `get` methods described in the [reference commentary](/manual/api/reference_commentary#common_get_method_parameters).|
fa	### پارامترها   `(شیء)` پارامترهای تعیین کننده خروجی مورد نظراست .  این روش تنها از یک پارامتر پشتیبانی می کند.  |پارامتر|[نوع](/manual/api/reference_commentary#data_types)|توضیحات| |--|--|------| |output|query|این پارامتر برای همه روش‌های «get» که در [تفسیر مرجع] توضیح داده شده مشترک است (/manual/api/reference_commentary#common_get_method_parameters).|

en-us	### Parameters  `(object)` Parameters defining the LLD rules to copy and the target hosts.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |discoveryids|array|IDs of the LLD rules to be copied.| |hostids|array|IDs of the hosts to copy the LLD rules to.|
fa	### پارامترها  `(object)` Parameters defining the LLD rules to copy and the target hosts.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |discoveryids|array|IDs of the LLD rules to be copied.| |hostids|array|IDs of the hosts to copy the LLD rules to.|

en-us	 # Plugins
fa	# Plugins

en-us	 #### Possible deadlocks with MySQL/MariaDB  When running under high load, and with more than one LLD worker involved, it is possible to run into a deadlock caused by an InnoDB error related to the row-locking strategy (see [upstream bug](https://github.com/mysql/mysql-server/commit/7037a0bdc83196755a3bf3e935cfb3c0127715d5)). The error has been fixed in MySQL since 8.0.29, but not in MariaDB. For more details, see [ZBX-21506](https://support.zabbix.com/browse/ZBX-21506).
fa	 #### Possible deadlocks with MySQL/MariaDB  When running under high load, and with more than one LLD worker involved, it is possible to run into a deadlock caused by an  InnoDB error related to the row-locking strategy (see [upstream bug](https://github.com/mysql/mysql-server/commit/7037a0bdc83196755a3bf3e935cfb3c0127715d5)).  The error has been fixed in MySQL since 8.0.29, but not in MariaDB. For more details, see [ZBX-21506](https://support.zabbix.com/browse/ZBX-21506).

en-us	### Reserved ID value "0"  Reserved ID value "0" can be used to filter elements and to remove referenced objects. For example, to remove a referenced proxy from a host, proxy\_hostid should be set to 0 ("proxy\_hostid": "0") or to filter hosts monitored by server option proxyids should be set to 0 ("proxyids": "0").
fa	### مقدار شناسه رزرو شده "0"  از مقدار شناسه رزرو شده "0" می توان برای فیلتر کردن عناصر و حذف اشیاء ارجاع شده استفاده کرد به عنوان مثال، برای حذف یک پراکسی ارجاع شده از a میزبان، پروکسی\_hostid باید روی 0 ("proxy\_hostid": "0") یا به میزبان های فیلتر که توسط پروکسی های گزینه سرور نظارت می شوند باید روی 0 تنظیم شوند ("proxyids": "0").

en-us	### Return values  `(array)` Returns an array with changes in configuration, that will be made.
fa	### مقادیر را برمی گرداند   `(آرایه)` یک آرایه را با تغییراتی در پیکربندی ساخته شده است را برمی گرداند

en-us	### Return values  `(boolean )` Returns boolean true as result on successful update.
fa	### مقادیر را برمی گرداند  «(بولین)» در به‌روزرسانی موفقیت‌آمیز، بولین واقعی را برمی‌گرداند.

en-us	### Return values  `(boolean)` Returns `true` if importing has been successful.
fa	### مقادیر را برمی گرداند  «(بولین)» اگر وارد کردن موفقیت آمیز باشد، «درست» را برمی‌گرداند.

en-us	### Return values  `(boolean)` Returns `true` if the copying was successful.
fa	### مقادیر را برمی گرداند

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
fa	### بازگشت مقادیر  «(عدد صحیح/آرایه)» یکی را برمی‌گرداند:  - آرایه ای از اشیاء؛ - تعداد اشیاء بازیابی شده، اگر پارامتر "countOutput" داشته باشد     استفاده شده است.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
fa	### بازگشت مقادیر  «(عدد صحیح/آرایه)» یکی را برمی‌گرداند:  - آرایه ای از اشیاء؛ - تعداد اشیاء بازیابی شده، اگر پارامتر "countOutput" داشته باشد     استفاده شده است.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
fa	### بازگشت مقادیر  «(عدد صحیح/آرایه)» یکی را برمی‌گرداند:  - آرایه ای از اشیاء؛ - تعداد اشیاء بازیابی شده، اگر پارامتر "countOutput" داشته باشد     استفاده شده است.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
fa	### بازگشت مقادیر  «(عدد صحیح/آرایه)» یکی را برمی‌گرداند:  - آرایه ای از اشیاء؛ - تعداد اشیاء بازیابی شده، اگر پارامتر "countOutput" داشته باشد     استفاده شده است.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
fa	### بازگشت مقادیر  «(عدد صحیح/آرایه)» یکی را برمی‌گرداند:  - آرایه ای از اشیاء؛ - تعداد اشیاء بازیابی شده، اگر پارامتر "countOutput" داشته باشد     استفاده شده است.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
fa	###بازگشت مقادیر   `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
fa	### بازگشت مقادیر  «(عدد صحیح/آرایه)» یکی را برمی‌گرداند:  - آرایه ای از اشیاء؛ - تعداد اشیاء بازیابی شده، اگر پارامتر "countOutput" داشته باشد     استفاده شده است.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
fa	### بازگشت مقادیر  «(عدد صحیح/آرایه)» یکی را برمی‌گرداند:  - آرایه ای از اشیاء؛ - تعداد اشیاء بازیابی شده، اگر پارامتر "countOutput" داشته باشد     استفاده شده است.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
fa	### بازگشت مقادیر  «(عدد صحیح/آرایه)» یکی را برمی‌گرداند:  - آرایه ای از اشیاء؛ - تعداد اشیاء بازیابی شده، اگر پارامتر "countOutput" داشته باشد     استفاده شده است.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
fa	### بازگشت مقادیر  «(عدد صحیح/آرایه)» یکی را برمی‌گرداند:  - آرایه ای از اشیاء؛ - تعداد اشیاء بازیابی شده، اگر پارامتر "countOutput" داشته باشد     استفاده شده است.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
fa	### بازگشت مقادیر  «(عدد صحیح/آرایه)» یکی را برمی‌گرداند:  - آرایه ای از اشیاء؛ - تعداد اشیاء بازیابی شده، اگر پارامتر "countOutput" داشته باشد     استفاده شده است.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
fa	### بازگشت مقادیر  «(عدد صحیح/آرایه)» یکی را برمی‌گرداند:  - آرایه ای از اشیاء؛ - تعداد اشیاء بازیابی شده، اگر پارامتر "countOutput" داشته باشد     استفاده شده است.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
fa	### بازگشت مقادیر  «(عدد صحیح/آرایه)» یکی را برمی‌گرداند:  - آرایه ای از اشیاء؛ - تعداد اشیاء بازیابی شده، اگر پارامتر "countOutput" داشته باشد     استفاده شده است.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
fa	### بازگشت مقادیر  «(عدد صحیح/آرایه)» یکی را برمی‌گرداند:  - آرایه ای از اشیاء؛ - تعداد اشیاء بازیابی شده، اگر پارامتر "countOutput" داشته باشد     استفاده شده است.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
fa	### بازگشت مقادیر  «(عدد صحیح/آرایه)» یکی را برمی‌گرداند:  - آرایه ای از اشیاء؛ - تعداد اشیاء بازیابی شده، اگر پارامتر "countOutput" داشته باشد     استفاده شده است.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
fa	### بازگشت مقادیر  «(عدد صحیح/آرایه)» یکی را برمی‌گرداند:  - آرایه ای از اشیاء؛ - تعداد اشیاء بازیابی شده، اگر پارامتر "countOutput" داشته باشد     استفاده شده است.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
fa	### بازگشت مقادیر  «(عدد صحیح/آرایه)» یکی را برمی‌گرداند:  - آرایه ای از اشیاء؛ - تعداد اشیاء بازیابی شده، اگر پارامتر "countOutput" داشته باشد     استفاده شده است.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
fa	### بازگشت مقادیر  «(عدد صحیح/آرایه)» یکی را برمی‌گرداند:  - آرایه ای از اشیاء؛ - تعداد اشیاء بازیابی شده، اگر پارامتر "countOutput" داشته باشد     استفاده شده است.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
fa	### بازگشت مقادیر  «(عدد صحیح/آرایه)» یکی را برمی‌گرداند:  - آرایه ای از اشیاء؛ - تعداد اشیاء بازیابی شده، اگر پارامتر "countOutput" داشته باشد     استفاده شده است.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
fa	### بازگشت مقادیر  «(عدد صحیح/آرایه)» یکی را برمی‌گرداند:  - آرایه ای از اشیاء؛ - تعداد اشیاء بازیابی شده، اگر پارامتر "countOutput" داشته باشد     استفاده شده است.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
fa	### بازگشت مقادیر  «(عدد صحیح/آرایه)» یکی را برمی‌گرداند:  - آرایه ای از اشیاء؛ - تعداد اشیاء بازیابی شده، اگر پارامتر "countOutput" داشته باشد     استفاده شده است.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
fa	### بازگشت مقادیر  «(عدد صحیح/آرایه)» یکی را برمی‌گرداند:  - آرایه ای از اشیاء؛ - تعداد اشیاء بازیابی شده، اگر پارامتر "countOutput" داشته باشد     استفاده شده است.

en-us	### Return values  `(object)` Returns an object containing the IDs of the cleared items under the `itemids` property.
fa	### بازگشت مقادیر   `(object)` Returns an object containing the IDs of the cleared items under the `itemids` property.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created actions under the `actionids` property. The order of the returned IDs matches the order of the passed actions.
fa	### برگشت مقادیر  `(object)` یک شی حاوی شناسه اقدامات ایجاد شده را تحت خاصیت «شناسه اکشن » برمی گرداند . ترتیب شناسه های برگشتی با ترتیب اقدامات انجام شده مطابقت دارد

en-us	### Return values  `(object)` Returns an object containing the IDs of the created correlations under the `correlationids` property. The order of the returned IDs matches the order of the passed correlations.
fa	### مقادیر را برمی گرداند  `(object)` یک شی حاوی شناسه های اسکریپت های ایجاد شده را تحت ویژگی "scriptids" برمی گرداند.  ترتیب شناسه های برگشتی با ترتیب اسکریپت های پاس شده مطابقت دارد

en-us	### Return values  `(object)` Returns an object containing the IDs of the created dashboards under the `dashboardids` property. The order of the returned IDs matches the order of the passed dashboards.
fa	### برگشت مقادیر  `(object)` یک شی حاوی شناسه اقدامات ایجاد شده را تحت خاصیت «شناسه اکشن » برمی گرداند . ترتیب شناسه های برگشتی با ترتیب اقدامات انجام شده مطابقت دارد

en-us	### Return values  `(object)` Returns an object containing the IDs of the created discovery rules under the `druleids` property. The order of the returned IDs matches the order of the passed discovery rules.
fa	### برگشت مقادیر  `(object)` یک شی حاوی شناسه اقدامات ایجاد شده را تحت خاصیت «شناسه اکشن » برمی گرداند . ترتیب شناسه های برگشتی با ترتیب اقدامات انجام شده مطابقت دارد

en-us	### Return values  `(object)` Returns an object containing the IDs of the created graph prototypes under the `graphids` property. The order of the returned IDs matches the order of the passed graph prototypes.
fa	### بازگشت مقادیر   `(object)` Returns an object containing the IDs of the created graph prototypes under the `graphids` property. The order of the returned IDs matches the order of the passed graph prototypes.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created graphs under the `graphids` property. The order of the returned IDs matches the order of the passed graphs.
fa	### بازگشت مقادیر   `(object)` Returns an object containing the IDs of the created graphs under the `graphids` property. The order of the returned IDs matches the order of the passed graphs.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created host groups under the `groupids` property. The order of the returned IDs matches the order of the passed host groups.
fa	### بازگشت مقادیر   `(object)` Returns an object containing the IDs of the created hosts under the `hostids` property. The order of the returned IDs matches the order of the passed hosts.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created host interfaces under the `interfaceids` property.
fa	###بازگشت مقادیر   `(object)` Returns an object containing the IDs of the created host interfaces under the `interfaceids` property.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created host interfaces under the `interfaceids` property.
fa	### بازگشت مقادیر   `(object)` Returns an object containing the IDs of the created host interfaces under the `interfaceids` property.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created host interfaces under the `interfaceids` property. The order of the returned IDs matches the order of the passed host interfaces.
fa	### بازگشت مقادیر  `(object)` Returns an object containing the IDs of the created host interfaces under the `interfaceids` property. The order of the returned IDs matches the order of the passed host interfaces.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created host prototypes under the `hostids` property. The order of the returned IDs matches the order of the passed host prototypes.
fa	### بازگشت مقادیر   `(object)` Returns an object containing the IDs of the created host prototypes under the `hostids` property. The order of the returned IDs matches the order of the passed host prototypes.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created hosts under the `hostids` property. The order of the returned IDs matches the order of the passed hosts.
fa	### بازگشت مقادیر   `(object)` Returns an object containing the IDs of the created hosts under the `hostids` property. The order of the returned IDs matches the order of the passed hosts.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created icon maps under the `iconmapids` property. The order of the returned IDs matches the order of the passed icon maps.
fa	### بازگشت مقادیر   `(object)` Returns an object containing the IDs of the created icon maps under the `iconmapids` property. The order of the returned IDs matches the order of the passed icon maps.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created images under the `imageids` property. The order of the returned IDs matches the order of the passed images.
fa	### بازگشت مقادیر   `(object)` Returns an object containing the IDs of the created images under the `imageids` property. The order of the returned IDs matches the order of the passed images.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created LLD rules under the `itemids` property. The order of the returned IDs matches the order of the passed LLD rules.
fa	### برگشت مقادیر  `(object)` یک شی حاوی شناسه اقدامات ایجاد شده را تحت خاصیت «شناسه اکشن » برمی گرداند . ترتیب شناسه های برگشتی با ترتیب اقدامات انجام شده مطابقت دارد

en-us	### Return values  `(object)` Returns an object containing the IDs of the created scripts under the `scriptids` property. The order of the returned IDs matches the order of the passed scripts.
fa	### مقادیر را برمی گرداند  `(object)` یک شی حاوی شناسه های اسکریپت های ایجاد شده را تحت ویژگی "scriptids" برمی گرداند.  ترتیب شناسه های برگشتی با ترتیب اسکریپت های پاس شده مطابقت دارد

en-us	### Return values  `(object)` Returns an object containing the IDs of the created templates under the `templateids` property. The order of the returned IDs matches the order of the passed templates.
fa	### برگشت مقادیر  `(object)` یک شی حاوی شناسه اقدامات ایجاد شده را تحت خاصیت «شناسه اکشن » برمی گرداند . ترتیب شناسه های برگشتی با ترتیب اقدامات انجام شده مطابقت دارد

en-us	### Return values  `(object)` Returns an object containing the IDs of the created web scenarios under the `httptestids` property. The order of the returned IDs matches the order of the passed web scenarios.
fa	###بازگشت مقادیر  `(object)` Returns an object containing the IDs of the created web scenarios under the `httptestids` property. The order of the returned IDs matches the order of the passed web scenarios.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted actions under the `actionids` property.
fa	### بازگشت مقادیر   `(object)` یک شی حاوی شناسه تحت خاصیت «actionids». اقدامات حذف شده را برمی گرداند

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted correlations under the `correlationids` property.
fa	### بازگشت مقادیر  `(object)` یک شی حاوی شناسه های حذف شده را برمی گرداند همبستگی تحت خاصیت "correlationids".

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted dashboards under the `dashboardids` property.
fa	### بازگشت مقادیر   `(object)` یک شی حاوی شناسه های به روز شده را  تحت خاصیت "dashboardids" برمی گرداند

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted discovery rules under the `druleids` property.
fa	### بازگشت مقادیر   `(object)` یک شی حاوی شناسه تحت خاصیت «actionids». اقدامات حذف شده را برمی گرداند

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted graph prototypes under the `graphids` property.
fa	### بازگشت مقادیر   `(object)` Returns an object containing the IDs of the deleted graph prototypes under the `graphids` property.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted graphs under the `graphids` property.
fa	###بازگشت مقادیر   `(object)` Returns an object containing the IDs of the deleted graphs under the `graphids` property.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted host groups under the `groupids` property.
fa	### بازگشت مقادیر   `(object)` Returns an object containing the IDs of the deleted host groups under the `groupids` property.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted host interfaces under the `interfaceids` property.
fa	###بازگشت مقادیر   `(object)` Returns an object containing the IDs of the deleted host interfaces under the `interfaceids` property.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted host interfaces under the `interfaceids` property.
fa	###بازگشت مقادیر   `(object)` Returns an object containing the IDs of the deleted host interfaces under the `interfaceids` property.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted host prototypes under the `hostids` property.
fa	### بازگشت مقادیر   `(object)` Returns an object containing the IDs of the deleted host prototypes under the `hostids` property.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted hosts under the `hostids` property.
fa	###بازگشت مقادیر   `(object)` Returns an object containing the IDs of the deleted hosts under the `hostids` property.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted icon maps under the `iconmapids` property.
fa	### بازگشت مقادیر    `(object)` Returns an object containing the IDs of the deleted icon maps under the `iconmapids` property.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted web scenarios under the `httptestids` property.
fa	### بازگشت مقادیر   `(object)` Returns an object containing the IDs of the deleted web scenarios under the `httptestids` property.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated actions under the `actionids` property.
fa	### بازگشت مقادیر  `(object)` یک شی حاوی شناسه اقدامات به روز شده را برمی گرداند تحت خاصیت «اکشنیدز».

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated correlations under the `correlationids` property.
fa	### بازگشت مقادیر   `(object)` یک شی حاوی شناسه های به روز شده را برمی گرداند همبستگی تحت خاصیت "correlationids".

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated dashboards under the `dashboardids` property.
fa	### بازگشت مقادیر   `(object)` یک شی حاوی شناسه های به روز شده را برمی گرداند همبستگی تحت خاصیت "correlationids".

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated discovery rules under the `druleids` property.
fa	### بازگشت مقادیر   `(object)` یک شی حاوی شناسه تحت خاصیت «actionids». اقدامات حذف شده را برمی گرداند

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated events under the `eventids` property.
fa	### بازگشت مقادیر   `(object)` Returns an object containing the IDs of the updated events under the `eventids` property.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated graph prototypes under the `graphids` property.
fa	### بازگشت مقادیر  `(object)` Returns an object containing the IDs of the updated graph prototypes under the `graphids` property.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated graphs under the `graphids` property.
fa	### بازگشت مقادیر   `(object)` Returns an object containing the IDs of the updated graphs under the `graphids` property.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated host groups under the `groupids` property.
fa	### بازگشت مقادیر   `(object)` Returns an object containing the IDs of the updated host groups under the `groupids` property.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated host groups under the `groupids` property.
fa	### بازگشت مقادیر   `(object)` Returns an object containing the IDs of the updated host groups under the `groupids` property.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated host groups under the `groupids` property.
fa	### بازگشت مقادیر  `(object)` Returns an object containing the IDs of the updated host groups under the `groupids` property.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated host groups under the `groupids` property.
fa	### بازگشت مقادیر   `(object)` Returns an object containing the IDs of the updated host groups under the `groupids` property.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated host interfaces under the `interfaceids` property.
fa	### بازگشت مقادیر    `(object)` Returns an object containing the IDs of the updated host interfaces under the `interfaceids` property.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated host prototypes under the `hostids` property.
fa	### بازگشت مقادیر   `(object)` Returns an object containing the IDs of the updated host prototypes under the `hostids` property.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated hosts under the `hostids` property.
fa	### بازگشت مقادیر   `(object)` Returns an object containing the IDs of the updated hosts under the `hostids` property.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated hosts under the `hostids` property.
fa	### بازگشت مقادیر   `(object)` Returns an object containing the IDs of the updated hosts under the `hostids` property.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated hosts under the `hostids` property.
fa	### بازگشت مقادیر   `(object)` Returns an object containing the IDs of the updated hosts under the `hostids` property.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated hosts under the `hostids` property.
fa	### بازگشت مقادیر   `(object)` Returns an object containing the IDs of the updated hosts under the `hostids` property.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated icon maps under the `iconmapids` property.
fa	### مقادیر را برمی گرداند  `(object)` یک شی حاوی شناسه آیکون نقشه های  به روز شده را برمی گرداند که تحت ویژگی "iconmapids" می باشد . 

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated LLD rules under the `itemids` property.
fa	### بازگشت مقادیر   `(object)` یک شی حاوی شناسه تحت خاصیت «actionids». اقدامات حذف شده را برمی گرداند

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated web scenarios under the `httptestid` property.
fa	###  بازگشت مقادیر   `(object)` Returns an object containing the IDs of the updated web scenarios under the `httptestid` property.

en-us	### Return values  `(object)` Returns authentication object.
fa	### مقادیر را برمی گرداند  `(object)` شیء احراز هویت را برمی گرداند.

en-us	### Return values  `(object)` Returns autoregistration object.
fa	### مقادیر را برمی گرداند  `(object)` شیء احراز هویت را برمی گرداند.

en-us	### Return values  `(object)` Returns housekeeping object.
fa	###بازگشت مقادیر   `(object)` Returns housekeeping object.

en-us	### Return values  `(string)` Returns a serialized string containing the requested configuration data.
fa	### بازگشت مقادیر   `(string)` یک رشته سریالی حاوی موارد درخواستی را برمی گرداند داده های پیکربندی

en-us	### Return values  `(string)` Returns the version of the Zabbix API.  ::: notetip Starting from Zabbix 2.0.4 the version of the API matches the version of Zabbix. :::
fa	### بازگشت مقادیر  `(string)` نسخه Zabbix API را برمی گرداند.  ::: یادداشت شروع از Zabbix 2.0.4 نسخه API با نسخه Zabbix مطابقت دارد. :::

en-us	###      Runtime control options     **config\_cache\_reload**   Reload configuration cache. Ignored if cache is being currently loaded. Active Zabbix proxy will connect to the Zabbix server and request configuration data. Default configuration file (unless **-c** option is specified) will be used to find PID file and signal will be sent to process, listed in PID file.     **snmp\_cache\_reload**   Reload SNMP cache.     **housekeeper\_execute**   Execute the housekeeper. Ignored if housekeeper is being currently executed.     **diaginfo**\[=*section*\]   Log internal diagnostic information of the specified section. Section can be *historycache*, *preprocessing*. By default diagnostic information of all sections is logged.     **log\_level\_increase**\[=*target*\]   Increase log level, affects all processes if target is not specified.     **log\_level\_decrease**\[=*target*\]   Decrease log level, affects all processes if target is not specified.  [ ]{#lbAG}
fa	###     گزینه های کنترل زمان اجرا     **config\_cache\_reload** بارگذاری مجدد کش پیکربندی اگر کش در حال بارگیری باشد نادیده گرفته می شود. پروکسی فعال Zabbix به سرور Zabbix متصل می شود و درخواست می کند داده های پیکربندی فایل پیکربندی پیش فرض (مگر اینکه گزینه **-c** باشد مشخص شده) برای یافتن فایل PID استفاده می شود و سیگنال به آن ارسال می شود فرآیند، در فایل PID فهرست شده است.     **snmp\_cache\_reload** بارگیری مجدد حافظه پنهان SNMP.     **خانه دار\_اجرا** خانه دار را اعدام کنید. اگر در حال حاضر خانه دار باشد نادیده گرفته می شود اجرا شده.     **اطلاعات دیاگ**\[=*بخش*\] اطلاعات تشخیصی داخلی بخش مشخص شده را ثبت کنید. بخش می تواند *historycache*، *preprocessing* باشد. به طور پیش فرض تشخیصی اطلاعات تمام بخش ها ثبت می شود.     **ورود\_سطح\_افزایش**\[=*هدف*\] اگر هدف مشخص نشده باشد، سطح گزارش را افزایش دهید، بر همه فرآیندها تأثیر می گذارد.     **ورود\_سطح\_کاهش**\[=*هدف*\] سطح گزارش را کاهش دهید، اگر هدف مشخص نشده باشد، بر تمام فرآیندها تأثیر می گذارد.  [ ]{#lbAG}

en-us	# script.create
fa	#ساخت اسکریپت

en-us	### See also  -   [Action filter](object#action_filter) -   [Action operation](object#action_operation)
fa	### همچنین ببینید  - [Action filter](object#action_filter) - [عملیات عمل] (شیء#عمل_عملی)

en-us	### See also  -   [Action filter](object#action_filter) -   [Action operation](object#action_operation)
fa	### همچنین ببینید  - [Action filter](object#action_filter) - [عملیات عمل] (شیء#عمل_عملی)

en-us	### See also  -   [Alert](/manual/api/reference/alert/object) -   [Item](/manual/api/reference/item/object) -   [Host](/manual/api/reference/host/object) -   [LLD rule](/manual/api/reference/discoveryrule/object#lld_rule) -   [Trigger](/manual/api/reference/trigger/object)
fa	### همچنین ببینید   -   [Alert](/manual/api/reference/alert/object) -   [Item](/manual/api/reference/item/object) -   [Host](/manual/api/reference/host/object) -   [LLD rule](/manual/api/reference/discoveryrule/object#lld_rule) -   [Trigger](/manual/api/reference/trigger/object)

en-us	### See also  -   [Audit log object](/manual/api/reference/auditlog/object)
fa	### همچنین ببینید  - [ابژه گزارش حسابرسی](/دستی/api/reference/auditlog/object)

en-us	### See also  -   [Correlation filter](object#correlation_filter) -   [Correlation operation](object#correlation_operation)
fa	### همچنین ببینید  - [فیلتر همبستگی](شیء#همبستگی_فیلتر) - [عملیات همبستگی] (object#correlation_operation)

en-us	### See also  -   [Correlation filter](object#correlation_filter) -   [Correlation operation](object#correlation_operation)
fa	### همچنین ببینید  - [فیلتر همبستگی](شیء#همبستگی_فیلتر) - [عملیات همبستگی] (object#correlation_operation)

en-us	### See also  -   [Correlation filter](object#correlation_filter) -   [Correlation operation](object#correlation_operation)
fa	### همچنین ببینید  - [فیلتر همبستگی](شیء#همبستگی_فیلتر) - [عملیات همبستگی] (object#correlation_operation)

en-us	### See also  -   [Dashboard page](object#dashboard_page) -   [Dashboard widget](object#dashboard_widget) -   [Dashboard widget field](object#dashboard_widget_field) -   [Dashboard user](object#dashboard_user) -   [Dashboard user group](object#dashboard_user_group)
fa	###همچنین ببینید :   -   [Dashboard page](object#dashboard_page) -   [Dashboard widget](object#dashboard_widget) -   [Dashboard widget field](object#dashboard_widget_field) -   [Dashboard user](object#dashboard_user) -   [Dashboard user group](object#dashboard_user_group)

en-us	### See also  -   [Dashboard page](object#dashboard_page) -   [Dashboard widget](object#dashboard_widget) -   [Dashboard widget field](object#dashboard_widget_field) -   [Dashboard user](object#dashboard_user) -   [Dashboard user group](object#dashboard_user_group)
fa	###همچنین ببینید :   -   [Dashboard page](object#dashboard_page) -   [Dashboard widget](object#dashboard_widget) -   [Dashboard widget field](object#dashboard_widget_field) -   [Dashboard user](object#dashboard_user) -   [Dashboard user group](object#dashboard_user_group)

en-us	### See also  -   [Dashboard page](object#dashboard_page) -   [Dashboard widget](object#dashboard_widget) -   [Dashboard widget field](object#dashboard_widget_field) -   [Dashboard user](object#dashboard_user) -   [Dashboard user group](object#dashboard_user_group)
fa	###همچنین ببینید :   -   [Dashboard page](object#dashboard_page) -   [Dashboard widget](object#dashboard_widget) -   [Dashboard widget field](object#dashboard_widget_field) -   [Dashboard user](object#dashboard_user) -   [Dashboard user group](object#dashboard_user_group)

en-us	### See also  -   [Discovered     host](/manual/api/reference/dhost/object#discovered_host) -   [Discovery     check](/manual/api/reference/dcheck/object#discovery_check)
fa	### همچنین ببینید  -   [Discovered     host](/manual/api/reference/dhost/object#discovered_host) -   [Discovery     check](/manual/api/reference/dcheck/object#discovery_check)

en-us	### See also  -   [Discovered     host](/manual/api/reference/dhost/object#discovered_host) -   [Discovery     check](/manual/api/reference/dcheck/object#discovery_check) -   [Host](/manual/api/reference/host/object#host)
fa	### همچنین ببینید   -   [Discovered     host](/manual/api/reference/dhost/object#discovered_host) -   [Discovery     check](/manual/api/reference/dcheck/object#discovery_check) -   [Host](/manual/api/reference/host/object#host)

en-us	### See also  -   [Discovered     service](/manual/api/reference/dservice/object#discovered_service) -   [Discovery rule](/manual/api/reference/drule/object#discovery_rule)
fa	### همچنین ببینید   -   [Discovered     service](/manual/api/reference/dservice/object#discovered_service) -   [Discovery rule](/manual/api/reference/drule/object#discovery_rule)

en-us	### See also  -   [Discovery     check](/manual/api/reference/dcheck/object#discovery_check)
fa	### همچنین ببینید  -   [Discovery     check](/manual/api/reference/dcheck/object#discovery_check)

en-us	### See also  -   [Discovery     check](/manual/api/reference/dcheck/object#discovery_check)
fa	### همچنین ببینید  -   [Discovery     check](/manual/api/reference/dcheck/object#discovery_check)

en-us	## SEE ALSO  Documentation <https://www.zabbix.com/manuals>  **[zabbix\_agent2](zabbix_agent2)**(8), **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_get](zabbix_get)**(1), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(1), **[zabbix\_server](zabbix_server)**(8)  ------------------------------------------------------------------------  [ ]{#index}
fa	## همچنین ببینید  مستندات <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8)، ***[zabbix\_get](zabbix_get)**(8)، **[zabbix\_js](zabbix_js)**(8)، **[zabbix\_proxy](zabbix_proxy)**(8) **[zabbix\_sender](zabbix_sender)**(8) ***[zabbix\_server](zabbix_server)**(8) [ ]{#lbAI}

en-us	## SEE ALSO  Documentation <https://www.zabbix.com/manuals>  **[zabbix\_agent2](zabbix_agent2)**(8), **[zabbix\_get](zabbix_get)**(1), **[zabbix\_js](zabbix_js)**(1), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(1), **[zabbix\_server](zabbix_server)**(8) [ ]{#lbAJ}
fa	## همچنین ببینید  مستندات <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8)، ***[zabbix\_get](zabbix_get)**(8)، **[zabbix\_js](zabbix_js)**(8)، **[zabbix\_proxy](zabbix_proxy)**(8) **[zabbix\_sender](zabbix_sender)**(8) ***[zabbix\_server](zabbix_server)**(8) [ ]{#lbAI}

en-us	## SEE ALSO  Documentation <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_get](zabbix_get)**(1), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(1), **[zabbix\_js](zabbix_js)**(1), **[zabbix\_agent2](zabbix_agent2)**(8) [ ]{#lbAJ}
fa	## همچنین ببینید  مستندات <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8)، ***[zabbix\_get](zabbix_get)**(1)، **[zabbix\_proxy](zabbix_proxy)**(8)، ***[zabbix\_sender](zabbix_sender)**(1)، **[zabbix\_js](zabbix_js)**(1)، ***[zabbix\_agent2](zabbix_agent2)**(8) [ ]{#lbAJ}

en-us	## SEE ALSO  Documentation <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_get](zabbix_get)**(1), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(1), **[zabbix\_server](zabbix_server)**(8), **[zabbix\_js](zabbix_js)**(1), **[zabbix\_agent2](zabbix_agent2)**(8) [ ]{#lbAH}
fa	## همچنین ببینید  مستندات <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8)، ***[zabbix\_get](zabbix_get)**(1)، **[zabbix\_proxy](zabbix_proxy)**(8)، **[zabbix\_sender](zabbix_sender)**(1)، **[zabbix\_server](zabbix_server)**(8)، **[zabbix\_js](zabbix_js)**(1)، ***[zabbix\_agent2](zabbix_agent2)**(8) [ ]{#lbAH}

en-us	## SEE ALSO  Documentation <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_get](zabbix_get)**(1), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_server](zabbix_server)**(8), **[zabbix\_js](zabbix_js)**(1), **[zabbix\_agent2](zabbix_agent2)**(8), **[zabbix\_web\_service](zabbix_web_service)**(8) [ ]{#lbAJ}
fa	## همچنین ببینید  مستندات <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8)، ***[zabbix\_get](zabbix_get)**(8)، **[zabbix\_js](zabbix_js)**(8)، **[zabbix\_proxy](zabbix_proxy)**(8) **[zabbix\_sender](zabbix_sender)**(8) ***[zabbix\_server](zabbix_server)**(8) [ ]{#lbAI}

en-us	## SEE ALSO  Documentation <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_get](zabbix_get)**(1), **[zabbix\_sender](zabbix_sender)**(1), **[zabbix\_server](zabbix_server)**(8), **[zabbix\_js](zabbix_js)**(1), **[zabbix\_agent2](zabbix_agent2)**(8) [ ]{#lbAJ}
fa	## همچنین ببینید  مستندات <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8)، ***[zabbix\_get](zabbix_get)**(8)، **[zabbix\_js](zabbix_js)**(8)، **[zabbix\_proxy](zabbix_proxy)**(8) **[zabbix\_sender](zabbix_sender)**(8) ***[zabbix\_server](zabbix_server)**(8) [ ]{#lbAI}

en-us	## SEE ALSO  Documentation <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_get](zabbix_get)**(8), **[zabbix\_js](zabbix_js)**(8), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(8), **[zabbix\_server](zabbix_server)**(8) [ ]{#lbAI}
fa	## همچنین ببینید  مستندات <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8)، ***[zabbix\_get](zabbix_get)**(8)، **[zabbix\_js](zabbix_js)**(8)، **[zabbix\_proxy](zabbix_proxy)**(8) **[zabbix\_sender](zabbix_sender)**(8) ***[zabbix\_server](zabbix_server)**(8) [ ]{#lbAI}

en-us	## SEE ALSO  Documentation <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(1), **[zabbix\_server](zabbix_server)**(8), **[zabbix\_js](zabbix_js)**(1), **[zabbix\_agent2](zabbix_agent2)**(8), **[zabbix\_web\_service](zabbix_web_service)**(8) [ ]{#lbAI}
fa	## همچنین ببینید  مستندات <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8)، ***[zabbix\_get](zabbix_get)**(8)، **[zabbix\_js](zabbix_js)**(8)، **[zabbix\_proxy](zabbix_proxy)**(8) **[zabbix\_sender](zabbix_sender)**(8) ***[zabbix\_server](zabbix_server)**(8) [ ]{#lbAI}

en-us	### See also  -   [Graph item](/manual/api/reference/graphitem/object#graph_item)
fa	### همچنین ببینید  -   [Graph item](/manual/api/reference/graphitem/object#graph_item)

en-us	### See also  -   [Graph item](/manual/api/reference/graphitem/object#graph_item)
fa	### همچنین ببینید  -   [Graph item](/manual/api/reference/graphitem/object#graph_item)

en-us	### See also  -   [Graph](/manual/api/reference/graph/object#graph)
fa	### همچنین ببینید  -   [Graph item](/manual/api/reference/graphitem/object#graph_item)

en-us	### See also  -   [Graph prototype](/manual/api/reference/graphprototype/object#graph_prototype) -   [Host](/manual/api/reference/host/object#host) -   [Item prototype](/manual/api/reference/itemprototype/object#item_prototype) -   [LLD rule filter](object#lld_rule_filter) -   [Trigger prototype](/manual/api/reference/triggerprototype/object#trigger_prototype)
fa	### همچنین ببینید  -   [Graph prototype](/manual/api/reference/graphprototype/object#graph_prototype) -   [Host](/manual/api/reference/host/object#host) -   [Item prototype](/manual/api/reference/itemprototype/object#item_prototype) -   [LLD rule filter](object#lld_rule_filter) -   [Trigger prototype](/manual/api/reference/triggerprototype/object#trigger_prototype)

en-us	### See also  -   [Group link](object#group_link) -   [Group prototype](object#group_prototype) -   [Host prototype tag](object#host_prototype_tag) -   [Custom interface](object#custom_interface) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro)
fa	###همچنین ببینید  -   [Group link](object#group_link) -   [Group prototype](object#group_prototype) -   [Host prototype tag](object#host_prototype_tag) -   [Custom interface](object#custom_interface) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro)

en-us	### See also  -   [Group link](object#group_link) -   [Group prototype](object#group_prototype) -   [Host prototype tag](object#host_prototype_tag) -   [Custom interface](object#custom_interface) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro)
fa	### همچنین ببینید  -   [Group link](object#group_link) -   [Group prototype](object#group_prototype) -   [Host prototype tag](object#host_prototype_tag) -   [Custom interface](object#custom_interface) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro)

en-us	### See also  -   [Group link](object#group_link) -   [Group prototype](object#group_prototype) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro)
fa	###همچنین ببینید  -   [Group link](object#group_link) -   [Group prototype](object#group_prototype) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro)

en-us	### See also  -   [hostinterface.create](create) -   [host.massadd](/manual/api/reference/host/massadd) -   [Host](/manual/api/reference/host/object#host)
fa	### همچنین ببینید  -   [hostinterface.create](create) -   [host.massadd](/manual/api/reference/host/massadd) -   [Host](/manual/api/reference/host/object#host)

en-us	### See also  -   [hostinterface.delete](delete) -   [host.massremove](/manual/api/reference/host/massremove)
fa	### همچنین ببینید  -   [hostinterface.delete](delete) -   [host.massremove](/manual/api/reference/host/massremove)

en-us	### See also  -   [hostinterface.massadd](massadd) -   [host.massadd](/manual/api/reference/host/massadd)
fa	### همچنین ببینید  -   [hostinterface.massadd](massadd) -   [host.massadd](/manual/api/reference/host/massadd)

en-us	### See also  -   [hostinterface.massremove](massremove) -   [host.massremove](/manual/api/reference/host/massremove)
fa	### همچنین ببینید  -   [hostinterface.massremove](massremove) -   [host.massremove](/manual/api/reference/host/massremove)

en-us	### See also  -   [Host](/manual/api/reference/host/object#host) -   [Item](/manual/api/reference/item/object#item)
fa	###همچنین ببینید   -   [Host](/manual/api/reference/host/object#host) -   [Item](/manual/api/reference/item/object#item)

en-us	### See also  -   [Host](/manual/api/reference/host/object#host) -   [Media type](/manual/api/reference/mediatype/object#media_type) -   [User](/manual/api/reference/user/object#user)
fa	### همچنین ببینید  - [میزبان](/دستی/api/reference/host/object#host) - [نوع رسانه](/دستی/api/reference/mediatype/object#media_type) - [کاربر](/دستی/api/reference/user/object#user)

en-us	### See also  -   [Host](/manual/api/reference/host/object#host) -   [Scenario step](object#scenario_step)
fa	### همچنین ببینید  -   [Host](/manual/api/reference/host/object#host) -   [Scenario step](object#scenario_step)

en-us	### See also  -   [host.update](/manual/api/reference/host/update) -   [host.massupdate](/manual/api/reference/host/massupdate)
fa	### همچنین ببینید  -   [host.update](/manual/api/reference/host/update) -   [host.massupdate](/manual/api/reference/host/massupdate)

en-us	### See also  -   [host.update](update) -   [Host group](/manual/api/reference/hostgroup/object#host_group) -   [Template](/manual/api/reference/template/object#template) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro) -   [Host     interface](/manual/api/reference/hostinterface/object#host_interface)
fa	### همچنین ببینید  -   [host.update](update) -   [Host group](/manual/api/reference/hostgroup/object#host_group) -   [Template](/manual/api/reference/template/object#template) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro) -   [Host     interface](/manual/api/reference/hostinterface/object#host_interface)

en-us	### See also  -   [host.update](update) -   [host.massadd](massadd) -   [host.massremove](massremove) -   [Host group](/manual/api/reference/hostgroup/object#host_group) -   [Template](/manual/api/reference/template/object#host_group) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro) -   [Host     interface](/manual/api/reference/hostinterface/object#host_interface)
fa	### همچنین ببینید   -   [host.update](update) -   [host.massadd](massadd) -   [host.massremove](massremove) -   [Host group](/manual/api/reference/hostgroup/object#host_group) -   [Template](/manual/api/reference/template/object#host_group) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro) -   [Host     interface](/manual/api/reference/hostinterface/object#host_interface)

en-us	### See also  -   [host.update](update) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro) -   [Host     interface](/manual/api/reference/hostinterface/object#host_interface)
fa	### همچنین ببینید  -   [host.update](update) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro) -   [Host     interface](/manual/api/reference/hostinterface/object#host_interface)

en-us	### See also  -   [Icon mapping](object#icon_mapping)
fa	### همچنین ببینید  - [اختصاص آیکون] (آبجکت#اختصاص آیکون)

en-us	### See also  -   [Icon mapping](object#icon_mapping)
fa	### همچنین ببینید  - [اختصاص آیکون] (آبجکت#اختصاص آیکون)

en-us	### See also  -   [Icon mapping](object#icon_mapping)
fa	### همچنین ببینید  - [اختصاص آیکون] (آبجکت#اختصاص آیکون)

en-us	### See also  -   [LLD rule filter](object#lld_rule_filter) -   [LLD macro paths](object#lld_macro_path) -   [LLD rule preprocessing](object#lld_rule_preprocessing)
fa	### همچنین ببینید   -   [LLD rule filter](object#lld_rule_filter) -   [LLD macro paths](object#lld_macro_path) -   [LLD rule preprocessing](object#lld_rule_preprocessing)

en-us	### See also  -   [Scenario step](object#scenario_step)
fa	###همچنین ببینید   -   [Scenario step](object#scenario_step)

en-us	### See also  -   [Scenario step](object#scenario_step)
fa	###همچنین ببینید   -   [Scenario step](object#scenario_step)

en-us	### Source  CAction::create() in *ui/include/classes/api/services/CAction.php*.
fa	### منبع  CAction::create() در *ui/include/classes/api/services/CAction.php*.

en-us	### Source  CAction::delete() in *ui/include/classes/api/services/CAction.php*.
fa	### منبع  CAction::delete() در *ui/include/classes/api/services/CAction.php*.

en-us	### Source  CAction::get() in *ui/include/classes/api/services/CAction.php*.
fa	### منبع  CAction::get() در *ui/include/classes/api/services/CAction.php*.

en-us	### Source  CAction::update() in *ui/include/classes/api/services/CAction.php*.
fa	### منبع  CAction::update() در *ui/include/classes/api/services/CAction.php*.

en-us	### Source  CAlert::get() in *ui/include/classes/api/services/CAlert.php*.
fa	### منبع  CAlert::get() در *ui/include/classes/api/services/CAlert.php*.

en-us	### Source  CAPIInfo::version() in *ui/include/classes/api/services/CAPIInfo.php*.
fa	### منبع  CAPIInfo::version() در *ui/include/classes/api/services/CAPIInfo.php*.

en-us	### Source  CAuditLog::get() in *ui/include/classes/api/services/CAuditLog.php*.
fa	### منبع  CAuditLog::get() در *ui/include/classes/api/services/CAuditLog.php*.

en-us	### Source  CAutoregistration::get() in *ui/include/classes/api/services/CAutoregistration.php*.
fa	### منبع  CIconMap::update() در *ui/include/classes/api/services/CIconMap.php*.

en-us	### Source  CAutoregistration::update() in *ui/include/classes/api/services/CAutoregistration.php*.
fa	### منبع  CIconMap::update() در *ui/include/classes/api/services/CIconMap.php*.

en-us	### Source  CConfiguration::export() in *ui/include/classes/api/services/CConfiguration.php*.
fa	### منبع   CIconMap::update() در *ui/include/classes/api/services/CIconMap.php*.

en-us	### Source  CConfiguration::importcompare() in *ui/include/classes/api/services/CConfiguration.php*.
fa	### منبع   CIconMap::update() در *ui/include/classes/api/services/CIconMap.php*.

en-us	### Source  CConfiguration::import() in *ui/include/classes/api/services/CConfiguration.php*.
fa	### منبع   CIconMap::update() در *ui/include/classes/api/services/CIconMap.php*.

en-us	### Source  CCorrelation::create() in *ui/include/classes/api/services/CCorrelation.php*.
fa	### منبع  CIconMap::update() در *ui/include/classes/api/services/CIconMap.php*.

en-us	### Source  CCorrelation::delete() in *ui/include/classes/api/services/CCorrelation.php*.
fa	### منبع  CCCorrelation::delete() در *ui/include/classes/api/services/CCorrelation.php*.

en-us	### Source  CCorrelation::get() in *ui/include/classes/api/services/CCorrelation.php*.
fa	### منبع  CCorrelation::get() in *ui/include/classes/api/services/CCorrelation.php*.

en-us	### Source  CCorrelation::update() in *ui/include/classes/api/services/CCorrelation.php*.
fa	### منبع  CCCorrelation::update() در *ui/include/classes/api/services/CCorrelation.php*.

en-us	### Source  CDashboard::create() in *ui/include/classes/api/services/CDashboard.php*.
fa	### منبع   CDashboard::create() in *ui/include/classes/api/services/CDashboard.php*.

en-us	### Source  CDashboard::delete() in *ui/include/classes/api/services/CDashboard.php*.
fa	  ### منبع  CDashboard::delete() in *ui/include/classes/api/services/CDashboard.php*.

en-us	### Source  CDashboard::get() in *ui/include/classes/api/services/CDashboard.php*.
fa	### منبع  CDashboard::get() in *ui/include/classes/api/services/CDashboard.php*.

en-us	### Source  CDashboard::update() in *ui/include/classes/api/services/CDashboard.php*.
fa	###  منبع  CDashboard::update() in *ui/include/classes/api/services/CDashboard.php*.

en-us	### Source  CDCheck::get() in *ui/include/classes/api/services/CDCheck.php*.
fa	### منبع  CDCheck::get() in *ui/include/classes/api/services/CDCheck.php*.

en-us	### Source  CDHost::get() in *ui/include/classes/api/services/CDHost.php*.
fa	### منبع  CDHost::get() in *ui/include/classes/api/services/CDHost.php*.

en-us	### Source  CDiscoveryRule::create() in *ui/include/classes/api/services/CDiscoveryRule.php*.
fa	### منبع  CDiscoveryrule::copy() in *ui/include/classes/api/services/CDiscoveryRule.php*.

en-us	### Source  CDiscoveryRule::delete() in *ui/include/classes/api/services/CDiscoveryRule.php*.
fa	### منبع  CDiscoveryrule::copy() in *ui/include/classes/api/services/CDiscoveryRule.php*.

en-us	### Source  CDiscoveryRule::get() in *ui/include/classes/api/services/CDiscoveryRule.php*.
fa	### منبع  CDiscoveryrule::copy() in *ui/include/classes/api/services/CDiscoveryRule.php*.

en-us	### Source  CDiscoveryRule::update() in *ui/include/classes/api/services/CDiscoveryRule.php*.
fa	### منبع  CDiscoveryrule::copy() in *ui/include/classes/api/services/CDiscoveryRule.php*.

en-us	### Source  CDRule::create() in *ui/include/classes/api/services/CDRule.php*.
fa	### منابع  CDRule::create() in *ui/include/classes/api/services/CDRule.php*.

en-us	### Source  CDRule::delete() in *ui/include/classes/api/services/CDRule.php*.
fa	### منبع  CDRule::delete() in *ui/include/classes/api/services/CDRule.php*.

en-us	### Source  CDRule::get() in *ui/include/classes/api/services/CDRule.php*.
fa	### منبع  CDRule::get() in *ui/include/classes/api/services/CDRule.php*.

en-us	### Source  CDRule::update() in *ui/include/classes/api/services/CDRule.php*.
fa	### منبع  CDRule::update() in *ui/include/classes/api/services/CDRule.php*.

en-us	### Source  CDService::get() in *ui/include/classes/api/services/CDService.php*.
fa	### منبع  CDService::get() in *ui/include/classes/api/services/CDService.php*.

en-us	### Source  CEvent::acknowledge() in *ui/include/classes/api/services/CEvent.php*.
fa	### منبع  CEvent::acknowledge() in *ui/include/classes/api/services/CEvent.php*.

en-us	### Source  CEvent::get() in *ui/include/classes/api/services/CEvent.php*.
fa	### منبع   CEvent::get() in *ui/include/classes/api/services/CEvent.php*.

en-us	### Source  CGraph::create() in *ui/include/classes/api/services/CGraph.php*.
fa	منبع

en-us	### Source  CGraph::delete() in *ui/include/classes/api/services/CGraph.php*.
fa	### منبع  CGraph::delete() in *ui/include/classes/api/services/CGraph.php*.

en-us	### Source  CGraph::get() in *ui/include/classes/api/services/CGraph.php*.
fa	### منبع  CGraph::get() in *ui/include/classes/api/services/CGraph.php*.

en-us	### Source  CGraphItem::get() in *ui/include/classes/api/services/CGraphItem.php*.
fa	### منبع CGraphItem::get() in *ui/include/classes/api/services/CGraphItem.php*.

en-us	### Source  CGraphPrototype::create() in *ui/include/classes/api/services/CGraphPrototype.php*.
fa	### منبع  CGraphPrototype::create() in *ui/include/classes/api/services/CGraphPrototype.php*.

en-us	### Source  CGraphPrototype::delete() in *ui/include/classes/api/services/CGraphPrototype.php*.
fa	### منبع  CGraphPrototype::delete() in *ui/include/classes/api/services/CGraphPrototype.php*.

en-us	### Source  CGraphPrototype::get() in *ui/include/classes/api/services/CGraphPrototype.php*.
fa	### منبع  CGraphPrototype::get() in *ui/include/classes/api/services/CGraphPrototype.php*.

en-us	### Source  CGraphPrototype::update() in *ui/include/classes/api/services/CGraphPrototype.php*.
fa	### منبع   CGraphPrototype::update() in *ui/include/classes/api/services/CGraphPrototype.php*.

en-us	### Source  CGraph::update() in *ui/include/classes/api/services/CGraph.php*.
fa	### منبع  CGraph::update() in *ui/include/classes/api/services/CGraph.php*.

en-us	### Source  CHaNode::get() in *ui/include/classes/api/services/CHaNode.php*.
fa	### منبع  CHaNode::get() in *ui/include/classes/api/services/CHaNode.php*.

en-us	### Source  CHistory::clear() in *ui/include/classes/api/services/CHistory.php*.
fa	### منبع  CHistory::clear() in *ui/include/classes/api/services/CHistory.php*.

en-us	### Source  CHistory::get() in *ui/include/classes/api/services/CHistory.php*.
fa	###منبع  CHistory::get() in *ui/include/classes/api/services/CHistory.php*.

en-us	### Source  CHost::create() in *ui/include/classes/api/services/CHost.php*.
fa	### منبع  CHost::create() in *ui/include/classes/api/services/CHost.php*.

en-us	### Source  CHost::delete() in *ui/include/classes/api/services/CHost.php*.
fa	###منبع  CHost::delete() in *ui/include/classes/api/services/CHost.php*.

en-us	### Source  CHost::get() in *ui/include/classes/api/services/CHost.php*.
fa	### منبع  CDHost::get() in *ui/include/classes/api/services/CDHost.php*.

en-us	### Source  CHostGroup::create() in *ui/include/classes/api/services/CHostGroup.php*.
fa	### منبع  CHostGroup::create() in *ui/include/classes/api/services/CHostGroup.php*.

en-us	### Source  CHostGroup::delete() in *ui/include/classes/api/services/CHostGroup.php*.
fa	### منبع  CHostGroup::create() in *ui/include/classes/api/services/CHostGroup.php*.

en-us	### Source  CHostGroup::get() in *ui/include/classes/api/services/CHostGroup.php*.
fa	### منبع  CHostGroup::get() in *ui/include/classes/api/services/CHostGroup.php*.

en-us	### Source  CHostGroup::massAdd() in *ui/include/classes/api/services/CHostGroup.php*.
fa	### منبع  CHostGroup::massAdd() in *ui/include/classes/api/services/CHostGroup.php*.

en-us	### Source  CHostGroup::massRemove() in *ui/include/classes/api/services/CHostGroup.php*.
fa	### منبع  CHostGroup::massRemove() in *ui/include/classes/api/services/CHostGroup.php*.

en-us	### Source  CHostGroup::massUpdate() in *ui/include/classes/api/services/CHostGroup.php*.
fa	### منبع  CHostGroup::massUpdate() in *ui/include/classes/api/services/CHostGroup.php*.

en-us	### Source  CHostGroup::update() in *ui/include/classes/api/services/CHostGroup.php*.
fa	### منبع  CHostGroup::update() in *ui/include/classes/api/services/CHostGroup.php*.

en-us	### Source  CHostInterface::create() in *ui/include/classes/api/services/CHostInterface.php*.
fa	### منبع  CHostInterface::create() in *ui/include/classes/api/services/CHostInterface.php*.

en-us	### Source  CHostInterface::delete() in *ui/include/classes/api/services/CHostInterface.php*.
fa	###منبع  CHostInterface::delete() in *ui/include/classes/api/services/CHostInterface.php*.

en-us	### Source  CHostInterface::get() in *ui/include/classes/api/services/CHostInterface.php*.
fa	### منبع  CHostInterface::get() in *ui/include/classes/api/services/CHostInterface.php*.

en-us	### Source  CHostInterface::massAdd() in *ui/include/classes/api/services/CHostInterface.php*.
fa	### منبع  CHostInterface::massAdd() in *ui/include/classes/api/services/CHostInterface.php*.

en-us	### Source  CHostInterface::massRemove() in *ui/include/classes/api/services/CHostInterface.php*.
fa	### منبع  CHostInterface::massRemove() in *ui/include/classes/api/services/CHostInterface.php*.

en-us	### Source  CHostInterface::replaceHostInterfaces() in *ui/include/classes/api/services/CHostInterface.php*.
fa	### منبع  CHostInterface::replaceHostInterfaces() in *ui/include/classes/api/services/CHostInterface.php*.

en-us	### Source  CHostInterface::update() in *ui/include/classes/api/services/CHostInterface.php*.
fa	### منبع  CHostInterface::update() in *ui/include/classes/api/services/CHostInterface.php*.

en-us	### Source  CHost::massAdd() in *ui/include/classes/api/services/CHost.php*.
fa	### منبع  CHost::massAdd() in *ui/include/classes/api/services/CHost.php*.

en-us	### Source  CHost::massRemove() in *ui/include/classes/api/services/CHost.php*.
fa	### منبع  CHost::massRemove() in *ui/include/classes/api/services/CHost.php*.

en-us	### Source  CHost::massUpdate() in *ui/include/classes/api/services/CHost.php*.
fa	### منبع  CHost::massUpdate() in *ui/include/classes/api/services/CHost.php*.

en-us	### Source  CHostPrototype::create() in *ui/include/classes/api/services/CHostPrototype.php*.
fa	###منبع  CHostPrototype::create() in *ui/include/classes/api/services/CHostPrototype.php*.

en-us	### Source  CHostPrototype::delete() in *ui/include/classes/api/services/CHostPrototype.php*.
fa	### منبع  CHostPrototype::delete() in *ui/include/classes/api/services/CHostPrototype.php*.

en-us	### Source  CHostPrototype::get() in *ui/include/classes/api/services/CHostPrototype.php*.
fa	###منبع  CHostPrototype::get() in *ui/include/classes/api/services/CHostPrototype.php*.

en-us	### Source  CHostPrototype::update() in *ui/include/classes/api/services/CHostPrototype.php*.
fa	### منبع  CHostPrototype::update() in *ui/include/classes/api/services/CHostPrototype.php*.

en-us	### Source  CHost::update() in *ui/include/classes/api/services/CHost.php*.
fa	### منبع  CHost::create() in *ui/include/classes/api/services/CHost.php*.

en-us	### Source  CHousekeeping ::get() in *ui/include/classes/api/services/CHousekeeping.php*.
fa	### منبع  CHousekeeping ::get() in *ui/include/classes/api/services/CHousekeeping.php*.

en-us	### Source  CHousekeeping::update() in *ui/include/classes/api/services/CHousekeeping.php*.
fa	### منبع  CHousekeeping::update() in *ui/include/classes/api/services/CHousekeeping.php*.

en-us	### Source  CHttpTest::create() in *ui/include/classes/api/services/CHttpTest.php*.
fa	### منبع  CHttpTest::create() in *ui/include/classes/api/services/CHttpTest.php*.

en-us	### Source  CHttpTest::delete() in *ui/include/classes/api/services/CHttpTest.php*.
fa	###منبع  CHttpTest::delete() in *ui/include/classes/api/services/CHttpTest.php*.

en-us	### Source  CHttpTest::get() in *ui/include/classes/api/services/CHttpTest.php*.
fa	###منبع   CHttpTest::get() in *ui/include/classes/api/services/CHttpTest.php*.

en-us	### Source  CHttpTest::update() in *ui/include/classes/api/services/CHttpTest.php*.
fa	###منبع  CHttpTest::update() in *ui/include/classes/api/services/CHttpTest.php*.

en-us	### Source  CIconMap::create() in *ui/include/classes/api/services/CIconMap.php*.
fa	### منبع  CIconMap::update() در *ui/include/classes/api/services/CIconMap.php*.

en-us	### Source  CIconMap::delete() in *ui/include/classes/api/services/CIconMap.php*.
fa	###منبع  CIconMap::delete() in *ui/include/classes/api/services/CIconMap.php*.

en-us	### Source  CIconMap::get() in *ui/include/classes/api/services/CIconMap.php*.
fa	### منبع  CIconMap::update() در *ui/include/classes/api/services/CIconMap.php*.

en-us	### Source  CIconMap::update() in *ui/include/classes/api/services/CIconMap.php*.
fa	### منبع  CIconMap::update() در *ui/include/classes/api/services/CIconMap.php*.

en-us	### Source  CImage::create() in *ui/include/classes/api/services/CImage.php*.
fa	### منبع  CImage::create() in *ui/include/classes/api/services/CImage.php*.

en-us	### Source  CScript::create() in *ui/include/classes/api/services/CScript.php*.
fa	### منبع  CIconMap::update() در *ui/include/classes/api/services/CIconMap.php*.

en-us	### Source  CTemplate::create() in *ui/include/classes/api/services/CTemplate.php*.
fa	### منبع  CTemplate::create() in *ui/include/classes/api/services/CTemplate.php*.

en-us	### String history  The string history object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |clock|timestamp|Time when that value was received.| |itemid|string|ID of the related item.| |ns|integer|Nanoseconds when the value was received.| |value|string|Received value.|
fa	### تاریخچه رشته   The string history object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |clock|timestamp|Time when that value was received.| |itemid|string|ID of the related item.| |ns|integer|Nanoseconds when the value was received.| |value|string|Received value.|

en-us	## SYNOPSIS  **zabbix\_agent2** \[**-c** *config-file*\]\ **zabbix\_agent2** \[**-c** *config-file*\] **-p**\ **zabbix\_agent2** \[**-c** *config-file*\] **-t** *item-key*\ **zabbix\_agent2** \[**-c** *config-file*\] **-R** *runtime-option*\ **zabbix\_agent2 -h**\ **zabbix\_agent2 -V**\ \ [ ]{#lbAD}
fa	## خلاصه  **zabbix\_agent2** \[**-c** *config-file*\]\ **zabbix\_agent2** \[**-c** *config-file*\] **-p**\ **zabbix\_agent2** \[**-c** *config-file*\] **-t** *item-key*\ **zabbix\_agent2** \[**-c** *config-file*\] **-R** *runtime-option*\ **zabbix\_agent2 -h**\ **zabbix\_agent2 -V**\ \ [ ]{#lbAD}

en-us	## SYNOPSIS  **zabbix\_agentd** \[**-c** *config-file*\]\ **zabbix\_agentd** \[**-c** *config-file*\] **-p**\ **zabbix\_agentd** \[**-c** *config-file*\] **-t** *item-key*\ **zabbix\_agentd** \[**-c** *config-file*\] **-R** *runtime-option*\ **zabbix\_agentd -h**\ **zabbix\_agentd -V** [ ]{#lbAD}
fa	## خلاصه  **zabbix\_agent2** \[**-c** *config-file*\]\ **zabbix\_agent2** \[**-c** *config-file*\] **-p**\ **zabbix\_agent2** \[**-c** *config-file*\] **-t** *item-key*\ **zabbix\_agent2** \[**-c** *config-file*\] **-R** *runtime-option*\ **zabbix\_agent2 -h**\ **zabbix\_agent2 -V**\ \ [ ]{#lbAD}

en-us	## SYNOPSIS  **zabbix\_get -s** *host-name-or-IP* \[**-p** *port-number*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **-k** *item-key*\ **zabbix\_get -s** *host-name-or-IP* \[**-p** *port-number*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **--tls-connect** **cert** **--tls-ca-file** *CA-file* \[**--tls-crl-file** *CRL-file*\] \[**--tls-agent-cert-issuer** *cert-issuer*\] \[**--tls-agent-cert-subject** *cert-subject*\] **--tls-cert-file** *cert-file* **--tls-key-file** *key-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *item-key*\ **zabbix\_get -s** *host-name-or-IP* \[**-p** *port-number*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **--tls-connect** **psk** **--tls-psk-identity** *PSK-identity* **--tls-psk-file** *PSK-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *item-key*\ **zabbix\_get -h**\ **zabbix\_get -V** [ ]{#lbAD}
fa	## نحوه استفاده  **zabbix\_get -s** *host-name-or-IP* \[**-p** *port-number*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **-k** *item-key*\ **zabbix\_get -s** *host-name-or-IP* \[**-p** *port-number*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **--tls-connect** **cert** **--tls-ca-file** *CA-file* \[**--tls-crl-file** *CRL-file*\] \[**--tls-agent-cert-issuer** *cert-issuer*\] \[**--tls-agent-cert-subject** *cert-subject*\] **--tls-cert-file** *cert-file* **--tls-key-file** *key-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *item-key*\ **zabbix\_get -s** *host-name-or-IP* \[**-p** *port-number*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **--tls-connect** **psk** **--tls-psk-identity** *PSK-identity* **--tls-psk-file** *PSK-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *item-key*\ **zabbix\_get -h**\ **zabbix\_get -V** [ ]{#lbAD}

en-us	## SYNOPSIS  **zabbix\_js -s** *script-file* **-p** *input-param* \[**-l** *log-level*\] \[**-t** *timeout*\]\ **zabbix\_js -s** *script-file* **-i** *input-file* \[**-l** *log-level*\] \[**-t** *timeout*\]\ **zabbix\_js -h**\ **zabbix\_js -V** [ ]{#lbAD}
fa	## خلاصه  **zabbix\_js -s** *اسکریپت-فایل* **-p** *input-param* \[**-l** *log-level*\] \[**-t** *timeout*\]\ **zabbix\_js -s** *script-file* **-i** *input-file* \[**-l** *log-level*\] \[**-t** *timeout*\]\ **zabbix\_js -h**\ **zabbix\_js -V** [ ]{#lbAD}

en-us	## SYNOPSIS  **zabbix\_proxy** \[**-c** *config-file*\]\ **zabbix\_proxy** \[**-c** *config-file*\] **-R** *runtime-option*\ **zabbix\_proxy -h**\ **zabbix\_proxy -V** [ ]{#lbAD}
fa	## خلاصه  **zabbix\_proxy** \[**-c** *config-file*\]\ **zabbix\_proxy** \[**-c** *config-file*\] **-R** *runtime-option*\ **zabbix\_proxy -h**\ **zabbix\_proxy -V** [ ]{#lbAD}

en-us	## SYNOPSIS  **zabbix\_sender** \[**-v**\] **-z** *server* \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **-s** *host* **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-z** *server* \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender** \[**-v**\] **-z** *server* \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **-s** *host* **--tls-connect** **cert** **--tls-ca-file** *CA-file* \[**--tls-crl-file** *CRL-file*\] \[**--tls-server-cert-issuer** *cert-issuer*\] \[**--tls-server-cert-subject** *cert-subject*\] **--tls-cert-file** *cert-file* **--tls-key-file** *key-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-z** *server* \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **cert** **--tls-ca-file** *CA-file* \[**--tls-crl-file** *CRL-file*\] \[**--tls-server-cert-issuer** *cert-issuer*\] \[**--tls-server-cert-subject** *cert-subject*\] **--tls-cert-file** *cert-file* **--tls-key-file** *key-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **cert** **--tls-ca-file** *CA-file* \[**--tls-crl-file** *CRL-file*\] \[**--tls-server-cert-issuer** *cert-issuer*\] \[**--tls-server-cert-subject** *cert-subject*\] **--tls-cert-file** *cert-file* **--tls-key-file** *key-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **cert** **--tls-ca-file** *CA-file* \[**--tls-crl-file** *CRL-file*\] \[**--tls-server-cert-issuer** *cert-issuer*\] \[**--tls-server-cert-subject** *cert-subject*\] **--tls-cert-file** *cert-file* **--tls-key-file** *key-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender** \[**-v**\] **-z** *server* \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **-s** *host* **--tls-connect** **psk** **--tls-psk-identity** *PSK-identity* **--tls-psk-file** *PSK-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-z** *server* \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **psk** **--tls-psk-identity** *PSK-identity* **--tls-psk-file** *PSK-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **psk** **--tls-psk-identity** *PSK-identity* **--tls-psk-file** *PSK-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **psk** **--tls-psk-identity** *PSK-identity* **--tls-psk-file** *PSK-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender -h**\ **zabbix\_sender -V** [ ]{#lbAD}
fa	## خلاصه  **zabbix\_sender** \[**-v**\] **-z** *سرور* \[**-p** *port*\] \[**-I** *آدرس IP*\] \[**-t** *timeout*\] **-s** *host* **-k** *key* **-o** *ارزش*\ **zabbix\_sender** \[**-v**\] **-z** *سرور* \[**-p** *port*\] \[**-I** *آدرس IP*\] \[**-t** *timeout*\] \[**-s** *host*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *آدرس IP*\] \[**-t** *timeout*\] \[**-s** *میزبان*\] **-k** *کلید* **-o** *مقدار*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *آدرس IP*\] \[**-t** *timeout*\] \[**-s** *میزبان*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender** \[**-v**\] **-z** *سرور* \[**-p** *port*\] \[**-I** *آدرس IP*\] \[**-t** *timeout*\] **-s** *host* **--tls-connect** **cert** **--tls-ca-file** *CA-file* \[**--tls-crl-file** *CRL-file*\] \[**--tls-server-cert-issuer** *cert-issuer*\] \[**--tls-server-cert-subject** *cert-subject*\] **--tls-cert-file** *cert-file* **--tls-key-file** *key-file* \[**--tls-cipher13** *رشته رمز*\] \[**--tls-cipher** *cipher-string*\] **-k** *key* **-o** *ارزش*\ **zabbix\_sender** \[**-v**\] **-z** *سرور* \[**-p** *port*\] \[**-I** *آدرس IP*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **cert** **--tls-ca-file** *CA-file* \[**--tls-crl-file** *CRL-file*\] \[**--tls-server-cert-issuer** *cert-issuer*\] \[**--tls-server-cert-subject** *cert-subject*\] **--tls-cert-file** *cert-file* **--tls-key-file** *key-file* \[**--tls-cipher13** *رشته رمزی*\] \[**--tls-cipher** *cipher-string*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *آدرس IP*\] \[**-t** *timeout*\] \[**-s** *میزبان*\] **--tls-connect** **cert** **--tls-ca-file** *CA-file* \[**--tls-crl-file** *CRL-file*\] \[**--tls-server-cert-issuer** *گواهی صادرکننده*\] \[**--tls-server-cert-subject** *cert-subject*\] **--tls-cert-file** *cert-file* **--tls-key-file** *key-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *رشته رمز*\] **-k** *کلید* **-o** *مقدار*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *آدرس IP*\] \[**-t** *timeout*\] \[**-s** *میزبان*\] **--tls-connect** **cert** **--tls-ca-file** *CA-file* \[**--tls-crl-file** *CRL-file*\] \[**--tls-server-cert-issuer** *گواهی صادرکننده*\] \[**--tls-server-cert-subject** *cert-subject*\] **--tls-cert-file** *cert-file* **--tls-key-file** *key-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *رشته رمز*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender** \[**-v**\] **-z** *سرور* \[**-p** *port*\] \[**-I** *آدرس IP*\] \[**-t** *timeout*\] **-s** *host* **--tls-connect** **psk** **--tls-psk-identity** *PSK-identity* **--tls-psk-file** *فایل PSK* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *رشته رمز*\] **-k** *کلید* **-o** *مقدار*\ **zabbix\_sender** \[**-v**\] **-z** *سرور* \[**-p** *port*\] \[**-I** *آدرس IP*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **psk** **--tls-psk-identity** *PSK-identity* **--tls-psk-file** *فایل PSK* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *رشته رمز*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *آدرس IP*\] \[**-t** *timeout*\] \[**-s** *میزبان*\] **--tls-connect** **psk** **--tls-psk-identity** *PSK-identity* **--tls-psk-file** *PSK-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *آدرس IP*\] \[**-t** *timeout*\] \[**-s** *میزبان*\] **--tls-connect** **psk** **--tls-psk-identity** *PSK-identity* **--tls-psk-file** *PSK-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender -h**\ **zabbix\_sender -V** [ ]{#lbAD}

en-us	## SYNOPSIS  **zabbix\_server** \[**-c** *config-file*\]\ **zabbix\_server** \[**-c** *config-file*\] **-R** *runtime-option*\ **zabbix\_server -h**\ **zabbix\_server -V** [ ]{#lbAD}
fa	## خلاصه  **zabbix\_server** \[**-c** *config-file*\]\ **zabbix\_server** \[**-c** *config-file*\] **-R** *runtime-option*\ **zabbix\_server -h**\ **zabbix\_server -V** [ ]{#lbAD}

en-us	## SYNOPSIS  **zabbix\_web\_service** \[**-c** *config-file*\]\ **zabbix\_web\_service -h**\ **zabbix\_web\_service -V** [ ]{#lbAD}
fa	## خلاصه  **zabbix\_web\_service** \[**-c** *config-file*\]\ **zabbix\_web\_service -h**\ **zabbix\_web\_service -V** [ ]{#lbAD}

en-us	# template.create
fa	# ساخت قالب