en-us	# 4 Zabbix agent 2 (UNIX)
tr	### 4 Zabbix agent 2 (UNIX)

en-us	# 5 Installation from containers
tr	# 5 Installation from containers

en-us	# 5 Zabbix agent (Windows)
tr	# 5 Zabbix ajanı(Windows)

en-us	# 6 Mass update
tr	6 Toplu güncelleme

en-us	##### 6 Review and edit configuration files  -   edit the Zabbix agent configuration file     **/usr/local/etc/zabbix\_agentd.conf**  You need to configure this file for every host with zabbix\_agentd installed.  You must specify the Zabbix server **IP address** in the file. Connections from other hosts will be denied.  -   edit the Zabbix server configuration file     **/usr/local/etc/zabbix\_server.conf**  You must specify the database name, user and password (if using any).  The rest of the parameters will suit you with their defaults if you have a small installation (up to ten monitored hosts). You should change the default parameters if you want to maximize the performance of Zabbix server (or proxy) though.  -   if you have installed a Zabbix proxy, edit the proxy configuration     file **/usr/local/etc/zabbix\_proxy.conf**  You must specify the server IP address and proxy hostname (must be known to the server), as well as the database name, user and password (if using any).  ::: noteclassic With SQLite the full path to database file must be specified; DB user and password are not required. :::
tr	##### 6 Review and edit configuration files  -   edit the Zabbix agent configuration file     **/usr/local/etc/zabbix\_agentd.conf**  You need to configure this file for every host with zabbix\_agentd installed.  You must specify the Zabbix server **IP address** in the file. Connections from other hosts will be denied.  -   edit the Zabbix server configuration file     **/usr/local/etc/zabbix\_server.conf**  You must specify the database name, user and password (if using any).  The rest of the parameters will suit you with their defaults if you have a small installation (up to ten monitored hosts). You should change the default parameters if you want to maximize the performance of Zabbix server (or proxy) though.  -   if you have installed a Zabbix proxy, edit the proxy configuration     file **/usr/local/etc/zabbix\_proxy.conf**  You must specify the server IP address and proxy hostname (must be known to the server), as well as the database name, user and password (if using any).  ::: noteclassic With SQLite the full path to database file must be specified; DB user and password are not required. :::

en-us	# 6 Sender
tr	# 6 Sender

en-us	# 6. Zabbix appliance
tr	# 6. Zabbix appliance

en-us	# 7. Configuration  Please use the sidebar to access content in the Configuration section.
tr	# 7. Yapılandırma  Yapılandırma bölümündeki içeriğe erişmek için lütfen kenar çubuğunu kullanın.

en-us	# 7 Get
tr	# 7 Get

en-us	# 7 Notifications
tr	Bildirimler

en-us	##### 7 Start up the daemons  Run zabbix\_server on the server side.      shell> zabbix_server  ::: noteclassic Make sure that your system allows allocation of 36MB (or a bit more) of shared memory, otherwise the server may not start and you will see "Cannot allocate shared memory for <type of cache>." in the server log file. This may happen on FreeBSD, Solaris 8.\. :::  Run zabbix\_agentd on all the monitored machines.      shell> zabbix_agentd  ::: noteclassic Make sure that your system allows allocation of 2MB of shared memory, otherwise the agent may not start and you will see "Cannot allocate shared memory for collector." in the agent log file. This may happen on Solaris 8. :::  If you have installed Zabbix proxy, run zabbix\_proxy.      shell> zabbix_proxy
tr	##### 7 Start up the daemons  Run zabbix\_server on the server side.      shell> zabbix_server  ::: noteclassic Make sure that your system allows allocation of 36MB (or a bit more) of shared memory, otherwise the server may not start and you will see "Cannot allocate shared memory for <type of cache>." in the server log file. This may happen on FreeBSD, Solaris 8.\ :::  Run zabbix\_agentd on all the monitored machines.      shell> zabbix_agentd  ::: noteclassic Make sure that your system allows allocation of 2MB of shared memory, otherwise the agent may not start and you will see "Cannot allocate shared memory for collector." in the agent log file. This may happen on Solaris 8. :::  If you have installed Zabbix proxy, run zabbix\_proxy.      shell> zabbix_proxy

en-us	# 7 Visualization
tr	# 7 Görselleştirme

en-us	# 8 Creating your own theme
tr	# 8 Kendi temanızı oluşturma

en-us	# 8 JS
tr	# 8 JS

en-us	# 8. Service monitoring
tr	# 8. Hizmet izleme

en-us	# 9 Debug mode
tr	# 9 Hata ayıklama modu

en-us	# 9 Templates out of the box
tr	# 9 Kullanıma hazır şablonlar

en-us	# 9. Web monitoring
tr	# 9. Web izleme

en-us	### Access control
tr	### Erişim kontrol

en-us	# action.delete
tr	Eylem silindi

en-us	# action.get
tr	## action.get

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
tr	# Eylem  Bu sınıf, eylemlerle çalışmak üzere tasarlanmıştır.  Nesne referansları:\  - [İşlem](/manual/api/reference/action/object#action) -   [Eylem     durum](/manual/api/reference/action/object#action_condition) -   [Eylem     işlem](/manual/api/reference/action/object#action_operation)  Kullanılabilir yöntemler:\  - [action.create](/manual/api/reference/action/create) - yeni oluştur     hareketler - [action.delete](/manual/api/reference/action/delete) - sil     hareketler - [action.get](/manual/api/reference/action/get) - eylemleri al - [action.update](/manual/api/reference/action/update) - güncelleme     hareketler

en-us	# action.update
tr	# eylem.güncelleme

en-us	#### Agent on UNIX-like systems  Zabbix agent on UNIX-like systems is run on the host being monitored.
tr	#### Agent on UNIX-like systems  Zabbix agent on UNIX-like systems is run on the host being monitored.

en-us	#### Agent on Windows systems  Zabbix agent on Windows runs as a Windows service.
tr	#### Agent on Windows systems  Zabbix agent on Windows runs as a Windows service.

en-us	# alert.get
tr	# uyarı.get

en-us	# > Alert object  The following objects are directly related to the `alert` API.
tr	# > Uyarı nesnesi  Aşağıdaki nesneler doğrudan "alert" API'si ile ilgilidir.

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
tr	# Denetim günlüğü  Bu sınıf, denetim günlüğü ile çalışmak üzere tasarlanmıştır.  Nesne referansları:\  - [Denetim günlüğü nesnesi](/manual/api/reference/auditlog/object)  Kullanılabilir yöntemler:\  - [auditlog.get](/manual/api/reference/auditlog/get) - denetimi geri al     günlük kayıtları

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
tr	# API bilgisi  Bu sınıf, API hakkında meta bilgileri almak için tasarlanmıştır.  Kullanılabilir yöntemler:\  - [apiinfo.version](/manual/api/reference/apiinfo/version) -     Zabbix API sürümünün alınması

en-us	# apiinfo.version
tr	# apiinfo.sürüm

en-us	# Appendix 1. Reference commentary
tr	# Ek 1. Referans açıklama

en-us	# auditlog.get
tr	# denetim günlüğü.get

en-us	# > Audit log object  The following objects are directly related to the `auditlog` API.
tr	# > Denetim günlüğü nesnesi  Aşağıdaki nesneler doğrudan "auditlog" API'si ile ilgilidir.

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
tr	# Denetim günlüğü  Bu sınıf, denetim günlüğü ile çalışmak üzere tasarlanmıştır.  Nesne referansları:\  - [Denetim günlüğü nesnesi](/manual/api/reference/auditlog/object)  Kullanılabilir yöntemler:\  - [auditlog.get](/manual/api/reference/auditlog/get) - denetimi geri al     günlük kayıtları

en-us	# authentication.get
tr	Kimlik Doğrulama

en-us	# > Authentication object  The following objects are directly related to the `authentication` API.
tr	# > Kimlik doğrulama nesnesi  Aşağıdaki nesneler doğrudan "kimlik doğrulama" API'si ile ilgilidir.

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
tr	# Kimlik doğrulama  Bu sınıf, kimlik doğrulama ayarlarıyla çalışmak üzere tasarlanmıştır.  Nesne referansları:\  - [Kimlik Doğrulama](/manual/api/reference/authentication/object#authentication)  Kullanılabilir yöntemler:\  - [authentication.get](/manual/api/reference/authentication/get) -     kimlik doğrulamasını al - [authentication.update](/manual/api/reference/authentication/update) -     kimlik doğrulamasını güncelle

en-us	# authentication.update
tr	# kimlik doğrulama.güncelleme

en-us	## AUTHOR  Alexei Vladishev <<alex@zabbix.com>>  ------------------------------------------------------------------------  [ ]{#index}
tr	## YAZAR  Alexei Vladishev <<alex@zabbix.com>>  -------------------------------------------------- ----------------------  [ ]{#index}

en-us	## AUTHOR  Zabbix LLC  ------------------------------------------------------------------------  [ ]{#index}
tr	## YAZAR  Alexei Vladishev <<alex@zabbix.com>>  -------------------------------------------------- ----------------------  [ ]{#index}

en-us	## AUTHOR  Zabbix LLC  ------------------------------------------------------------------------  [ ]{#index}
tr	## YAZAR  Alexei Vladishev <<alex@zabbix.com>>  -------------------------------------------------- ----------------------  [ ]{#index}

en-us	# autoregistration.get
tr	# otomatik kayıt.güncelleme

en-us	# > Autoregistration object  The following objects are directly related to the `autoregistration` API.
tr	# > Denetim günlüğü nesnesi  Aşağıdaki nesneler doğrudan "auditlog" API'si ile ilgilidir.

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
tr	# Kimlik doğrulama  Bu sınıf, kimlik doğrulama ayarlarıyla çalışmak üzere tasarlanmıştır.  Nesne referansları:\  - [Kimlik Doğrulama](/manual/api/reference/authentication/object#authentication)  Kullanılabilir yöntemler:\  - [authentication.get](/manual/api/reference/authentication/get) -     kimlik doğrulamasını al - [authentication.update](/manual/api/reference/authentication/update) -     kimlik doğrulamasını güncelle

en-us	# autoregistration.update
tr	# otomatik kayıt.güncelleme

en-us	##### Buttons  View mode buttons being common for all sections are described on the [Monitoring](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons) page.
tr	##### Düğmeler  Tüm bölümler için ortak olan görünüm modu düğmeleri, [İzleme](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons) sayfa.

en-us	##### - Changing time zone  By default the appliance uses UTC for the system clock. To change the time zone, copy the appropriate file from */usr/share/zoneinfo* to */etc/localtime*, for example:      cp /usr/share/zoneinfo/Europe/Riga /etc/localtime
tr	##### - Changing time zone  By default the appliance uses UTC for the system clock. To change the time zone, copy the appropriate file from */usr/share/zoneinfo* to */etc/localtime*, for example:      cp /usr/share/zoneinfo/Europe/Riga /etc/localtime

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.
tr	##### 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
tr	# 5 Konfigürasyon

en-us	#### Configuration
tr	#  Konfigürasyon

en-us	# configuration.export
tr	# konfigürasyon.dışa aktarma

en-us	#### Configuration file  For details on configuring Zabbix agent see the configuration file options for [zabbix\_agentd](/manual/appendix/config/zabbix_agentd) or [Windows agent](/manual/appendix/config/zabbix_agentd_win).
tr	#### Configuration file  For details on configuring Zabbix agent see the configuration file options for [zabbix\_agentd](/manual/appendix/config/zabbix_agentd) or [Windows agent](/manual/appendix/config/zabbix_agentd_win).

en-us	##### Configuration file  See the [configuration file](/manual/appendix/config/zabbix_proxy) options for details on configuring zabbix\_proxy.
tr	##### Yapılandırma dosyası  zabbix\_server\'ı yapılandırmayla ilgili ayrıntılar için [yapılandırma dosyası](/manual/appendix/config/zabbix_server) seçeneklerine bakın.

en-us	##### Configuration file  See the [configuration file](/manual/appendix/config/zabbix_server) options for details on configuring zabbix\_server.
tr	##### Configuration file  See the [configuration file](/manual/appendix/config/zabbix_server) options for details on configuring zabbix\_server.

en-us	# configuration.import
tr	Yapılandırma içe aktarma

en-us	# configuration.importcompare
tr	# konfigürasyon.importkarşılaştır

en-us	# connector.delete
tr	# bağlayıcı.delete

en-us	# correlation.create
tr	# korelasyon.oluştur

en-us	# correlation.delete
tr	Korelasyon silindi

en-us	# correlation.get
tr	# korelasyon.getir

en-us	# > Correlation object  The following objects are directly related to the `correlation` API.
tr	# > Korelasyon nesnesi  Aşağıdaki nesneler doğrudan "korelasyon" API'si ile ilgilidir.

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
tr	# Öğe  Bu sınıf, öğelerle çalışmak üzere tasarlanmıştır.  Nesne referansları:\  - [Öğe](/manual/api/reference/item/object#item)  Kullanılabilir yöntemler:\  - [item.create](/manual/api/reference/item/create) - yeni oluşturma     öğeler - [item.delete](/manual/api/reference/item/delete) - öğeleri silme - [item.get](/manual/api/reference/item/get) - öğeleri alma - [item.update](/manual/api/reference/item/update) - öğeleri güncelleme

en-us	# correlation.update
tr	Korelasyon güncellendi

en-us	**CPU**  Zabbix and especially Zabbix database may require significant CPU resources depending on number of monitored parameters and chosen database engine.
tr	**CPU**  Zabbix and especially Zabbix database may require significant CPU resources depending on number of monitored parameters and chosen database engine.

en-us	 # Create a module (tutorial)
tr	 # Bir modül oluşturma (Öğretici)

en-us	### Cryptography
tr	### Kriptografi

en-us	# dashboard.create
tr	Pano oluşturulma

en-us	# dashboard.delete
tr	## dashboard.delete

en-us	# dashboard.get
tr	## dashboard.get

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
tr	# Gösterge Paneli  Bu sınıf, panolarla çalışmak üzere tasarlanmıştır.  Nesne referansları:\  - [Dashboard](/manual/api/reference/dashboard/object#dashboard) -   [Gösterge Paneli     sayfa](/manual/api/reference/dashboard/object#dashboard_page) -   [Gösterge Paneli     widget](/manual/api/reference/dashboard/object#dashboard_widget) - [Gösterge panosu widget'ı     alan](/manual/api/reference/dashboard/object#dashboard_widget_field) -   [Gösterge Paneli     kullanıcı](/manual/api/reference/dashboard/object#dashboard_user) - [Gösterge paneli kullanıcısı     grup](/manual/api/reference/dashboard/object#dashboard_user_group)  Kullanılabilir yöntemler:\  - [dashboard.create](/manual/api/reference/dashboard/create) -     yeni gösterge tabloları oluşturma - [dashboard.delete](/manual/api/reference/dashboard/delete) -     panoları silme - [dashboard.get](/manual/api/reference/dashboard/get) - alma     panolar - [dashboard.update](/manual/api/reference/dashboard/update) -     panoları güncelleme

en-us	# dashboard.update
tr	# kontrol paneli.güncelleme

en-us	#### Data flow  In addition it is important to take a step back and have a look at the overall data flow within Zabbix. In order to create an item that gathers data you must first create a host. Moving to the other end of the Zabbix spectrum you must first have an item to create a trigger. You must have a trigger to create an action. Thus if you want to receive an alert that your CPU load is too high on *Server X* you must first create a host entry for *Server X* followed by an item for monitoring its CPU, then a trigger which activates if the CPU is too high, followed by an action which sends you an email. While that may seem like a lot of steps, with the use of templating it really isn't. However, due to this design it is possible to create a very flexible setup.
tr	#### Data flow  In addition it is important to take a step back and have a look at the overall data flow within Zabbix. In order to create an item that gathers data you must first create a host. Moving to the other end of the Zabbix spectrum you must first have an item to create a trigger. You must have a trigger to create an action. Thus if you want to receive an alert that your CPU load is too high on *Server X* you must first create a host entry for *Server X* followed by an item for monitoring its CPU, then a trigger which activates if the CPU is too high, followed by an action which sends you an email. While that may seem like a lot of steps, with the use of templating it really isn't. However, due to this design it is possible to create a very flexible setup.

en-us	#### Deleting multiple connectors  Delete two connector entries.  [Request](/manual/api#performing-requests):  ```json {     "jsonrpc": "2.0",     "method": "connector.delete",     "params": [         3,         5     ],     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": {         "connectorids": [             "3",             "5"         ]     },     "id": 1 } ```
tr	#### Birden fazla bağlayıcıyı silme  İki bağlayıcı girişini silin.  [İstek](/manual/api#performing-requests):  ```json {     "jsonrpc": "2.0",     "yöntem": "connector.delete",     "parametreler": [         3,         5     ],     "kimlik": 1 } ''''  Cevap:  ```json {     "jsonrpc": "2.0",     "sonuç": {         "konektör kimlikleri": [             "3",             "5"         ]     },     "kimlik": 1 } ''''

en-us	### Description  `object connector.delete(array connectorids)`  This method allows to delete connector entries.  ::: noteclassic This method is only available to *Super admin* user type. Permissions to call the method can be revoked in user role settings. See [User roles](/manual/web_interface/frontend_sections/users/user_roles) for more information. :::
tr	### Tanım  `nesne bağlayıcı.delete(dizi bağlayıcı kimlikleri)`  Bu yöntem bağlayıcı girişlerinin silinmesine olanak tanır.  ::: klasik not Bu yöntem yalnızca *Süper yönetici* kullanıcı türü için geçerlidir. Yöntemi çağırma izinleri kullanıcı rolü ayarlarından iptal edilebilir. Daha fazla bilgi için [Kullanıcı rolleri](/manual/web_interface/frontend_sections/users/user_roles) konusuna bakın. :::

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. :::
tr	### Tanım  `string apiinfo.version(dizi)`  Bu yöntem, Zabbix API sürümünün alınmasına izin verir.  ::: notönemli Bu yöntem yalnızca kimliği doğrulanmamış kullanıcılar için uygun ve JSON-RPC'de "auth" parametresi olmadan çağrılmalıdır.  :::

en-us	## DESCRIPTION  **zabbix\_js** is a command line utility that can be used for embedded script testing. [ ]{#lbAE}
tr	## TANIM  **zabbix\_js**, gömülü olarak kullanılabilen bir komut satırı yardımcı programıdır. komut dosyası testi. [ ]{#lbAE}

en-us	## DESCRIPTION  **zabbix\_server** is the core daemon of Zabbix software. [ ]{#lbAE}
tr	## TANIM  **zabbix\_server**, Zabbix yazılımının temel arka plan programıdır. [ ]{#lbAE}

en-us	## DESCRIPTION  **zabbix\_web\_service** is an application for providing web services to Zabbix components. [ ]{#lbAE}
tr	## TANIM  **zabbix\_web\_service**, aşağıdakilere web hizmetleri sağlamak için bir uygulamadır: Zabbix bileşenleri. [ ]{#lbAE}

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.
tr	#### - 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	### 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.|
tr	### Bulunan sunucu  ::: notklasik Bulunan ana bilgisayar, Zabbix sunucusu tarafından oluşturulur ve API aracılığıyla değiştirilebilir. :::  Bulunan ana bilgisayar nesnesi, keşfedilen bir ana bilgisayar hakkında bilgi içerir. bir ağ bulma kuralı tarafından. Aşağıdaki özelliklere sahiptir.  |Özellik|[Tür](/manual/api/reference_commentary#data_types)|Açıklama| |--|--|------| |dhostid|string|Keşfedilen ana bilgisayarın kimliği.| |druleid|string|Ana bilgisayarı algılayan keşif kuralının kimliği.| |lastdown|timestamp|Keşfedilen sunucunun en son kapatıldığı saat.| |lastup|timestamp|Keşfedilen sunucunun en son yükseldiği saat.| |durum|integer|Keşfedilen ana bilgisayarın açık mı yoksa kapalı mı olduğu. Bir ana bilgisayar, keşfedilen en az bir etkin hizmeti varsa çalışır durumdadır.<br><br>Olası değerler:<br>0 - ana bilgisayar yukarı;<br>1 - ana bilgisayar kapalı.|

en-us	# > Discovered host object  The following objects are directly related to the `dhost` API.
tr	# > Keşfedilen hizmet nesnesi  Aşağıdaki nesneler doğrudan 'dservice' API'si ile ilgilidir.

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
tr	# Keşif kontrolü  Bu sınıf, keşif kontrolleriyle çalışmak üzere tasarlanmıştır.  Nesne referansları:\  - [Keşif     kontrol et](/manual/api/reference/dcheck/object#discovery_check)  Kullanılabilir yöntemler:\  - [dcheck.get](/manual/api/reference/dcheck/get) - keşfi geri al     çekler

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.|
tr	### Keşfedilen hizmet  ::: notklasik Keşfedilen hizmetler Zabbix sunucusu tarafından oluşturulur ve API aracılığıyla değiştirilemez. :::  Keşfedilen hizmet nesnesi, bir hizmet hakkında bilgi içerir. bir ana bilgisayarda bir ağ bulma kuralı tarafından keşfedildi. Aşağıdakilere sahiptir özellikleri.  |Özellik|[Tür](/manual/api/reference_commentary#data_types)|Açıklama| |--|--|------| |dserviceid|string|Keşfedilen hizmetin kimliği.| |dcheckid|string|Hizmeti algılamak için kullanılan keşif denetiminin kimliği.| |dhostid|string|Hizmeti çalıştıran keşfedilen ana bilgisayarın kimliği.| |dns|string|hizmeti çalıştıran ana bilgisayarın DNS'si.| |ip|string|hizmeti çalıştıran ana bilgisayarın IP adresi.| |lastdown|timestamp|Keşfedilen hizmetin en son ne zaman kapandığı.| |lastup|timestamp|Keşfedilen hizmetin en son ne zaman çalıştığı.| |bağlantı noktası|tamsayı|Hizmet bağlantı noktası numarası.| |durum|tamsayı|Hizmetin durumu.<br><br>Olası değerler:<br>0 - hizmet yukarı;<br>1 - hizmet kapalı.| |değer|dize|Bir Zabbix aracısı, SNMPv1, SNMPv2 veya SNMPv3 keşif denetimi gerçekleştirirken hizmet tarafından döndürülen değer.|

en-us	# > Discovered service object  The following objects are directly related to the `dservice` API.
tr	# > Keşfedilen hizmet nesnesi  Aşağıdaki nesneler doğrudan 'dservice' API'si ile ilgilidir.

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
tr	# Keşfedilen hizmet  Bu sınıf, keşfedilen hizmetlerle çalışmak üzere tasarlanmıştır.  Nesne referansları:\  -   [Keşfetti     hizmet](/manual/api/reference/dservice/object#discovered_service)  Kullanılabilir yöntemler:\  - [dservice.get](/manual/api/reference/dservice/get) - al     keşfedilen hizmetler

en-us	#### Discovery actions  The following conditions can be used in discovery-based events:  |Condition type|Supported operators|Description| |--|--|------| |*Host IP*|equals<br>does not equal|Specify an IP address range or a range to exclude for a discovered host.<br>**equals** - host IP is in the range.<br>**does not equal** - host IP is not in the range.<br>It may have the following formats:<br>Single IP: 192.168.1.33<br>Range of IP addresses: 192.168.1-10.1-254<br>IP mask: 192.168.4.0/24<br>List: 192.168.1.1-254, 192.168.2.1-100, 192.168.2.200, 192.168.4.0/24<br>Support for spaces in the list format is provided since Zabbix 3.0.0.| |*Service type*|equals<br>does not equal|Specify a service type of a discovered service or a service type to exclude.<br>**equals** - matches the discovered service.<br>**does not equal** - does not match the discovered service.<br>Available service types: SSH, LDAP, SMTP, FTP, HTTP, HTTPS *(available since Zabbix 2.2 version)*, POP, NNTP, IMAP, TCP, Zabbix agent, SNMPv1 agent, SNMPv2 agent, SNMPv3 agent, ICMP ping, telnet *(available since Zabbix 2.2 version)*.| |*Service port*|equals<br>does not equal|Specify a TCP port range of a discovered service or a range to exclude.<br>**equals** - service port is in the range.<br>**does not equal** - service port is not in the range.| |*Discovery rule*|equals<br>does not equal|Specify a discovery rule or a discovery rule to exclude.<br>**equals** - using this discovery rule.<br>**does not equal** - using any other discovery rule, except this one.| |*Discovery check*|equals<br>does not equal|Specify a discovery check or a discovery check to exclude.<br>**equals** - using this discovery check.<br>**does not equal** - using any other discovery check, except this one.| |*Discovery object*|equals|Specify the discovered object.<br>**equals** - equal to discovered object (a device or a service).| |*Discovery status*|equals|**Up** - matches 'Host Up' and 'Service Up' events.<br>**Down** - matches 'Host Down' and 'Service Down' events.<br>**Discovered** - matches 'Host Discovered' and 'Service Discovered' events.<br>**Lost** - matches 'Host Lost' and 'Service Lost' events.| |*Uptime/Downtime*|is greater than or equals<br>is less than or equals|Uptime for 'Host Up' and 'Service Up' events. Downtime for 'Host Down' and 'Service Down' events.<br>**is greater than or equals** - is more or equal to. Parameter is given in seconds.<br>**is less than or equals** - is less or equal to. Parameter is given in seconds.| |*Received value*|equals<br>does not equal<br>is greater than or equals<br>is less than or equals<br>contains<br>does not contain|Specify the value received from an agent (Zabbix, SNMP) check in a discovery rule. String comparison. If several Zabbix agent or SNMP checks are configured for a rule, received values for each of them are checked (each check generates a new event which is matched against all conditions).<br>**equals** - equal to the value.<br>**does not equal** - not equal to the value.<br>**is greater than or equals** - more or equal to the value.<br>**is less than or equals** - less or equal to the value.<br>**contains** - contains the substring. Parameter is given as a string.<br>**does not contain** - does not contain the substring. Parameter is given as a string.| |*Proxy*|equals<br>does not equal|Specify a proxy or a proxy to exclude.<br>**equals** - using this proxy.<br>**does not equal** - using any other proxy except this one.|  ::: noteclassic Service checks in a discovery rule, which result in discovery events, do not take place simultaneously. Therefore, if **multiple** values are configured for `Service type`, `Service port` or `Received value` conditions in the action, they will be compared to one discovery event at a time, but **not** to several events simultaneously. As a result, actions with multiple values for the same check types may not be executed correctly. :::
tr	#### Discovery actions  The following conditions can be used in discovery-based events:  |Condition type|Supported operators|Description| |--|--|------| |*Host IP*|equals<br>does not equal|Specify an IP address range or a range to exclude for a discovered host.<br>**equals** - host IP is in the range.<br>**does not equal** - host IP is not in the range.<br>It may have the following formats:<br>Single IP: 192.168.1.33<br>Range of IP addresses: 192.168.1-10.1-254<br>IP mask: 192.168.4.0/24<br>List: 192.168.1.1-254, 192.168.2.1-100, 192.168.2.200, 192.168.4.0/24<br>Support for spaces in the list format is provided since Zabbix 3.0.0.| |*Service type*|equals<br>does not equal|Specify a service type of a discovered service or a service type to exclude.<br>**equals** - matches the discovered service.<br>**does not equal** - does not match the discovered service.<br>Available service types: SSH, LDAP, SMTP, FTP, HTTP, HTTPS *(available since Zabbix 2.2 version)*, POP, NNTP, IMAP, TCP, Zabbix agent, SNMPv1 agent, SNMPv2 agent, SNMPv3 agent, ICMP ping, telnet *(available since Zabbix 2.2 version)*.| |*Service port*|equals<br>does not equal|Specify a TCP port range of a discovered service or a range to exclude.<br>**equals** - service port is in the range.<br>**does not equal** - service port is not in the range.| |*Discovery rule*|equals<br>does not equal|Specify a discovery rule or a discovery rule to exclude.<br>**equals** - using this discovery rule.<br>**does not equal** - using any other discovery rule, except this one.| |*Discovery check*|equals<br>does not equal|Specify a discovery check or a discovery check to exclude.<br>**equals** - using this discovery check.<br>**does not equal** - using any other discovery check, except this one.| |*Discovery object*|equals|Specify the discovered object.<br>**equals** - equal to discovered object (a device or a service).| |*Discovery status*|equals|**Up** - matches 'Host Up' and 'Service Up' events<br>**Down** - matches 'Host Down' and 'Service Down' events<br>**Discovered** - matches 'Host Discovered' and 'Service Discovered' events<br>**Lost** - matches 'Host Lost' and 'Service Lost' events| |*Uptime/Downtime*|is greater than or equals<br>is less than or equals|Uptime for 'Host Up' and 'Service Up' events. Downtime for 'Host Down' and 'Service Down' events.<br>**is greater than or equals** - is more or equal to. Parameter is given in seconds.<br>**is less than or equals** - is less or equal to. Parameter is given in seconds.| |*Received value*|equals<br>does not equal<br>is greater than or equals<br>is less than or equals<br>contains<br>does not contain|Specify the value received from an agent (Zabbix, SNMP) check in a discovery rule. String comparison. If several Zabbix agent or SNMP checks are configured for a rule, received values for each of them are checked (each check generates a new event which is matched against all conditions).<br>**equals** - equal to the value.<br>**does not equal** - not equal to the value.<br>**is greater than or equals** - more or equal to the value.<br>**is less than or equals** - less or equal to the value.<br>**contains** - contains the substring. Parameter is given as a string.<br>**does not contain** - does not contain the substring. Parameter is given as a string.| |*Proxy*|equals<br>does not equal|Specify a proxy or a proxy to exclude.<br>**equals** - using this proxy.<br>**does not equal** - using any other proxy except this one.|  ::: noteclassic Service checks in a discovery rule, which result in discovery events, do not take place simultaneously. Therefore, if **multiple** values are configured for `Service type`, `Service port` or `Received value` conditions in the action, they will be compared to one discovery event at a time, but **not** to several events simultaneously. As a result, actions with multiple values for the same check types may not be executed correctly. :::

en-us	# > Discovery check object  The following objects are directly related to the `dcheck` API.
tr	# > Keşfedilen hizmet nesnesi  Aşağıdaki nesneler doğrudan 'dservice' API'si ile ilgilidir.

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
tr	# Keşif kontrolü  Bu sınıf, keşif kontrolleriyle çalışmak üzere tasarlanmıştır.  Nesne referansları:\  - [Keşif     kontrol et](/manual/api/reference/dcheck/object#discovery_check)  Kullanılabilir yöntemler:\  - [dcheck.get](/manual/api/reference/dcheck/get) - keşfi geri al     çekler

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}. :::
tr	##### 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.create
tr	Keşif kuralı oluşturuldu

en-us	# discoveryrule.delete
tr	Keşif kuralları silindi

en-us	# discoveryrule.get
tr	## discoveryrule.get

en-us	# > Discovery rule object  The following objects are directly related to the `drule` API.
tr	# > Keşfedilen hizmet nesnesi  Aşağıdaki nesneler doğrudan 'dservice' API'si ile ilgilidir.

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
tr	# Keşif kuralı  Bu sınıf, ağ bulma kurallarıyla çalışmak üzere tasarlanmıştır.  ::: not ipucu Bu API, ağ bulma kurallarıyla çalışmak içindir. Düşük seviyeli keşif kuralları için [LLD kuralına bakın] API](keşif kuralı). :::  Nesne referansları:\  - [Keşif kuralı](/manual/api/reference/drule/object#discovery_rule)  Kullanılabilir yöntemler:\  - [drule.create](/manual/api/reference/drule/create) - yeni oluştur     keşif kuralları - [drule.delete](/manual/api/reference/drule/delete) - sil     keşif kuralları - [drule.get](/manual/api/reference/drule/get) - keşfi geri al     tüzük - [drule.update](/manual/api/reference/drule/update) - güncelleme     keşif kuralları

en-us	# discoveryrule.update
tr	## discoveryrule.update

en-us	# drule.delete
tr	## drule.delete

en-us	# drule.get
tr	## drule.get

en-us	# drule.update
tr	## drule.update

en-us	# event.acknowledge
tr	Olay onaylandı

en-us	# event.get
tr	## event.get

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.|
tr	### Etkinlik etiketi  Olay etiketi nesnesi aşağıdaki özelliklere sahiptir.  |Özellik|[Tür](/manual/api/reference_commentary#data_types)|Açıklama| |--|--|------| |etiket|dize|Olay etiketi adı.| |değer|dize|Olay etiketi değeri.|

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
tr	# Etkinlik  Bu sınıf, olaylarla çalışmak üzere tasarlanmıştır.  Nesne referansları:\  - [Etkinlik](/manual/api/reference/event/object#host)  Kullanılabilir yöntemler:\  - [event.get](/manual/api/reference/event/get) - olayları alma - [event.acknowledge](/manual/api/reference/event/acknowledge) -     olayları kabul etmek

en-us	### Example
tr	### Örnek

en-us	##### Example 1  Message subject:      Problem: {TRIGGER.NAME}  When you receive the message, the message subject will be replaced by something like:      Problem: Processor load is too high on Zabbix server
tr	##### Örnek 1  Mesaj Konusu:      Sorun: {TRIGGER.NAME}  Mesajı aldığınızda mesaj konusu şu şekilde değiştirilecektir: gibi bir şey:      Sorun: Zabbix sunucusunda işlemci yükü çok yüksek

en-us	##### Example 2  Message:      Processor load is: {?last(/zabbix.zabbix.com/system.cpu.load[,avg1])}  When you receive the message, the message will be replaced by something like:      Processor load is: 1.45
tr	##### Örnek 2  İleti:      İşlemci yükü: {?last(/zabbix.zabbix.com/system.cpu.load[,avg1])}  Mesajı aldığınızda mesajın yerini bir şey alacak beğenmek:      İşlemci yükü: 1,45

en-us	##### Example 3  Message:      Latest value: {?last(/{HOST.HOST}/{ITEM.KEY})}     MAX for 15 minutes: {?max(/{HOST.HOST}/{ITEM.KEY},15m)}     MIN for 15 minutes: {?min(/{HOST.HOST}/{ITEM.KEY},15m)}  When you receive the message, the message will be replaced by something like:      Latest value: 1.45     MAX for 15 minutes: 2.33     MIN for 15 minutes: 1.01
tr	##### Örnek 3  İleti:      En son değer: {?last(/{HOST.HOST}/{ITEM.KEY})}     15 dakika boyunca MAX: {?max(/{HOST.HOST}/{ITEM.KEY},15m)}     15 dakika boyunca MIN: {?min(/{HOST.HOST}/{ITEM.KEY},15m)}  Mesajı aldığınızda mesajın yerini bir şey alacak beğenmek:      Son değer: 1,45     15 dakika boyunca MAX: 2,33     15 dakika boyunca MIN: 1.01

en-us	##### Example 4  Message:      http://<server_ip_or_name>/zabbix/tr_events.php?triggerid={TRIGGER.ID}&eventid={EVENT.ID}  When you receive the message, it will contain a link to the *Event details* page, which provides information about the event, its trigger, and a list of latest events generated by the same trigger.
tr	##### Örnek 4  İleti:      http://<server_ip_or_name>/zabbix/tr_events.php?triggerid={TRIGGER.ID}&eventid={EVENT.ID}  Mesajı aldığınızda, *Etkinliğe bir bağlantı içerecektir. Etkinlik ve tetikleyicisi hakkında bilgi sağlayan ayrıntılar* sayfası, ve aynı tetikleyici tarafından oluşturulan en son olayların bir listesi.

en-us	##### Example 5  Informing about values from several hosts in a trigger expression.  Message:      Problem name: {TRIGGER.NAME}     Trigger expression: {TRIGGER.EXPRESSION}           1. Item value on {HOST.NAME1}: {ITEM.VALUE1} ({ITEM.NAME1})     2. Item value on {HOST.NAME2}: {ITEM.VALUE2} ({ITEM.NAME2})  When you receive the message, the message will be replaced by something like:      Problem name: Processor load is too high on a local host     Trigger expression: last(/Myhost/system.cpu.load[percpu,avg1])>5 or last(/Myotherhost/system.cpu.load[percpu,avg1])>5      1. Item value on Myhost: 0.83 (Processor load (1 min average per core))     2. Item value on Myotherhost: 5.125 (Processor load (1 min average per core))
tr	##### Örnek 5  Bir tetikleyici ifadedeki çeşitli ana bilgisayarlardan gelen değerler hakkında bilgi verme.  İleti:      Sorun adı: {TRIGGER.NAME}     Tetikleyici ifade: {TRIGGER.EXPRESSION}           1. {HOST.NAME1} üzerindeki öğe değeri: {ITEM.VALUE1} ({ITEM.NAME1})     2. {HOST.NAME2} üzerindeki öğe değeri: {ITEM.VALUE2} ({ITEM.NAME2})  Mesajı aldığınızda mesajın yerini bir şey alacak beğenmek:      Sorun adı: Yerel ana bilgisayarda işlemci yükü çok yüksek     Tetikleyici ifade: last(/Myhost/system.cpu.load[percpu,avg1])>5 veya last(/Myotherhost/system.cpu.load[percpu,avg1])>5      1. Myhost'taki öğe değeri: 0,83 (İşlemci yükü (çekirdek başına ortalama 1 dakika))     2. Myotherhost'taki öğe değeri: 5,125 (İşlemci yükü (çekirdek başına ortalama 1 dakika))

en-us	##### Example 6  Receiving details of both the problem event and recovery event in a [recovery](/manual/config/notifications/action/recovery_operations) message:  Message:      Problem:      Event ID: {EVENT.ID}     Event value: {EVENT.VALUE}      Event status: {EVENT.STATUS}      Event time: {EVENT.TIME}     Event date: {EVENT.DATE}     Event age: {EVENT.AGE}     Event acknowledgment: {EVENT.ACK.STATUS}      Event update history: {EVENT.UPDATE.HISTORY}      Recovery:       Event ID: {EVENT.RECOVERY.ID}     Event value: {EVENT.RECOVERY.VALUE}      Event status: {EVENT.RECOVERY.STATUS}      Event time: {EVENT.RECOVERY.TIME}     Event date: {EVENT.RECOVERY.DATE}     Operational data: {EVENT.OPDATA}  When you receive the message, the macros will be replaced by something like:      Problem:      Event ID: 21874     Event value: 1      Event status: PROBLEM      Event time: 13:04:30     Event date: 2018.01.02     Event age: 5m     Event acknowledgment: Yes      Event update history: 2018.01.02 13:05:51 "John Smith (Admin)"     Actions: acknowledged.      Recovery:       Event ID: 21896     Event value: 0      Event status: OK      Event time: 13:10:07     Event date: 2018.01.02     Operational data: Current value is 0.83  ::: noteimportant Separate notification macros for the original problem event and recovery event are supported since Zabbix 2.2.0. :::
tr	##### Örnek 6  Hem sorun olayının hem de kurtarma olayının ayrıntılarını bir [kurtarma](/manual/config/notifications/action/recovery_operations) İleti:  İleti:      Sorun:      Etkinlik Kimliği: {EVENT.ID}     Etkinlik değeri: {EVENT.VALUE}     Etkinlik durumu: {EVENT.STATUS}     Etkinlik zamanı: {EVENT.TIME}     Etkinlik tarihi: {EVENT.DATE}     Etkinlik yaşı: {EVENT.AGE}     Etkinlik onayı: {EVENT.ACK.STATUS}     Etkinlik güncelleme geçmişi: {EVENT.UPDATE.HISTORY}      İyileşmek:      Etkinlik Kimliği: {EVENT.RECOVERY.ID}     Etkinlik değeri: {EVENT.RECOVERY.VALUE}     Etkinlik durumu: {EVENT.RECOVERY.STATUS}     Etkinlik zamanı: {EVENT.RECOVERY.TIME}     Etkinlik tarihi: {EVENT.RECOVERY.DATE}     Operasyonel veriler: {EVENT.OPDATA}  Mesajı aldığınızda makroların yerini bir şey alacak beğenmek:      Sorun:      Olay Kimliği: 21874     Etkinlik değeri: 1     Olay durumu: SORUN     Etkinlik zamanı: 13:04:30     Etkinlik tarihi: 2018.01.02     Etkinlik yaşı: 5m     Etkinlik onayı: Evet     Etkinlik güncelleme geçmişi: 2018.01.02 13:05:51 "John Smith (Yönetici)"     Eylemler: onaylandı.      İyileşmek:      Olay Kimliği: 21896     Etkinlik değeri: 0     Etkinlik durumu: Tamam     Etkinlik zamanı: 13:10:07     Etkinlik tarihi: 2018.01.02     Operasyonel veriler: Mevcut değer 0,83  ::: notönemli Orijinal için ayrı bildirim makroları sorun olayı ve kurtarma olayı Zabbix'ten beri desteklenmektedir 2.2.0. :::

en-us	##### Example configuration for Apache      # ..     ProxyPass "/" http://host/zabbix/     ProxyPassReverse "/" http://host/zabbix/     ProxyPassReverseCookiePath /zabbix /     ProxyPassReverseCookieDomain host zabbix.example.com     # ..
tr	##### Apache için örnek konfigürasyon      # ..     ProxyPass "/" http://host/zabbix/     ProxyPassReverse "/" http://host/zabbix/     ProxyPassReverseCookiePath /zabbix /     ProxyPassReverseCookieDomain host zabbix.example.com     # ..

en-us	##### Example configuration for nginx      # ..     location / {     # ..     proxy_cookie_path /zabbix /;     proxy_pass http://192.168.0.94/zabbix/;     # ..
tr	#####Nginx için örnek konfigürasyon      # ..     location / {     # ..     proxy_cookie_path /zabbix /;     proxy_pass http://192.168.0.94/zabbix/;     # ..

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnek

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	### Examples
tr	### Örnekler

en-us	#### Examples
tr	### Örnekler

en-us	#### Examples
tr	### Örnekler

en-us	#### Examples
tr	### Örnekler

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)`
tr	#### - 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  Examples here illustrate how you can use macros in messages.
tr	#### Örnekler  Buradaki örnekler, mesajlarda makroları nasıl kullanabileceğinizi göstermektedir.

en-us	#### Examples of triggers
tr	#### Tetikleyici örnekleri

en-us	## EXAMPLES  **zabbix\_js -s script-file.js -p example** [ ]{#lbAG}
tr	## ÖRNEKLER  **zabbix\_js -s script-file.js -p örneği** [ ]{#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}
tr	## ÖRNEKLER  **zabbix\_sender -c /etc/zabbix/zabbix\_agentd.conf -k mysql.queries -o 342,45**\     **342.45**'i, izlenen **mysql.queries** öğesi için değer olarak gönderin ev sahibi. Aracıda tanımlanan izlenen ana bilgisayarı ve Zabbix sunucusunu kullanın yapılandırma dosyası.  **zabbix\_sender -c /etc/zabbix/zabbix\_agentd.conf -s "İzlenen Ana Bilgisayar" -k mysql.queries -o 342.45**\     **342.45**'i **Monitored'ın **mysql.queries** öğesi için değer olarak gönderin Ajan yapılandırma dosyasında tanımlanan Zabbix sunucusunu kullanan ana bilgisayar**.  \ **zabbix\_sender -z 192.168.1.113 -i data\_values.txt**     \ **data\_values.txt** dosyasındaki değerleri IP ile Zabbix sunucusuna gönderin **192.168.1.113**. Ana bilgisayar adları ve anahtarları dosyada tanımlanır.  \ **yankı "- hw.serial.number 1287872261 SQ4321ASDF" | zabbix\_sender -c /usr/local/etc/zabbix\_agentd.conf -T -i -**\     Komut satırından Zabbix sunucusuna zaman damgalı bir değer gönderin, aracı yapılandırma dosyasında belirtilir. Giriş verilerinde kısa çizgi ana bilgisayar adının da aynı yapılandırmadan kullanılması gerektiğini belirtir dosya.  \ **echo '"Zabbax sunucusu" trapper.item ""' | zabbix\_sender -z 192.168.1.113 -p 10000 -i -**\     IP adresi ile Zabbix sunucusuna bir öğenin boş değerini gönder **192.168.1.113**, komut satırından **10000** bağlantı noktasında. Boş değerler boş çift tırnak ile belirtilmelidir.  **zabbix\_sender -z 192.168.1.113 -s "İzlenen Ana Bilgisayar" -k mysql.queries -o 342.45 --tls-bağlantı sertifikası --tls-ca-dosyası /home/zabbix/zabbix\_ca\_file --tls-cert-file /home/zabbix/zabbix\_agentd.crt --tls-key-file /home/zabbix/zabbix\_agentd.key**\     **İzlenen içindeki **mysql.queries** öğesi için değer olarak **342.45** gönderin Ana bilgisayar** ana bilgisayardan sunucuya IP **192.168.1.113** ile TLS kullanarak sertifika.  **zabbix\_sender -z 192.168.1.113 -s "İzlenen Ana Bilgisayar" -k mysql.queries -o 342.45 --tls-connect psk --tls-psk-kimliği "PSK ID Zabbix aracısı" --tls-psk dosyası /home/zabbix/zabbix\_agentd.psk**\     **İzlenen içindeki **mysql.queries** öğesi için değer olarak **342.45** gönderin Ana bilgisayar** ana bilgisayardan sunucuya IP **192.168.1.113** ile TLS kullanarak önceden paylaşılan anahtar (PSK).  [ ]{#lbAI}

en-us	#### Exit code  Before version 2.2 Zabbix agent returned 0 in case of successful exit and 255 in case of failure. Starting from version 2.2 and higher Zabbix agent returns 0 in case of successful exit and 1 in case of failure.
tr	#### Exit code  Before version 2.2 Zabbix agent returned 0 in case of successful exit and 255 in case of failure. Starting from version 2.2 and higher Zabbix agent returns 0 in case of successful exit and 1 in case of failure.

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}
tr	## ÇIKIŞ DURUMU  Değerler gönderildiyse ve hepsi gönderildiyse çıkış durumu 0'dır. sunucu tarafından başarıyla işlendi. Veri gönderildiyse, ancak işleniyorsa değerlerden en az biri başarısız, çıkış durumu 2'dir. başarısız, çıkış durumu 1'dir.  [ ]{#lbAH}

en-us	##### - File locations  -   Configuration files are located in **/etc/zabbix**. -   Zabbix server, proxy and agent logfiles are located in     **/var/log/zabbix**. -   Zabbix frontend is located in **/usr/share/zabbix**. -   Home directory for the user **zabbix** is **/var/lib/zabbix**.
tr	##### - File locations  -   Configuration files are located in **/etc/zabbix**. -   Zabbix server, proxy and agent logfiles are located in     **/var/log/zabbix**. -   Zabbix frontend is located in **/usr/share/zabbix**. -   Home directory for the user **zabbix** is **/var/lib/zabbix**.

en-us	## FILES  */usr/local/etc/zabbix\_agent2.conf*   Default location of Zabbix agent 2 configuration file (if not modified during compile time).  [ ]{#lbAH}
tr	## DOSYALAR  */usr/local/etc/zabbix\_web\_service.conf* Zabbix web hizmeti yapılandırma dosyasının varsayılan konumu (eğer değilse derleme süresi sırasında değiştirildi).  [ ]{#lbAG}

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}
tr	## DOSYALAR  */usr/local/etc/zabbix\_web\_service.conf* Zabbix web hizmeti yapılandırma dosyasının varsayılan konumu (eğer değilse derleme süresi sırasında değiştirildi).  [ ]{#lbAG}

en-us	##### - Firewall configuration  The appliance uses iptables firewall with predefined rules:  -   Opened SSH port (22 TCP); -   Opened Zabbix agent (10050 TCP) and Zabbix trapper (10051 TCP)     ports; -   Opened HTTP (80 TCP) and HTTPS (443 TCP) ports; -   Opened SNMP trap port (162 UDP); -   Opened outgoing connections to NTP port (53 UDP); -   ICMP packets limited to 5 packets per second; -   All other incoming connections are dropped.
tr	##### - Firewall configuration  The appliance uses iptables firewall with predefined rules:  -   Opened SSH port (22 TCP); -   Opened Zabbix agent (10050 TCP) and Zabbix trapper (10051 TCP)     ports; -   Opened HTTP (80 TCP) and HTTPS (443 TCP) ports; -   Opened SNMP trap port (162 UDP); -   Opened outgoing connections to NTP port (53 UDP); -   ICMP packets limited to 5 packets per second; -   All other incoming connections are dropped.

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.
tr	##### Dipnotlar  ^**1**^ Dizi değerleri için yalnızca dizi dışa aktarılacaktır (örn. "EMAIL") bu tabloda kullanılan numaralandırma olmadan. Aralık için sayılar Bu tablodaki değerler (API değerlerine karşılık gelen) aşağıdakiler için kullanılır: sadece sipariş

en-us	#### Getting Java gateway  You can install Java gateway either from the sources or packages downloaded from [Zabbix website](http://www.zabbix.com/download.php).  Using the links below you can access information how to get and run Zabbix Java gateway, how to configure Zabbix server (or Zabbix proxy) to use Zabbix Java gateway for JMX monitoring, and how to configure Zabbix items in Zabbix frontend that correspond to particular JMX counters.  |Installation from|Instructions|Instructions| |-----------------|------------|------------| |*Sources*|[Installation](/manual/installation/install#installing_java_gateway)|[Setup](/manual/concepts/java/from_sources)| |*RHEL packages*|[Installation](/manual/installation/install_from_packages/rhel#java_gateway_installation)|[Setup](/manual/concepts/java/from_rhel)| |*Debian/Ubuntu packages*|[Installation](/manual/installation/install_from_packages/debian_ubuntu#java_gateway_installation)|[Setup](/manual/concepts/java/from_debian_ubuntu)|
tr	#### Getting Java gateway  You can install Java gateway either from the sources or packages downloaded from [Zabbix website](http://www.zabbix.com/download.php).  Using the links below you can access information how to get and run Zabbix Java gateway, how to configure Zabbix server (or Zabbix proxy) to use Zabbix Java gateway for JMX monitoring, and how to configure Zabbix items in Zabbix frontend that correspond to particular JMX counters.  |Installation from|Instructions|Instructions| |-----------------|------------|------------| |*Sources*|[Installation](/manual/installation/install#installing_java_gateway)|[Setup](/manual/concepts/java/from_sources)| |*RHEL packages*|[Installation](/manual/installation/install_from_packages/rhel#java_gateway_installation)|[Setup](/manual/concepts/java/from_rhel)| |*Debian/Ubuntu packages*|[Installation](/manual/installation/install_from_packages/debian_ubuntu#java_gateway_installation)|[Setup](/manual/concepts/java/from_debian_ubuntu)|

en-us	#### Getting Zabbix source code  There are several ways of getting Zabbix source code:  -   You can [download](https://www.zabbix.com/download_sources) the     released stable versions from the official Zabbix website -   You can [download](https://www.zabbix.com/developers) nightly builds     from the official Zabbix website developer page -   You can get the latest development version from the Git source code     repository system:     -   The primary location of the full repository is at         <https://git.zabbix.com/scm/zbx/zabbix.git>     -   Master and supported releases are also mirrored to Github at         <https://github.com/zabbix/zabbix>  A Git client must be installed to clone the repository. The official commandline Git client package is commonly called **git** in distributions. To install, for example, on Debian/Ubuntu, run:      sudo apt-get update     sudo apt-get install git  To grab all Zabbix source, change to the directory you want to place the code in and execute:      git clone https://git.zabbix.com/scm/zbx/zabbix.git
tr	#### Zabbix kaynak kodunu alma  Zabbix kaynak kodunu almanın birkaç yolu vardır:  - [İndirebilirsin](https://www.zabbix.com/download_sources)     resmi Zabbix web sitesinden kararlı sürümler yayınlandı - Gecelik derlemeleri [indirebilirsiniz](https://www.zabbix.com/developers)     resmi Zabbix web sitesi geliştirici sayfasından - En son geliştirme sürümünü Git kaynak kodundan alabilirsiniz.     depo sistemi:     - Tam havuzun birincil konumu şu adrestedir:         <https://git.zabbix.com/scm/zbx/zabbix.git>     - Master ve desteklenen sürümler ayrıca şu adreste Github'a yansıtılır:         <https://github.com/zabbix/zabbix>  Depoyu klonlamak için bir Git istemcisi kurulmalıdır. Resmi komut satırı Git istemci paketi genellikle **git** olarak adlandırılır. dağıtımlar. Örneğin, Debian/Ubuntu'ya yüklemek için şunu çalıştırın:      sudo apt-get güncellemesi     sudo apt-get kurulum git  Tüm Zabbix kaynağını almak için, yerleştirmek istediğiniz dizine geçin. kodlayın ve çalıştırın:      git klonu https://git.zabbix.com/scm/zbx/zabbix.git

en-us	# graph.create
tr	## graph.create

en-us	# graph.delete
tr	# grafik.sil

en-us	# graph.get
tr	# grafik.get

en-us	# graphitem.get
tr	## graphitem.get

en-us	# > Graph item object  The following objects are directly related to the `graphitem` API.
tr	# > Grafik öğesi nesnesi  Aşağıdaki nesneler doğrudan "grafik" API'si ile ilgilidir.

en-us	# > Graph object  The following objects are directly related to the `graph` API.
tr	# > Grafik öğesi nesnesi  Aşağıdaki nesneler doğrudan "grafik" API'si ile ilgilidir.

en-us	# graphprototype.create
tr	## graphprototype.create

en-us	# graphprototype.get
tr	# graphprototype.get

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
tr	# Öğe  Bu sınıf, öğelerle çalışmak üzere tasarlanmıştır.  Nesne referansları:\  - [Öğe](/manual/api/reference/item/object#item)  Kullanılabilir yöntemler:\  - [item.create](/manual/api/reference/item/create) - yeni oluşturma     öğeler - [item.delete](/manual/api/reference/item/delete) - öğeleri silme - [item.get](/manual/api/reference/item/get) - öğeleri alma - [item.update](/manual/api/reference/item/update) - öğeleri güncelleme

en-us	# graphprototype.update
tr	## graphprototype.update

en-us	# graph.update
tr	# grafik.güncelleme

en-us	# hanode.get
tr	#hanode.get

en-us	#### Hardware
tr	#### Hardware

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.
tr	##### 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.
tr	# > Yüksek kullanılabilirlikli düğüm nesnesi  Aşağıdaki nesne, bir Yüksek Kullanılabilirlik kümesinin çalıştırılmasıyla ilgilidir. Zabbix sunucularının sayısı.

en-us	# history.clear
tr	# history.clear

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. :::
tr	# > Geçmiş nesnesi  Aşağıdaki nesneler doğrudan "geçmiş" API'si ile ilgilidir.  ::: notklasik Geçmiş nesneleri, öğenin türüne bağlı olarak farklılık gösterir. bilgi. Zabbix sunucusu tarafından oluşturulurlar ve değiştirilemezler. API aracılığıyla değiştirildi. :::

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.
tr	# Keşif kontrolü  Bu sınıf, keşif kontrolleriyle çalışmak üzere tasarlanmıştır.  Nesne referansları:\  - [Keşif     kontrol et](/manual/api/reference/dcheck/object#discovery_check)  Kullanılabilir yöntemler:\  - [dcheck.get](/manual/api/reference/dcheck/get) - keşfi geri al     çekler

en-us	# host.create
tr	## host.create

en-us	# host.delete
tr	## host.delete

en-us	# host.get
tr	# host.get

en-us	# hostgroup.delete
tr	## hostgroup.delete

en-us	# hostgroup.get
tr	## hostgroup.get

en-us	# hostgroup.massadd
tr	## hostgroup.massadd

en-us	# hostgroup.massremove
tr	## hostgroup.massremove

en-us	# hostgroup.massupdate
tr	# hostgroup.massupdate

en-us	# > Host group object  The following objects are directly related to the `hostgroup` API.
tr	# > Ana bilgisayar grubu nesnesi  Aşağıdaki nesneler doğrudan "ana bilgisayar grubu" API'si ile ilgilidir.

en-us	# hostgroup.update
tr	# ana bilgisayar grubu.güncelleme

en-us	# hostinterface.create
tr	## hostinterface.create

en-us	# hostinterface.get
tr	## hostinterface.get

en-us	# hostinterface.massadd
tr	## hostinterface.massadd

en-us	# hostinterface.massremove
tr	#hostinterface.massremove

en-us	# hostinterface.replacehostinterfaces
tr	## hostinterface.replacehostinterfaces

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
tr	# Ana grup  Bu sınıf, ana bilgisayar gruplarıyla çalışmak üzere tasarlanmıştır.  Nesne referansları:\  - [Ana grup](/manual/api/reference/hostgroup/object#host_group)  Kullanılabilir yöntemler:\  - [hostgroup.create](/manual/api/reference/hostgroup/create) -     yeni ana bilgisayar grupları oluşturma - [hostgroup.delete](/manual/api/reference/hostgroup/delete) -     ana bilgisayar gruplarını silme - [hostgroup.get](/manual/api/reference/hostgroup/get) - alma     ev sahibi gruplar - [hostgroup.massadd](/manual/api/reference/hostgroup/massadd) -     ana bilgisayar gruplarına ilgili nesneler ekleme - [hostgroup.massremove](/manual/api/reference/hostgroup/massremove) -     ilgili nesneleri ana bilgisayar gruplarından kaldırma - [hostgroup.massupdate](/manual/api/reference/hostgroup/massupdate) -     ilgili nesneleri ana bilgisayar gruplarından değiştirme veya kaldırma - [hostgroup.update](/manual/api/reference/hostgroup/update) -     ana bilgisayar gruplarını güncelleme

en-us	# host.massadd
tr	## host.massadd

en-us	# host.massupdate
tr	# host.massupdate

en-us	# hostprototype.create
tr	## hostprototype.create

en-us	# hostprototype.delete
tr	## hostprototype.delete

en-us	# hostprototype.get
tr	## hostprototype.get

en-us	# > Host prototype object  The following objects are directly related to the `hostprototype` API.
tr	# > Ana bilgisayar grubu nesnesi  Aşağıdaki nesneler doğrudan "ana bilgisayar grubu" API'si ile ilgilidir.

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
tr	# Öğe protptipi  Bu sınıf, öğelerle çalışmak üzere tasarlanmıştır.  Nesne referansları:\  - [Öğe](/manual/api/reference/item/object#item)  Kullanılabilir yöntemler:\  - [item.create](/manual/api/reference/item/create) - yeni oluşturma     öğeler - [item.delete](/manual/api/reference/item/delete) - öğeleri silme - [item.get](/manual/api/reference/item/get) - öğeleri alma - [item.update](/manual/api/reference/item/update) - öğeleri güncelleme

en-us	# hostprototype.update
tr	Ana makine prototipi güncellendi

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
tr	# Ana grup  Bu sınıf, ana bilgisayar gruplarıyla çalışmak üzere tasarlanmıştır.  Nesne referansları:\  - [Ana grup](/manual/api/reference/hostgroup/object#host_group)  Kullanılabilir yöntemler:\  - [hostgroup.create](/manual/api/reference/hostgroup/create) -     yeni ana bilgisayar grupları oluşturma - [hostgroup.delete](/manual/api/reference/hostgroup/delete) -     ana bilgisayar gruplarını silme - [hostgroup.get](/manual/api/reference/hostgroup/get) - alma     ev sahibi gruplar - [hostgroup.massadd](/manual/api/reference/hostgroup/massadd) -     ana bilgisayar gruplarına ilgili nesneler ekleme - [hostgroup.massremove](/manual/api/reference/hostgroup/massremove) -     ilgili nesneleri ana bilgisayar gruplarından kaldırma - [hostgroup.massupdate](/manual/api/reference/hostgroup/massupdate) -     ilgili nesneleri ana bilgisayar gruplarından değiştirme veya kaldırma - [hostgroup.update](/manual/api/reference/hostgroup/update) -     ana bilgisayar gruplarını güncelleme

en-us	# host.update
tr	## host.update

en-us	# housekeeping.update
tr	## housekeeping.update

en-us	# httptest.delete
tr	## httptest.delete

en-us	# httptest.get
tr	# httptest.get

en-us	# httptest.update
tr	## httptest.update

en-us	# iconmap.create
tr	## iconmap.create

en-us	# iconmap.delete
tr	## iconmap.delete

en-us	# iconmap.get
tr	## iconmap.get

en-us	# iconmap.update
tr	## iconmap.update

en-us	##### If installed as package  Zabbix agent runs as a daemon process. The agent can be started by executing:      shell> service zabbix-agent start  This will work on most of GNU/Linux systems. On other systems you may need to run:      shell> /etc/init.d/zabbix-agent start  Similarly, for stopping/restarting/viewing status of Zabbix agent, use the following commands:      shell> service zabbix-agent stop     shell> service zabbix-agent restart     shell> service zabbix-agent status
tr	##### If installed as package  Zabbix agent runs as a daemon process. The agent can be started by executing:      shell> service zabbix-agent start  This will work on most of GNU/Linux systems. On other systems you may need to run:      shell> /etc/init.d/zabbix-agent start  Similarly, for stopping/restarting/viewing status of Zabbix agent, use the following commands:      shell> service zabbix-agent stop     shell> service zabbix-agent restart     shell> service zabbix-agent status

en-us	##### If installed as package  Zabbix proxy runs as a daemon process. The proxy can be started by executing:      shell> service zabbix-proxy start  This will work on most of GNU/Linux systems. On other systems you may need to run:      shell> /etc/init.d/zabbix-proxy start  Similarly, for stopping/restarting/viewing status of Zabbix proxy, use the following commands:      shell> service zabbix-proxy stop     shell> service zabbix-proxy restart     shell> service zabbix-proxy status
tr	##### If installed as package  Zabbix proxy runs as a daemon process. The proxy can be started by executing:      shell> service zabbix-proxy start  This will work on most of GNU/Linux systems. On other systems you may need to run:      shell> /etc/init.d/zabbix-proxy start  Similarly, for stopping/restarting/viewing status of Zabbix proxy, use the following commands:      shell> service zabbix-proxy stop     shell> service zabbix-proxy restart     shell> service zabbix-proxy status

en-us	##### If installed as package  Zabbix server runs as a daemon process. The server can be started by executing:      shell> service zabbix-server start  This will work on most of GNU/Linux systems. On other systems you may need to run:      shell> /etc/init.d/zabbix-server start  Similarly, for stopping/restarting/viewing status, use the following commands:      shell> service zabbix-server stop     shell> service zabbix-server restart     shell> service zabbix-server status
tr	##### If installed as package  Zabbix server runs as a daemon process. The server can be started by executing:      shell> service zabbix-server start  This will work on most of GNU/Linux systems. On other systems you may need to run:      shell> /etc/init.d/zabbix-server start  Similarly, for stopping/restarting/viewing status, use the following commands:      shell> service zabbix-server stop     shell> service zabbix-server restart     shell> service zabbix-server status

en-us	# image.delete
tr	## image.delete

en-us	# image.get
tr	## image.get

en-us	# > Image object  The following objects are directly related to the `image` API.
tr	# > Görüntü nesnesi  Aşağıdaki nesneler, "image" API'si ile doğrudan ilişkilidir.

en-us	# Image  This class is designed to work with images.  Object references:\  -   [Image](/manual/api/reference/image/object#image)  Available methods:\  -   [image.create](/manual/api/reference/image/create) - create new     images -   [image.delete](/manual/api/reference/image/delete) - delete images -   [image.get](/manual/api/reference/image/get) - retrieve images -   [image.update](/manual/api/reference/image/update) - update images
tr	# Resim  Bu sınıf, görüntülerle çalışmak üzere tasarlanmıştır.  Nesne referansları:\  - [Resim](/manual/api/reference/image/object#image)  Kullanılabilir yöntemler:\  - [image.create](/manual/api/reference/image/create) - yeni oluştur     Görüntüler - [image.delete](/manual/api/reference/image/delete) - resimleri sil - [image.get](/manual/api/reference/image/get) - görüntüleri al - [image.update](/manual/api/reference/image/update) - resimleri güncelleyin

en-us	# image.update
tr	## image.update

en-us	##### Installation  After this is done use the following command to install Zabbix agent as Windows service:      C:\> c:\zabbix\zabbix_agentd.exe -c c:\zabbix\zabbix_agentd.conf -i  Now you should be able to configure "Zabbix agent" service normally as any other Windows service.  See [more details](/manual/appendix/install/windows_agent#installing_agent_as_windows_service) on installing and running Zabbix agent on Windows.
tr	##### Installation  After this is done use the following command to install Zabbix agent as Windows service:      C:\> c:\zabbix\zabbix_agentd.exe -c c:\zabbix\zabbix_agentd.conf -i  Now you should be able to configure "Zabbix agent" service normally as any other Windows service.  See [more details](/manual/appendix/install/windows_agent#installing_agent_as_windows_service) on installing and running Zabbix agent on Windows.

en-us	##### Installation  See the [package installation](/manual/installation/install_from_packages) section for instructions on how to install Zabbix agent as package.  Alternatively see instructions for [manual installation](/manual/installation/install#installing_zabbix_daemons) if you do not want to use packages.  ::: noteimportant In general, 32bit Zabbix agents will work on 64bit systems, but may fail in some cases. :::
tr	##### Installation  See the [package installation](/manual/installation/install_from_packages) section for instructions on how to install Zabbix agent as package.  Alternatively see instructions for [manual installation](/manual/installation/install#installing_zabbix_daemons) if you do not want to use packages.  ::: noteimportant In general, 32bit Zabbix agents will work on 64bit systems, but may fail in some cases. :::

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.
tr	#### 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	#### - Installing Zabbix daemons
tr	#### - Installing Zabbix daemons

en-us	#### - Installing Zabbix web interface
tr	#### - Installing Zabbix web interface

en-us	#### Internal event actions  The following conditions can be set for actions based on internal events:  |Condition type|Supported operators|Description| |--|--|------| |*Event type*|equals|**Item in "not supported" state** - matches events where an item goes from a 'normal' to 'not supported' state.<br>**Low-level discovery rule in "not supported" state** - matches events where a low-level discovery rule goes from a 'normal' to 'not supported' state.<br>**Trigger in "unknown" state** - matches events where a trigger goes from a 'normal' to 'unknown' state.| |*Host group*|equals<br>does not equal|Specify host groups or host groups to exclude.<br>**equals** - event belongs to this host group.<br>**does not equal** - event does not belong to this host group.| |*Tag name*|equals<br>does not equal<br>contains<br>does not contain|Specify event tag or event tag to exclude.<br>**equals** - event has this tag.<br>**does not equal** - event does not have this tag.<br>**contains** - event has a tag containing this string.<br>**does not contain** - event does not have a tag containing this string.| |*Tag value*|equals<br>does not equal<br>contains<br>does not contain|Specify event tag and value combination or tag and value combination to exclude.<br>**equals** - event has this tag and value.<br>**does not equal** - event does not have this tag and value.<br>**contains** - event has a tag and value containing these strings.<br>**does not contain** - event does not have a tag and value containing these strings.| |*Template*|equals<br>does not equal|Specify templates or templates to exclude.<br>**equals** - event belongs to an item/trigger/low-level discovery rule inherited from this template.<br>**does not equal** - event does not belong to an item/trigger/low-level discovery rule inherited from this template.| |*Host*|equals<br>does not equal|Specify hosts or hosts to exclude.<br>**equals** - event belongs to this host.<br>**does not equal** - event does not belong to this host.|
tr	#### Internal event actions  The following conditions can be set for actions based on internal events:  |Condition type|Supported operators|Description| |--|--|------| |*Event type*|equals|**Item in "not supported" state** - matches events where an item goes from a 'normal' to 'not supported' state<br>**Low-level discovery rule in "not supported" state** - matches events where a low-level discovery rule goes from a 'normal' to 'not supported' state<br>**Trigger in "unknown" state** - matches events where a trigger goes from a 'normal' to 'unknown' state| |*Host group*|equals<br>does not equal|Specify host groups or host groups to exclude.<br>**equals** - event belongs to this host group.<br>**does not equal** - event does not belong to this host group.| |*Tag name*|equals<br>does not equal<br>contains<br>does not contain|Specify event tag or event tag to exclude.<br>**equals** - event has this tag<br>**does not equal** - event does not have this tag<br>**contains** - event has a tag containing this string<br>**does not contain** - event does not have a tag containing this string| |*Tag value*|equals<br>does not equal<br>contains<br>does not contain|Specify event tag and value combination or tag and value combination to exclude.<br>**equals** - event has this tag and value<br>**does not equal** - event does not have this tag and value<br>**contains** - event has a tag and value containing these strings<br>**does not contain** - event does not have a tag and value containing these strings| |*Template*|equals<br>does not equal|Specify templates or templates to exclude.<br>**equals** - event belongs to an item/trigger/low-level discovery rule inherited from this template.<br>**does not equal** - event does not belong to an item/trigger/low-level discovery rule inherited from this template.| |*Host*|equals<br>does not equal|Specify hosts or hosts to exclude.<br>**equals** - event belongs to this host.<br>**does not equal** - event does not belong to this host.|

en-us	# item.create
tr	## item.create

en-us	# item.delete
tr	## item.delete

en-us	# item.get
tr	## item.get

en-us	# itemprototype.delete
tr	## itemprototype.delete

en-us	# itemprototype.get
tr	## itemprototype.get

en-us	# itemprototype.update
tr	## itemprototype.update

en-us	# Item  This class is designed to work with items.  Object references:\  -   [Item](/manual/api/reference/item/object#item)  Available methods:\  -   [item.create](/manual/api/reference/item/create) - creating new     items -   [item.delete](/manual/api/reference/item/delete) - deleting items -   [item.get](/manual/api/reference/item/get) - retrieving items -   [item.update](/manual/api/reference/item/update) - updating items
tr	# Öğe  Bu sınıf, öğelerle çalışmak üzere tasarlanmıştır.  Nesne referansları:\  - [Öğe](/manual/api/reference/item/object#item)  Kullanılabilir yöntemler:\  - [item.create](/manual/api/reference/item/create) - yeni oluşturma     öğeler - [item.delete](/manual/api/reference/item/delete) - öğeleri silme - [item.get](/manual/api/reference/item/get) - öğeleri alma - [item.update](/manual/api/reference/item/update) - öğeleri güncelleme

en-us	# item.update
tr	## item.update

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
tr	# LLD kuralı  Bu sınıf, düşük seviyeli keşif kurallarıyla çalışmak üzere tasarlanmıştır.  Nesne referansları:\  - [LLD kuralı](/manual/api/reference/discoveryrule/object#lld_rule)  Kullanılabilir yöntemler:\  - [discoveryrule.copy](/manual/api/reference/discoveryrule/copy) -     LLD kurallarını kopyalama - [discoveryrule.create](/manual/api/reference/discoveryrule/create) -     yeni LLD kuralları oluşturma - [discoveryrule.delete](/manual/api/reference/discoveryrule/delete) -     LLD kurallarını silme - [discoveryrule.get](/manual/api/reference/discoveryrule/get) -     LLD kurallarını alma - [discoveryrule.update](/manual/api/reference/discoveryrule/update) -     LLD kurallarını güncelleme

en-us	# maintenance.create
tr	## maintenance.create

en-us	# maintenance.get
tr	## maintenance.get

en-us	# > Maintenance object  The following objects are directly related to the `maintenance` API.
tr	# > Bakım nesnesi  Aşağıdaki nesneler doğrudan "bakım" API'si ile ilgilidir.

en-us	# maintenance.update
tr	## maintenance.update

en-us	 # manifest.json  Any module needs the manifest.json file. The file must be located in the module's primary directory (for example, *zabbix/ui/modules/module_name/manifest.json*).  As a bare minimum, manifest.json should specify these fields:  ```json {     "manifest_version": 2.0,     "id": "my_ip_address",     "name": "My IP Address",     "namespace": "MyIPAddress",     "version": "1.0" } ```  Parameters supported in **manifest.json** (press on the parameter name for a detailed description):  |Parameter |Description |Required | |--|--------|--| |[manifest_version](#manifest-version)|Manifest version of the module.| Yes | |[id](#id) |Unique module ID. |^| |[name](#name) |Module name that will be displayed in the Administration section. |^| |[namespace](#namespace) |PHP namespace for module classes.|^| |[version](#version) |Module version. |^| |[type](#type) |Type of the module. For widget must be set to *widget* | Yes for widgets, otherwise no | |[widget](#widget) |Widget configuration. Used for widgets only. |^| |[actions](#actions) | Actions to register with the module. |^| |[assets](#assets) | CSS styles and JavaScript files to include. | No | |[author](#author) |Module author. |^| |[config](#config) |Default values for custom module options. |^| |[description](#description) |Module description.|^| |[url](#url) |A link to the module description. |^|
tr	 # manifest.json  Herhangi bir modülün manifest.json dosyasına ihtiyacı vardır. Dosya, modülün birincil dizininde bulunmalıdır (örneğin, *zabbix/ui/modules/module_name/manifest.json*).  En azından manifest.json şu alanları belirtmelidir:  ```json {     "manifest_version": 2.0,     "id": "ip_adresim",     "name": "IP Adresim",     "ad alanı": "IPAdresim",     "sürüm": "1.0" } ''''  **manifest.json**'da desteklenen parametreler (ayrıntılı açıklama için parametre adına basın):  |Parametre |Açıklama |Gerekli | |--|-----------|--| |[manifest_version](#manifest-version)|Modülün manifest sürümü.| Evet | |[id](#id) |Benzersiz modül kimliği. |^| |[name](#name) |Yönetim bölümünde görüntülenecek modül adı. |^| |[ad alanı](#ad alanı) |Modül sınıfları için PHP ad alanı.|^| |[sürüm](#sürüm) |Modül sürümü. |^| |[type](#type) |Modülün türü. Widget için *widget* olarak ayarlanmalıdır | Widget'lar için evet, aksi takdirde hayır | |[widget](#widget) |Widget yapılandırması. Yalnızca widget'lar için kullanılır. |^| |[eylemler](#eylemler) | Modüle kaydedilecek eylemler. |^| |[varlıklar](#varlıklar) | Eklenecek CSS stilleri ve JavaScript dosyaları. | Hayır | |[yazar](#yazar) |Modül yazarı. |^| |[config](#config) |Özel modül seçenekleri için varsayılan değerler. |^| |[açıklama](#açıklama) |Modül açıklaması.|^| |[url](#url) |Modül açıklamasına bağlantı. |^|

en-us	 ### manifest_version {#manifest-version}  Manifest version of the module. Currently, supported version is **2.0**.  *Type*: Double  *Example*:   ```json "manifest_version": 2.0 ```
tr	 ### manifest_version {#manifest-version}  Modülün manifest versiyonu. Şu anda desteklenen sürüm **2.0**'dır.  *Tip*: Çift  *Örnek*:  ```json "manifest_version": 2,0 ''''

en-us	# map.create
tr	## map.create

en-us	# map.delete
tr	## map.delete

en-us	# map.get
tr	## map.get

en-us	#### Map listing  ![](../../../../../assets/en/manual/web_interface/map_list.png){width="600"}  Displayed data:  |Column|Description| |--|--------| |*Name*|Name of the map. Click on the name to [view](/manual/web_interface/frontend_sections/monitoring/maps#viewing_maps) the map.| |*Width*|Map width is displayed.| |*Height*|Map height is displayed.| |*Actions*|Two actions are available:<br>**Properties** - edit general map [properties](/manual/config/visualization/maps/map#creating_a_map)<br>**Constructor** - access the grid for adding [map elements](/manual/config/visualization/maps/map#adding_elements)|  To [configure](/manual/config/visualization/maps/map#creating_a_map) a new map, click on the *Create map* button in the top right-hand corner. To import a map from a YAML, XML, or JSON file, click on the *Import* button in the top right-hand corner. The user who imports the map will be set as its owner.  Two buttons below the list offer some mass-editing options:  -   *Export* - export the maps to a YAML, XML, or JSON file -   *Delete* - delete the maps  To use these options, mark the checkboxes before the respective maps, then click on the required button.
tr	#### Harita listesi  ![](../../../../../assets/en/manual/web_interface/map_list.png){width="600"}  Görüntülenen veriler:  |Sütun|Açıklama| |--|--------| |*Ad*|Haritanın adı. Haritayı [görüntülemek](/manual/web_interface/frontend_sections/monitoring/maps#viewing_maps) için isme tıklayın.| |*Genişlik*|Harita genişliği görüntülenir.| |*Yükseklik*|Harita yüksekliği görüntülenir.| |*Eylemler*|İki eylem kullanılabilir:<br>**Özellikler** - genel haritayı düzenle [özellikler](/manual/config/visualization/maps/map#creating_a_map)<br>**Yapıcı** - [harita öğeleri](/manual/config/visualization/maps/map#adding_elements)| eklemek için ızgara  Bir [yapılandırmak](/manual/config/visualization/maps/map#creating_a_map) için yeni harita, sağ üst köşedeki *Harita oluştur* düğmesini tıklayın. YAML, XML veya JSON dosyasından bir haritayı içe aktarmak için *İçe Aktar* seçeneğine tıklayın. sağ üst köşedeki düğme. Haritayı içe aktaran kullanıcı, sahibi olarak belirlenir.  Listenin altındaki iki düğme bazı toplu düzenleme seçenekleri sunar:  - *Dışa Aktar* - haritaları bir YAML, XML veya JSON dosyasına aktarın - *Sil* - haritaları silin  Bu seçenekleri kullanmak için ilgili haritaların önündeki onay kutularını işaretleyin, ardından gerekli butona tıklayın.

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.
tr	##### 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	# mediatype.create
tr	## mediatype.create

en-us	# mediatype.get
tr	## mediatype.get

en-us	# mediatype.update
tr	## mediatype.update

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)|
tr	##### - 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}
tr	## İSİM  zabbix\_agent2 - Zabbix aracısı 2\ \ [ ]{#lbAC}

en-us	## NAME  zabbix\_js - Zabbix JS utility [ ]{#lbAC}
tr	## İSİM  zabbix\_js - Zabbix JS yardımcı programı [ ]{#lbAC}

en-us	## NAME  zabbix\_proxy - Zabbix proxy daemon [ ]{#lbAC}
tr	## İSİM  zabbix\_proxy - Zabbix proxy arka plan programı [ ]{#lbAC}

en-us	## NAME  zabbix\_sender - Zabbix sender utility [ ]{#lbAC}
tr	## İSİM  zabbix\_proxy - Zabbix proxy arka plan programı [ ]{#lbAC}

en-us	## NAME  zabbix\_server - Zabbix server daemon [ ]{#lbAC}
tr	## İSİM  zabbix\_proxy - Zabbix proxy arka plan programı [ ]{#lbAC}

en-us	## NAME  zabbix\_web\_service - Zabbix web service [ ]{#lbAC}
tr	## İSİM  zabbix\_web\_service - Zabbix web hizmeti [ ]{#lbAC}

en-us	### Notation
tr	### Gösterim

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}
tr	## SEÇENEKLER  **-c**, **--config** *yapılandırma dosyası* Varsayılan dosyanın yerine alternatif *config-file* dosyasını kullanın.  **-h**, **--yardım** Bu yardımı görüntüleyin ve çıkın.  **-V**, **--versiyon** Sürüm bilgisi çıktısı alın ve çıkın.  [ ]{#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*.
tr	## SEÇENEKLER  **-c**, **--config** *yapılandırma dosyası* Varsayılan dosyanın yerine alternatif *config-file* dosyasını kullanın.  **-R**, **--çalışma zamanı kontrolü** *çalışma zamanı seçeneği* *runtime-option*'a göre yönetimsel işlevleri gerçekleştirin.

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

en-us	#### Other agent options  It is possible to run multiple instances of the agent on a host. A single instance can use the default configuration file or a configuration file specified in the command line. In case of multiple instances each agent instance must have its own configuration file (one of the instances can use the default configuration file).  The following command line parameters can be used with Zabbix agent:  |Parameter|Description| |--|--------| |**UNIX and Windows agent**|<| |-c --config <config-file>|Path to the configuration file.<br>You may use this option to specify a configuration file that is not the default one.<br>On UNIX, default is /usr/local/etc/zabbix\_agentd.conf or as set by [compile-time](/manual/installation/install#installing_zabbix_daemons) variables *--sysconfdir* or *--prefix*<br>On Windows, default is c:\\zabbix\_agentd.conf| |-p --print|Print known items and exit.<br>*Note*: To return [user parameter](/manual/config/items/userparameters) results as well, you must specify the configuration file (if it is not in the default location).| |-t --test <item key>|Test specified item and exit.<br>*Note*: To return [user parameter](/manual/config/items/userparameters) results as well, you must specify the configuration file (if it is not in the default location).| |-h --help|Display help information| |-V --version|Display version number| |**UNIX agent only**|<| |-R --runtime-control <option>|Perform administrative functions. See [runtime control](/manual/concepts/agent#runtime_control).| |**Windows agent only**|<| |-m --multiple-agents|Use multiple agent instances (with -i,-d,-s,-x functions).<br>To distinguish service names of instances, each service name will include the Hostname value from the specified configuration file.| |**Windows agent only (functions)**|<| |-i --install|Install Zabbix Windows agent as service| |-d --uninstall|Uninstall Zabbix Windows agent service| |-s --start|Start Zabbix Windows agent service| |-x --stop|Stop Zabbix Windows agent service|  Specific **examples** of using command line parameters:  -   printing all built-in agent items with values -   testing a user parameter with "mysql.ping" key defined in the     specified configuration file -   installing a "Zabbix Agent" service for Windows using the default     path to configuration file c:\\zabbix\_agentd.conf -   installing a "Zabbix Agent \[Hostname\]" service for Windows using     the configuration file zabbix\_agentd.conf located in the same     folder as agent executable and make the service name unique by     extending it by Hostname value from the config file  ```{=html} <!-- --> ```     shell> zabbix_agentd --print     shell> zabbix_agentd -t "mysql.ping" -c /etc/zabbix/zabbix_agentd.conf     shell> zabbix_agentd.exe -i     shell> zabbix_agentd.exe -i -m -c zabbix_agentd.conf
tr	#### Other agent options  It is possible to run multiple instances of the agent on a host. A single instance can use the default configuration file or a configuration file specified in the command line. In case of multiple instances each agent instance must have its own configuration file (one of the instances can use the default configuration file).  The following command line parameters can be used with Zabbix agent:  |Parameter|Description| |--|--------| |**UNIX and Windows agent**|<| |-c --config <config-file>|Path to the configuration file.<br>You may use this option to specify a configuration file that is not the default one.<br>On UNIX, default is /usr/local/etc/zabbix\_agentd.conf or as set by [compile-time](/manual/installation/install#installing_zabbix_daemons) variables *--sysconfdir* or *--prefix*<br>On Windows, default is c:\\zabbix\_agentd.conf| |-p --print|Print known items and exit.<br>*Note*: To return [user parameter](/manual/config/items/userparameters) results as well, you must specify the configuration file (if it is not in the default location).| |-t --test <item key>|Test specified item and exit.<br>*Note*: To return [user parameter](/manual/config/items/userparameters) results as well, you must specify the configuration file (if it is not in the default location).| |-h --help|Display help information| |-V --version|Display version number| |**UNIX agent only**|<| |-R --runtime-control <option>|Perform administrative functions. See [runtime control](/manual/concepts/agent#runtime_control).| |**Windows agent only**|<| |-m --multiple-agents|Use multiple agent instances (with -i,-d,-s,-x functions).<br>To distinguish service names of instances, each service name will include the Hostname value from the specified configuration file.| |**Windows agent only (functions)**|<| |-i --install|Install Zabbix Windows agent as service| |-d --uninstall|Uninstall Zabbix Windows agent service| |-s --start|Start Zabbix Windows agent service| |-x --stop|Stop Zabbix Windows agent service|  Specific **examples** of using command line parameters:  -   printing all built-in agent items with values -   testing a user parameter with "mysql.ping" key defined in the     specified configuration file -   installing a "Zabbix Agent" service for Windows using the default     path to configuration file c:\\zabbix\_agentd.conf -   installing a "Zabbix Agent \[Hostname\]" service for Windows using     the configuration file zabbix\_agentd.conf located in the same     folder as agent executable and make the service name unique by     extending it by Hostname value from the config file  ```{=html} <!-- --> ```     shell> zabbix_agentd --print     shell> zabbix_agentd -t "mysql.ping" -c /etc/zabbix/zabbix_agentd.conf     shell> zabbix_agentd.exe -i     shell> zabbix_agentd.exe -i -m -c zabbix_agentd.conf

en-us	**Other hardware**  A serial communication port and a serial GSM modem are required for using SMS notification support in Zabbix. USB-to-serial converter will also work.
tr	**Other hardware**  A serial communication port and a serial GSM modem are required for using SMS notification support in Zabbix. USB-to-serial converter will also work.

en-us	#### Overview  By default, Zabbix provides a number of predefined themes. You may follow the step-by-step procedure provided here in order to create your own. Feel free to share the result of your work with Zabbix community if you created something nice.
tr	#### Genel Bakış  Varsayılan olarak, Zabbix bir dizi önceden tanımlanmış tema sağlar. Yapabilirsin oluşturmak için burada sağlanan adım adım prosedürü izleyin. sahip olmak. Çalışmanızın sonucunu Zabbix topluluğuyla paylaşmaktan çekinmeyin. güzel bir şey yaratmışsın

en-us	#### Overview  Debug mode may be used to diagnose performance problems with frontend pages.
tr	#### Genel bakış  Hata ayıklama modu, ön uç sayfalarla ilgili performans sorunlarını teşhis etmek için kullanılabilir.

en-us	#### Overview  In message subjects and message text you can use macros for more efficient problem reporting.  In addition to a number of built-in macros, [user macros](/manual/config/macros/user_macros) and [expression macros](/manual/config/macros/expression_macros) are also supported. A [full list of macros](/manual/appendix/macros/supported_by_location) supported by Zabbix is available.
tr	#### Genel Bakış  Mesaj konuları ve mesaj metninde daha fazlası için makroları kullanabilirsiniz. etkili sorun raporlama.  Bir dizi yerleşik makroya ek olarak, [kullanıcı makroları](/manual/config/macros/user_macros) ve [ifade makroları](/manual/config/macros/expression_macros) da desteklenir. Zabbix tarafından desteklenen [makroların tam listesi](/manual/appendix/macros/supported_by_location) mevcuttur.

en-us	#### Overview  In the *Monitoring → Maps* section you can configure, manage and view [network maps](/manual/config/visualization/maps).  When you open this section, you will either see the last map you accessed or a listing of all maps you have access to.  All maps can be either public or private. Public maps are available to all users, while private maps are accessible only to their owner and the users the map is shared with.
tr	#### Genel Bakış  *İzleme → Haritalar* bölümünde yapılandırabilir, yönetebilir ve görüntüleyebilirsiniz [ağ haritaları](/manual/config/visualization/maps).  Bu bölümü açtığınızda ya son haritayı göreceksiniz. erişilen veya erişiminiz olan tüm haritaların bir listesi.  Tüm haritalar genel veya özel olabilir. Herkese açık haritalar kullanılabilir tüm kullanıcılar, özel haritalara ise yalnızca sahipleri ve haritanın paylaşıldığı kullanıcılar.

en-us	#### Overview  In this section you can learn the meaning of some terms commonly used in Zabbix.
tr	#### Genel bakış  Bu bölümde, Zabbix\'te yaygın olarak kullanılan bazı terimlerin anlamlarını öğrenebilirsiniz.

en-us	#### Overview  Media types are [exported](/manual/xml_export_import) with all related objects and object relations.
tr	#### Genel Bakış  Medya türleri, ilgili nesneler ve nesne ilişkileri ile[dışa aktarılır](/manual/xml_export_import).

en-us	#### Overview  The Inventory menu features sections providing an overview of host inventory data by a chosen parameter as well as the ability to view host inventory details.
tr	#### Genel Bakış  Envanter menüsü, ana bilgisayara genel bir bakış sağlayan bölümler içerir. Ana bilgisayarı görüntüleme yeteneğinin yanı sıra seçilen bir parametreye göre envanter verileri envanter detayları.

en-us	#### Overview  The *Inventory → Overview* section provides ways of having an overview of [host inventory](/manual/config/hosts/inventory) data.  For an overview to be displayed, choose host groups (or none) and the inventory field by which to display data. The number of hosts corresponding to each entry of the chosen field will be displayed.  ![](../../../../../assets/en/manual/web_interface/inventory_overview.png){width="600"}  The completeness of an overview depends on how much inventory information is maintained with the hosts.  Numbers in the *Host count* column are links; they lead to these hosts being filtered out in the *Host Inventories* table.  ![](../../../../../assets/en/manual/web_interface/inventory_filtered1.png){width="600"}
tr	#### Genel Bakış  *Envanter → Genel Bakış* bölümü, genel bir bakışa sahip olmanın yollarını sunar [ana bilgisayar envanteri](/manual/config/hosts/inventory) verisi.  Görüntülenecek bir genel bakış için, ana bilgisayar gruplarını seçin (veya hiçbiri) ve verilerin görüntüleneceği envanter alanı. ev sahibi sayısı seçilen alanın her girişine karşılık gelen görüntülenecektir.  ![](../../../../../assets/en/manual/web_interface/inventory_overview.png){width="600"}  Bir genel bakışın eksiksiz olması, envanterin ne kadar bilgiler ana bilgisayarlarda tutulur.  *Ana bilgisayar sayısı* sütunundaki sayılar bağlantıdır; bu ana bilgisayarlara yol açarlar *Ana Bilgisayar Envanterleri* tablosunda filtrelenir.  ![](../../../../../assets/en/manual/web_interface/inventory_filtered1.png){width="600"}

en-us	#### Overview  The Monitoring menu is all about displaying data. Whatever information Zabbix is configured to gather, visualize and act upon, it will be displayed in the various sections of the Monitoring menu.
tr	#### Genel Bakış  İzleme menüsü tamamen verileri görüntülemekle ilgilidir. Hangi bilgi olursa olsun Zabbix toplamak, görselleştirmek ve buna göre hareket etmek için yapılandırılmıştır. İzleme menüsünün çeşitli bölümlerinde görüntülenir.

en-us	#### Overview  The Services menu is for the [service monitoring](/manual/it_services) functions of Zabbix.
tr	#### Genel Bakış  Hizmetler menüsü, Zabbix'in [hizmet izleme](/manual/it_services) işlevleri içindir.

en-us	### Overview  This section allows to view and [configure](/manual/it_services/sla) SLAs.
tr	### Genel Bakış  Bu bölüm SLA'ları görüntülemeye ve [yapılandırmaya](/manual/it_services/sla) izin verir.

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.
tr	#### Genel Bakış  Bu bölüm, Ceph Zabbix aracısı 2'de desteklenen parametreleri listeler eklenti yapılandırma dosyası (ceph.conf).  Dikkat:  - Varsayılan değerler, işlem varsayılanlarını yansıtır, içindeki değerleri değil.     gönderilen yapılandırma dosyaları; - Zabbix, yapılandırma dosyalarını yalnızca UTF-8 kodlamasında destekler.     [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); - "\#" ile başlayan yorumlar yalnızca başında desteklenir     çizgi.

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.
tr	#### Genel Bakış  Bu bölüm, Ceph Zabbix aracısı 2'de desteklenen parametreleri listeler eklenti yapılandırma dosyası (ceph.conf).  Dikkat:  - Varsayılan değerler, işlem varsayılanlarını yansıtır, içindeki değerleri değil.     gönderilen yapılandırma dosyaları; - Zabbix, yapılandırma dosyalarını yalnızca UTF-8 kodlamasında destekler.     [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); - "\#" ile başlayan yorumlar yalnızca başında desteklenir     çizgi.

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.
tr	#### 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.
tr	#### 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	#### Overview  Zabbix is a highly integrated network monitoring solution, offering a multiplicity of features in a single package.  **[Data gathering](/manual/config/items)**  -   availability and performance checks -   support for SNMP (both trapping and polling), IPMI, JMX, VMware     monitoring -   custom checks -   gathering desired data at custom intervals -   performed by server/proxy and by agents  **[Flexible threshold definitions](/manual/config/triggers)**  -   you can define very flexible problem thresholds, called triggers,     referencing values from the backend database  **[Highly configurable alerting](/manual/config/notifications)**  -   sending notifications can be customized for the escalation schedule,     recipient, media type -   notifications can be made meaningful and helpful using macro     variables -   automatic actions include remote commands  **[Real-time graphing](/manual/config/visualization/graphs/simple)**  -   monitored items are immediately graphed using the built-in graphing     functionality  **[Web monitoring capabilities](/manual/web_monitoring)**  -   Zabbix can follow a path of simulated mouse clicks on a web site and     check for functionality and response time  **[Extensive visualization options](/manual/config/visualization)**  -   ability to create custom graphs that can combine multiple items into     a single view -   network maps -   slideshows in a dashboard-style overview -   reports -   high-level (business) view of monitored resources  **[Historical data storage](/manual/installation/requirements#database_size)**  -   data stored in a database -   configurable history -   built-in housekeeping procedure  **[Easy configuration](/manual/config/hosts)**  -   add monitored devices as hosts -   hosts are picked up for monitoring, once in the database -   apply templates to monitored devices  **[Use of templates](/manual/config/templates)**  -   grouping checks in templates -   templates can inherit other templates  **[Network discovery](/manual/discovery)**  -   automatic discovery of network devices -   agent autoregistration -   discovery of file systems, network interfaces and SNMP OIDs  **[Fast web interface](/manual/web_interface)**  -   a web-based frontend in PHP -   accessible from anywhere -   you can click your way through -   audit log  **[Zabbix API](/manual/api)**  -   Zabbix API provides programmable interface to Zabbix for mass     manipulations, third-party software integration and other purposes.  **[Permissions system](/manual/config/users_and_usergroups)**  -   secure user authentication -   certain users can be limited to certain views  **[Full featured and easily extensible agent](/manual/concepts/agent)**  -   deployed on monitoring targets -   can be deployed on both Linux and Windows  **[Binary daemons](/manual/concepts/server)**  -   written in C, for performance and small memory footprint -   easily portable  **[Ready for complex environments](/manual/distributed_monitoring)**  -   remote monitoring made easy by using a Zabbix proxy
tr	#### Overview  Zabbix is a highly integrated network monitoring solution, offering a multiplicity of features in a single package.  **[Data gathering](/manual/config/items)**  -   availability and performance checks -   support for SNMP (both trapping and polling), IPMI, JMX, VMware     monitoring -   custom checks -   gathering desired data at custom intervals -   performed by server/proxy and by agents  **[Flexible threshold definitions](/manual/config/triggers)**  -   you can define very flexible problem thresholds, called triggers,     referencing values from the backend database  **[Highly configurable alerting](/manual/config/notifications)**  -   sending notifications can be customized for the escalation schedule,     recipient, media type -   notifications can be made meaningful and helpful using macro     variables -   automatic actions include remote commands  **[Real-time graphing](/manual/config/visualization/graphs/simple)**  -   monitored items are immediately graphed using the built-in graphing     functionality  **[Web monitoring capabilities](/manual/web_monitoring)**  -   Zabbix can follow a path of simulated mouse clicks on a web site and     check for functionality and response time  **[Extensive visualization options](/manual/config/visualization)**  -   ability to create custom graphs that can combine multiple items into     a single view -   network maps -   slideshows in a dashboard-style overview -   reports -   high-level (business) view of monitored resources  **[Historical data storage](/manual/installation/requirements#database_size)**  -   data stored in a database -   configurable history -   built-in housekeeping procedure  **[Easy configuration](/manual/config/hosts)**  -   add monitored devices as hosts -   hosts are picked up for monitoring, once in the database -   apply templates to monitored devices  **[Use of templates](/manual/config/templates)**  -   grouping checks in templates -   templates can inherit other templates  **[Network discovery](/manual/discovery)**  -   automatic discovery of network devices -   agent autoregistration -   discovery of file systems, network interfaces and SNMP OIDs  **[Fast web interface](/manual/web_interface)**  -   a web-based frontend in PHP -   accessible from anywhere -   you can click your way through -   audit log  **[Zabbix API](/manual/api)**  -   Zabbix API provides programmable interface to Zabbix for mass     manipulations, third-party software integration and other purposes.  **[Permissions system](/manual/config/users_and_usergroups)**  -   secure user authentication -   certain users can be limited to certain views  **[Full featured and easily extensible agent](/manual/concepts/agent)**  -   deployed on monitoring targets -   can be deployed on both Linux and Windows  **[Binary daemons](/manual/concepts/server)**  -   written in C, for performance and small memory footprint -   easily portable  **[Ready for complex environments](/manual/distributed_monitoring)**  -   remote monitoring made easy by using a Zabbix proxy

en-us	#### Overview  Zabbix proxy is a process that may collect monitoring data from one or more monitored devices and send the information to the Zabbix server, essentially working on behalf of the server. All collected data is buffered locally and then transferred to the Zabbix server the proxy belongs to.  Deploying a proxy is optional, but may be very beneficial to distribute the load of a single Zabbix server. If only proxies collect data, processing on the server becomes less CPU and disk I/O hungry.  A Zabbix proxy is the ideal solution for centralized monitoring of remote locations, branches and networks with no local administrators.  Zabbix proxy requires a separate database.  ::: noteimportant Note that databases supported with Zabbix proxy are SQLite, MySQL and PostgreSQL. Using Oracle is at your own risk and may contain some limitations as, for example, in [return values](/manual/discovery/low_level_discovery#overview) of low-level discovery rules. :::  See also: [Using proxies in a distributed environment](/manual/distributed_monitoring/proxies)
tr	#### Overview  Zabbix proxy is a process that may collect monitoring data from one or more monitored devices and send the information to the Zabbix server, essentially working on behalf of the server. All collected data is buffered locally and then transferred to the Zabbix server the proxy belongs to.  Deploying a proxy is optional, but may be very beneficial to distribute the load of a single Zabbix server. If only proxies collect data, processing on the server becomes less CPU and disk I/O hungry.  A Zabbix proxy is the ideal solution for centralized monitoring of remote locations, branches and networks with no local administrators.  Zabbix proxy requires a separate database.  ::: noteimportant Note that databases supported with Zabbix proxy are SQLite, MySQL and PostgreSQL. Using Oracle is at your own risk and may contain some limitations as, for example, in [return values](/manual/discovery/low_level_discovery#overview) of low-level discovery rules. :::  See also: [Using proxies in a distributed environment](/manual/distributed_monitoring/proxies)

en-us	#### Overview  Zabbix server is the central process of Zabbix software.  The server performs the polling and trapping of data, it calculates triggers, sends notifications to users. It is the central component to which Zabbix agents and proxies report data on availability and integrity of systems. The server can itself remotely check networked services (such as web servers and mail servers) using simple service checks.  The server is the central repository in which all configuration, statistical and operational data is stored, and it is the entity in Zabbix that will actively alert administrators when problems arise in any of the monitored systems.  The functioning of a basic Zabbix server is broken into three distinct components; they are: Zabbix server, web frontend and database storage.  All of the configuration information for Zabbix is stored in the database, which both the server and the web frontend interact with. For example, when you create a new item using the web frontend (or API) it is added to the items table in the database. Then, about once a minute Zabbix server will query the items table for a list of the items which are active that is then stored in a cache within the Zabbix server. This is why it can take up to two minutes for any changes made in Zabbix frontend to show up in the latest data section.
tr	#### Overview  Zabbix server is the central process of Zabbix software.  The server performs the polling and trapping of data, it calculates triggers, sends notifications to users. It is the central component to which Zabbix agents and proxies report data on availability and integrity of systems. The server can itself remotely check networked services (such as web servers and mail servers) using simple service checks.  The server is the central repository in which all configuration, statistical and operational data is stored, and it is the entity in Zabbix that will actively alert administrators when problems arise in any of the monitored systems.  The functioning of a basic Zabbix server is broken into three distinct components; they are: Zabbix server, web frontend and database storage.  All of the configuration information for Zabbix is stored in the database, which both the server and the web frontend interact with. For example, when you create a new item using the web frontend (or API) it is added to the items table in the database. Then, about once a minute Zabbix server will query the items table for a list of the items which are active that is then stored in a cache within the Zabbix server. This is why it can take up to two minutes for any changes made in Zabbix frontend to show up in the latest data section.

en-us	### Parameters  `(array)` IDs of items to clear.
tr	### Parametreler  `(dizi)` Silinecek kullanıcıların kimlikleri.

en-us	### Parameters  `(array)` IDs of the actions to delete.
tr	### Parametreler  `(dizi)` Silinecek eylemlerin kimlikleri.

en-us	### Parameters  `(array)` IDs of the connectors to delete.
tr	### Parametreler  Silinecek bağlayıcıların `(dizi)` kimlikleri.

en-us	### Parameters  `(array)` IDs of the correlations to delete.
tr	### Parametreler  `(dizi)` Silinecek bağıntıların kimlikleri.

en-us	### Parameters  `(array)` IDs of the dashboards to delete.
tr	### Parametreler  `(dizi)` Silinecek grafiklerin kimlikleri.

en-us	### Parameters  `(array)` IDs of the discovery rules to delete.
tr	### Parametreler  `(dizi)` Silinecek grafiklerin kimlikleri.

en-us	### Parameters  `(array)` IDs of the graphs to delete.
tr	### Parametreler  `(dizi)` Silinecek grafiklerin kimlikleri.

en-us	### Parameters  `(array)` IDs of the icon maps to delete.
tr	### Parametreler  `(dizi)` Silinecek harita resimlerinin kimlikleri.

en-us	### Parameters  `(array)` IDs of the images to delete.
tr	### Parametreler  `(dizi)` Silinecek resimlerin kimlikleri.

en-us	### Parameters  `(array)` IDs of the item prototypes to delete.
tr	### Parametreler  `(dizi)` Silinecek eylemlerin kimlikleri.

en-us	### Parameters  `(array)` IDs of the items to delete.
tr	### Parametreler  `(dizi)` Silinecek eylemlerin kimlikleri.

en-us	### Parameters  `(array)` IDs of the LLD rules to delete.
tr	### Parametreler  `(dizi)` Silinecek eylemlerin kimlikleri.

en-us	### Parameters  `(array)` IDs of the triggers to delete.
tr	### Parametreler  `(dizi)` Silinecek tetikleyicilerin kimlikleri.

en-us	### Parameters  `(array)` IDs of the user groups to delete.
tr	### Parametreler  `(dizi)` Silinecek kullanıcı gruplarının kimlikleri.

en-us	### Parameters  `(array)` IDs of users to delete.
tr	### Parametreler  `(dizi)` Silinecek kullanıcıların kimlikleri.

en-us	### Parameters  `(array)` The method accepts an empty array.
tr	### Parametreler  `(dizi)` Yöntem boş bir diziyi kabul eder.

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.|
tr	### Parametreler  `(nesne/dizi)` Grafik özellikleri güncellenecek.  Her grafik için 'graphid' özelliği tanımlanmalıdır, diğer tüm özellikler isteğe bağlıdır. Yalnızca geçirilen özellikler güncellenecek, tümü diğerleri değişmeden kalacaktır.  [standart grafik özelliklerine](nesne#graf) ek olarak, yöntem aşağıdaki parametreleri kabul eder.  |Parametre|[Tür](/manual/api/reference_commentary#data_types)|Açıklama| |--|--|------| |gitems|array|Mevcut grafik öğelerini değiştirmek için [öğeler](/manual/api/reference/graphitem/object) grafiği. Bir grafik öğesinin `gitemid` özelliği tanımlanmışsa, güncellenecektir, aksi takdirde yeni bir grafik öğesi oluşturulacaktır.|

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.|
tr	### Parametreler  `(nesne/dizi)` Grafik özellikleri güncellenecek.  Her grafik için 'graphid' özelliği tanımlanmalıdır, diğer tüm özellikler isteğe bağlıdır. Yalnızca geçirilen özellikler güncellenecek, tümü diğerleri değişmeden kalacaktır.  [standart grafik özelliklerine](nesne#graf) ek olarak, yöntem aşağıdaki parametreleri kabul eder.  |Parametre|[Tür](/manual/api/reference_commentary#data_types)|Açıklama| |--|--|------| |gitems|array|Mevcut grafik öğelerini değiştirmek için [öğeler](/manual/api/reference/graphitem/object) grafiği. Bir grafik öğesinin `gitemid` özelliği tanımlanmışsa, güncellenecektir, aksi takdirde yeni bir grafik öğesi oluşturulacaktır.|

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.|
tr	### Parametreler  `(nesne/dizi)` Grafik özellikleri güncellenecek.  Her grafik için 'graphid' özelliği tanımlanmalıdır, diğer tüm özellikler isteğe bağlıdır. Yalnızca geçirilen özellikler güncellenecek, tümü diğerleri değişmeden kalacaktır.  [standart grafik özelliklerine](nesne#graf) ek olarak, yöntem aşağıdaki parametreleri kabul eder.  |Parametre|[Tür](/manual/api/reference_commentary#data_types)|Açıklama| |--|--|------| |gitems|array|Mevcut grafik öğelerini değiştirmek için [öğeler](/manual/api/reference/graphitem/object) grafiği. Bir grafik öğesinin `gitemid` özelliği tanımlanmışsa, güncellenecektir, aksi takdirde yeni bir grafik öğesi oluşturulacaktır.|

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.
tr	### Parametreler  `(nesne/dizi)` [Ana grup özellikleri](object#host_group) olacak güncellenmiş.  "groupid" özelliği, her ana bilgisayar grubu için tanımlanmalıdır, diğer tüm özellikler isteğe bağlıdır. Yalnızca verilen özellikler güncellenecek, tümü diğerleri değişmeden kalacaktır.

en-us	### Parameters  `(object/array)` Items to create.  Additionally to the [standard item properties](object#host), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |preprocessing|array|Item [preprocessing](/manual/api/reference/item/object#item_preprocessing) options.| |tags|array|Item [tags](/manual/api/reference/item/object#item_tag).|
tr	### Parameters  `(object/array)` Items to create.  Additionally to the [standard item properties](object#host), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |preprocessing|array|Item [preprocessing](/manual/api/reference/item/object#item_preprocessing) options.| |tags|array|Item [tags.](/manual/api/reference/item/object#item_tag)|

en-us	### Parameters  `(object/array)` Role properties to be updated.  The `roleid` property must be defined for each role, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  Additionally to the [standard role properties](object#role) the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |rules|array|Access [rules](object#role_rules) to replace the current access rules assigned to the role.|
tr	### Parametreler  `(nesne/dizi)` Grafik özellikleri güncellenecek.  Her grafik için 'graphid' özelliği tanımlanmalıdır, diğer tüm özellikler isteğe bağlıdır. Yalnızca geçirilen özellikler güncellenecek, tümü diğerleri değişmeden kalacaktır.  [standart grafik özelliklerine](nesne#graf) ek olarak, yöntem aşağıdaki parametreleri kabul eder.  |Parametre|[Tür](/manual/api/reference_commentary#data_types)|Açıklama| |--|--|------| |gitems|array|Mevcut grafik öğelerini değiştirmek için [öğeler](/manual/api/reference/graphitem/object) grafiği. Bir grafik öğesinin `gitemid` özelliği tanımlanmışsa, güncellenecektir, aksi takdirde yeni bir grafik öğesi oluşturulacaktır.|

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).|
tr	### 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)|

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).|
tr	### Parametreler  `(nesne)` İstenen çıktıyı tanımlayan parametreler.  Yöntem yalnızca bir parametreyi destekler.  |Parametre|[Tür](/manual/api/reference_commentary#data_types)|Açıklama| |--|--|------| |output|query|Bu parametre, [referans yorumunda](/manual/api/reference_commentary#common_get_method_parameters) açıklanan tüm "get" yöntemleri için ortaktır.|

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).|
tr	### Parametreler  `(nesne)` İstenen çıktıyı tanımlayan parametreler.  Yöntem yalnızca bir parametreyi destekler.  |Parametre|[Tür](/manual/api/reference_commentary#data_types)|Açıklama| |--|--|------| |output|query|Bu parametre, [referans yorumunda](/manual/api/reference_commentary#common_get_method_parameters) açıklanan tüm "get" yöntemleri için ortaktır.|

en-us	### Part III - Module action  An action is implemented in two files - *actions/MyAddress.php* and *views/my.address.php*. The ***actions/MyAddress.php*** file takes care of the business logic implementation, while the ***views/my.address.php*** file is responsible for the view.  1. Create a directory *actions* in the *MyAddress* directory.  2. Create a *MyAddress.php* file in the *actions* directory.  The action logic will be defined in the *MyAddress* class. This action class will implement four functions: *init()*, *checkInput()*, *checkPermissions()*, and *doAction()*. Zabbix frontend calls the *doAction()* function when the action is requested. This function is responsible for the business logic of the module.  ::: noteimportant The data must be organized as an associative array. The array can be multidimensional and may contain any data expected by the view. :::  **ui/modules/MyAddress/actions/MyAddress.php**  ```php <?php  namespace Modules\MyAddress\Actions;  use CController,     CControllerResponseData;  class MyAddress extends CController {      public function init(): void {         $this->disableCsrfValidation();     }      protected function checkInput(): bool {         return true;     }      protected function checkPermissions(): bool {         return true;     }      protected function doAction(): void {         $data = ['my-ip' => file_get_contents("https://api.seeip.org")];         $response = new CControllerResponseData($data);         $this->setResponse($response);     } } ```  3. Create a new directory *views* in the *MyAddress* directory.  4. Create a *my.address.php* file in the *views* directory and define the module view.  Note that the variable `$data` is available in the view without specifically defining it. The framework automatically passes the associative array to the view.  **ui/modules/MyAddress/views/my.address.php**  ```php <?php  (new CHtmlPage())     ->setTitle(_('The HTML Title of My Address Page'))     ->addItem(new CDiv($data['my-ip']))     ->show(); ```  5. The module action has to be registered in the *manifest.json* file. Open *manifest.json* and add a new object `actions` that contains:  -   the action key with the action name written in lowercase (a-z) and with words separated by dots (for example, `my.address`); -   the action class name (`MyAddress`) as a value for the `class` key of the `my.address` object; -   the action view name (`my.address`) as a value for the `view` key of the `my.address` object.  **ui/modules/MyAddress/manifest.json**  ```json {     "manifest_version": 2.0,     "id": "my-address",     "name": "My IP Address",     "version": "1.0",     "namespace": "MyAddress",     "description": "My External IP Address",     "actions": {         "my.address": {             "class": "MyAddress",             "view": "my.address"         }     } } ```  6. Open *Module.php* and change the action name in the **setAction()** method to *my.address*.  **ui/modules/MyAddress/Module.php**  ```php <?php  namespace Modules\MyAddress;  use Zabbix\Core\CModule,     APP,     CMenuItem;  class Module extends CModule {      public function init(): void {         APP::Component()->get('menu.main')             ->findOrAdd(_('Monitoring'))                 ->getSubmenu()                     ->insertAfter(_('Discovery'),                         (new CMenuItem(_('My Address')))->setAction('my.address')                     );     } } ```  7. Refresh Zabbix frontend. Click on the *My address* menu section to see the IP address of your computer.  ![](../../../../assets/en/devel/modules/tutorials/module/my_address_finished.png){width="600"}
tr	### Bölüm III - Modül eylemi  Bir eylem iki dosyada uygulanır - *actions/MyAddress.php* ve *views/my.address.php*. ***actions/MyAddress.php*** dosyası iş mantığının uygulanmasıyla ilgilenirken ***views/my.address.php*** dosyası görünümden sorumludur.  1. *Adresim* dizininde bir *eylemler* dizini oluşturun.  2. *actions* dizininde bir *Adresim.php* dosyası oluşturun.  Eylem mantığı *MyAddress* sınıfında tanımlanacaktır. Bu eylem sınıfı dört işlevi uygulayacaktır: *init()*, *checkInput()*, *checkPermissions()* ve *doAction()*. Zabbix ön ucu, eylem istendiğinde *doAction()* işlevini çağırır. Bu fonksiyon modülün iş mantığından sorumludur.  ::: notönemli Veriler ilişkisel bir dizi olarak düzenlenmelidir. Dizi çok boyutlu olabilir ve görünümün beklediği herhangi bir veriyi içerebilir. :::  **ui/modules/Adresim/actions/Adresim.php**  ```php <?php  ad alanı Modüller\Adresim\Actions;  CController'ı kullanın,     CControllerResponseData;  class MyAddress CController'ı genişletir {      genel işlev başlatma(): void {         $this->disableCsrfValidation();     }      korumalı işlev checkInput(): bool {         doğruyu döndür;     }      korumalı işlev checkPermissions(): bool {         doğruyu döndür;     }      korumalı işlev doAction(): void {         $veri = ['ip'im' => file_get_contents("https://api.seeip.org")];         $yanıt = new CControllerResponseData($veri);         $this->setResponse($response);     } } ''''  3. *Adresim* dizininde yeni bir *görünümler* dizini oluşturun.  4. *views* dizininde bir *my.address.php* dosyası oluşturun ve modül görünümünü tanımlayın.  '$data' değişkeninin görünümde özel olarak tanımlanmadan mevcut olduğunu unutmayın. Çerçeve, ilişkisel diziyi otomatik olarak görünüme aktarır.  **ui/modules/Adresim/views/my.address.php**  ```php <?php  (yeni CHtmlPage())     ->setTitle(_('Adres Sayfamın HTML Başlığı'))     ->addItem(new CDiv($data['my-ip']))     ->göster(); ''''  5. Modül eyleminin *manifest.json* dosyasına kaydedilmesi gerekir. *manifest.json* dosyasını açın ve aşağıdakileri içeren yeni bir `actions' nesnesi ekleyin:  - eylem adının küçük harflerle (a-z) yazıldığı ve kelimelerin noktalarla ayrıldığı eylem anahtarı (örneğin, 'my.address'); - "my.address" nesnesinin "class" anahtarının değeri olarak eylem sınıfı adı ("Adresim"); - "my.address" nesnesinin "view" anahtarının değeri olarak eylem görünümü adı ("my.address").  **ui/modules/Adresim/manifest.json**  ```json {     "manifest_version": 2.0,     "id": "adresim",     "name": "IP Adresim",     "sürüm": "1.0",     "ad alanı": "Adresim",     "description": "Harici IP Adresim",     "hareketler": {         "benim adresim": {             "sınıf": "Adresim",             "görüntüle": "adresim"         }     } } ''''  6. *Module.php*'yi açın ve **setAction()** yöntemindeki eylem adını *my.address* olarak değiştirin.  **ui/modules/Adresim/Module.php**  ```php <?php  ad alanı Modüller\Adresim;  Zabbix\Core\CModule'u kullanın,     UYGULAMA,     CMenuItem;  sınıf Modülü CModule'u genişletir {      genel işlev başlatma(): void {         APP::Component()->get('menu.main')             ->findOrAdd(_('İzleme'))                 ->getSubmenu()                     ->insertAfter(_('Keşif'),                         (new CMenuItem(_('Adresim')))->setAction('my.address')                     );     } } ''''  7. Zabbix kullanıcı arayüzünü yenileyin. Bilgisayarınızın IP adresini görmek için *Adresim* menü bölümüne tıklayın.  ![](../../../../assets/en/devel/modules/tutorials/module/my_address_finished.png){width="600"}

en-us	### Part I - New menu section
tr	### Bölüm I - Yeni menü bölümü

en-us	##### Passive and active checks  Zabbix agents can perform passive and active checks.  In a [passive check](/manual/appendix/items/activepassive#passive_checks) the agent responds to a data request. Zabbix server (or proxy) asks for data, for example, CPU load, and Zabbix agent sends back the result.  [Active checks](/manual/appendix/items/activepassive#active_checks) require more complex processing. The agent must first retrieve a list of items from Zabbix server for independent processing. Then it will periodically send new values to the server.  Whether to perform passive or active checks is configured by selecting the respective monitoring [item type](/manual/config/items/itemtypes/zabbix_agent). Zabbix agent processes items of type 'Zabbix agent' or 'Zabbix agent (active)'.
tr	##### Passive and active checks  Zabbix agents can perform passive and active checks.  In a [passive check](/manual/appendix/items/activepassive#passive_checks) the agent responds to a data request. Zabbix server (or proxy) asks for data, for example, CPU load, and Zabbix agent sends back the result.  [Active checks](/manual/appendix/items/activepassive#active_checks) require more complex processing. The agent must first retrieve a list of items from Zabbix server for independent processing. Then it will periodically send new values to the server.  Whether to perform passive or active checks is configured by selecting the respective monitoring [item type](/manual/config/items/itemtypes/zabbix_agent). Zabbix agent processes items of type 'Zabbix agent' or 'Zabbix agent (active)'.

en-us	 # Plugins
tr	# 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).
tr	 #### 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	##### Preparation  Zabbix agent is distributed as a zip archive. After you download the archive you need to unpack it. Choose any folder to store Zabbix agent and the configuration file, e. g.      C:\zabbix  Copy bin\\zabbix\_agentd.exe and conf\\zabbix\_agentd.conf files to c:\\zabbix.  Edit the c:\\zabbix\\zabbix\_agentd.conf file to your needs, making sure to specify a correct "Hostname" parameter.
tr	##### Preparation  Zabbix agent is distributed as a zip archive. After you download the archive you need to unpack it. Choose any folder to store Zabbix agent and the configuration file, e. g.      C:\zabbix  Copy bin\\zabbix\_agentd.exe and conf\\zabbix\_agentd.conf files to c:\\zabbix.  Edit the c:\\zabbix\\zabbix\_agentd.conf file to your needs, making sure to specify a correct "Hostname" parameter.

en-us	# problem.get
tr	## problem.get

en-us	#### Process user  Zabbix agent on UNIX is designed to run as a non-root user. It will run as whatever non-root user it is started as. So you can run agent as any non-root user without any issues.  If you will try to run it as 'root', it will switch to a hardcoded 'zabbix' user, which must be present on your system. You can only run agent as 'root' if you modify the 'AllowRoot' parameter in the agent configuration file accordingly.
tr	#### Process user  Zabbix agent on UNIX is designed to run as a non-root user. It will run as whatever non-root user it is started as. So you can run agent as any non-root user without any issues.  If you will try to run it as 'root', it will switch to a hardcoded 'zabbix' user, which must be present on your system. You can only run agent as 'root' if you modify the 'AllowRoot' parameter in the agent configuration file accordingly.

en-us	##### Process user  Zabbix proxy is designed to run as a non-root user. It will run as whatever non-root user it is started as. So you can run proxy as any non-root user without any issues.  If you will try to run it as 'root', it will switch to a hardcoded 'zabbix' user, which must be present on your system. You can only run proxy as 'root' if you modify the 'AllowRoot' parameter in the proxy configuration file accordingly.
tr	##### Process user  Zabbix proxy is designed to run as a non-root user. It will run as whatever non-root user it is started as. So you can run proxy as any non-root user without any issues.  If you will try to run it as 'root', it will switch to a hardcoded 'zabbix' user, which must be present on your system. You can only run proxy as 'root' if you modify the 'AllowRoot' parameter in the proxy configuration file accordingly.

en-us	##### Process user  Zabbix server is designed to run as a non-root user. It will run as whatever non-root user it is started as. So you can run server as any non-root user without any issues.  If you will try to run it as 'root', it will switch to a hardcoded 'zabbix' user, which must be [present](/manual/installation/install) on your system. You can only run server as 'root' if you modify the 'AllowRoot' parameter in the server configuration file accordingly.  If Zabbix server and [agent](agent) are run on the same machine it is recommended to use a different user for running the server than for running the agent. Otherwise, if both are run as the same user, the agent can access the server configuration file and any Admin level user in Zabbix can quite easily retrieve, for example, the database password.
tr	##### Process user  Zabbix server is designed to run as a non-root user. It will run as whatever non-root user it is started as. So you can run server as any non-root user without any issues.  If you will try to run it as 'root', it will switch to a hardcoded 'zabbix' user, which must be [present](/manual/installation/install) on your system. You can only run server as 'root' if you modify the 'AllowRoot' parameter in the server configuration file accordingly.  If Zabbix server and [agent](agent) are run on the same machine it is recommended to use a different user for running the server than for running the agent. Otherwise, if both are run as the same user, the agent can access the server configuration file and any Admin level user in Zabbix can quite easily retrieve, for example, the database password.

en-us	# proxy.create
tr	## proxy.create

en-us	# proxy.delete
tr	## proxy.delete

en-us	# Proxy  This class is designed to work with proxies.  Object references:\  -   [Proxy](/manual/api/reference/proxy/object#proxy) -   [Proxy     interface](/manual/api/reference/proxy/object#proxy_interface)  Available methods:\  -   [proxy.create](/manual/api/reference/proxy/create) - create new     proxies -   [proxy.delete](/manual/api/reference/proxy/delete) - delete proxies -   [proxy.get](/manual/api/reference/proxy/get) - retrieve proxies -   [proxy.update](/manual/api/reference/proxy/update) - update proxies
tr	# Resim  Bu sınıf, görüntülerle çalışmak üzere tasarlanmıştır.  Nesne referansları:\  - [Resim](/manual/api/reference/image/object#image)  Kullanılabilir yöntemler:\  - [image.create](/manual/api/reference/image/create) - yeni oluştur     Görüntüler - [image.delete](/manual/api/reference/image/delete) - resimleri sil - [image.get](/manual/api/reference/image/get) - görüntüleri al - [image.update](/manual/api/reference/image/update) - resimleri güncelleyin

en-us	# proxy.update
tr	# proxy.update

en-us	##### Proxy  [Zabbix proxy](/manual/concepts/proxy) can collect performance and availability data on behalf of Zabbix server. A proxy is an optional part of Zabbix deployment; however, it may be very beneficial to distribute the load of a single Zabbix server.
tr	##### Proxy  [Zabbix proxy](/manual/concepts/proxy) can collect performance and availability data on behalf of Zabbix server. A proxy is an optional part of Zabbix deployment; however, it may be very beneficial to distribute the load of a single Zabbix server.

en-us	##### Referencing a network map  Network maps can be referenced by both `sysmapid` and `mapname` GET parameters. For example,      http://zabbix/zabbix/zabbix.php?action=map.view&mapname=Local%20network  will open the map with that name (Local network).  If both `sysmapid` (map ID) and `mapname` (map name) are specified, `mapname` has higher priority.
tr	##### Bir ağ haritasına başvurma  Ağ haritalarına hem "sysmapid" hem de "mapname" GET tarafından başvurulabilir. parametreler. Örneğin,      http://zabbix/zabbix/zabbix.php?action=map.view&mapname=Local%20network  haritayı bu adla açacaktır (Yerel ağ).  Hem "sysmapid" (harita kimliği) hem de "mapname" (harita adı) belirtilirse, "mapname" daha yüksek önceliğe sahiptir.

en-us	# regexp.create
tr	## item.create

en-us	# Regular expression  This class is designed to work with global regular expressions.  Object references:\  -   [Regular expression](/manual/api/reference/regexp/object)  Available methods:\  -   [regexp.create](/manual/api/reference/regexp/create) - creating new     regular expressions -   [regexp.delete](/manual/api/reference/regexp/delete) - deleting     regular expressions -   [regexp.get](/manual/api/reference/regexp/get) - retrieving regular     expressions -   [regexp.update](/manual/api/reference/regexp/update) - updating     regular expressions
tr	# Düzenli ifade  Bu sınıf, global düzenli ifadeler ile çalışmak üzere tasarlanmıştır.  Nesne referansları:\  - [Öğe](/manual/api/reference/item/object#item)  Kullanılabilir yöntemler:\  - [item.create](/manual/api/reference/item/create) - yeni oluşturma     öğeler - [item.delete](/manual/api/reference/item/delete) - öğeleri silme - [item.get](/manual/api/reference/item/get) - öğeleri alma - [item.update](/manual/api/reference/item/update) - öğeleri güncelleme

en-us	# report.delete
tr	## report.delete

en-us	# report.get
tr	## report.get

en-us	# report.update
tr	## report.update

en-us	#### Required software  Zabbix is built around modern web servers, leading database engines, and PHP scripting language.
tr	#### Required software  Zabbix is built around modern web servers, leading database engines, and PHP scripting language.

en-us	#### Retrieving the version of the API  Retrieve the version of the Zabbix API.  [Request](/manual/api#performing-requests):  ```json {     "jsonrpc": "2.0",     "method": "apiinfo.version",     "params": [],     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": "6.4.0",     "id": 1 } ```
tr	#### API sürümünü alma  Zabbix API sürümünü alın.  Rica etmek:  ``` json {     "jsonrpc": "2.0",     "method": "apiinfo.version",     "paramlar": [],     "kimlik": 1 } ```  Tepki:  ``` json {     "jsonrpc": "2.0",     "sonuç": "4.0.0",     "kimlik": 1 } ```

en-us	### Return values  `(boolean )` Returns boolean true as result on successful update.
tr	### Dönüş değerleri  `(boolean )` Başarılı güncellemenin sonucu olarak boolean true değerini döndürür.

en-us	### Return values  `(boolean)` Returns `true` if importing has been successful.
tr	### Dönüş değerleri  `(boolean)` İçe aktarma başarılıysa `true` değerini döndürür.

en-us	### Return values  `(boolean)` Returns `true` if the copying was successful.
tr	### Dönüş değerleri  `(boolean)` Kopyalama başarılıysa `true` değerini döndürür.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
tr	### Dönüş değerleri  `(tamsayı/dizi)` Şunlardan birini döndürür:  - bir dizi nesne; - `countOutput` parametresi varsa, alınan nesnelerin sayısı     kullanılmış

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
tr	### Dönüş değerleri  `(tamsayı/dizi)` Şunlardan birini döndürür:  - bir dizi nesne; - `countOutput` parametresi varsa, alınan nesnelerin sayısı     kullanılmış

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
tr	### Dönüş değerleri  `(integer/dizi)` Şunlardan birini döndürür:  - bir dizi nesne; - "countOutput" parametresi varsa, alınan nesnelerin sayısı     kullanılmış.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
tr	### Dönüş değerleri  `(integer/dizi)` Şunlardan birini döndürür:  - bir dizi nesne; - "countOutput" parametresi varsa, alınan nesnelerin sayısı     kullanılmış.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
tr	### Dönen değerler  `(integer/dizi)` Şunlardan birini döndürür:  - bir dizi nesne; - "countOutput" parametresi varsa, alınan nesnelerin sayısı     kullanılmış.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
tr	### Dönen değerler  `(integer/dizi)` Şunlardan birini döndürür:  - bir dizi nesne; - "countOutput" parametresi varsa, alınan nesnelerin sayısı     kullanılmış.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
tr	### Dönüş değerleri  `(tamsayı/dizi)` Şunlardan birini döndürür:  - bir dizi nesne; - `countOutput` parametresi varsa, alınan nesnelerin sayısı     kullanılmış

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
tr	### Dönüş değerleri  `(integer/dizi)` Şunlardan birini döndürür:  - bir dizi nesne; - "countOutput" parametresi varsa, alınan nesnelerin sayısı     kullanılmış.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
tr	### Dönen değerler  `(integer/dizi)` Şunlardan birini döndürür:  - bir dizi nesne; - "countOutput" parametresi varsa, alınan nesnelerin sayısı     kullanılmış.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
tr	### Dönen değerler  `(integer/dizi)` Şunlardan birini döndürür:  - bir dizi nesne; - "countOutput" parametresi varsa, alınan nesnelerin sayısı     kullanılmış.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
tr	### Dönüş değerleri  `(tamsayı/dizi)` Şunlardan birini döndürür:  - bir dizi nesne; - `countOutput` parametresi varsa, alınan nesnelerin sayısı     kullanılmış

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
tr	### Dönen değerler  `(integer/dizi)` Şunlardan birini döndürür:  - bir dizi nesne; - "countOutput" parametresi varsa, alınan nesnelerin sayısı     kullanılmış.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
tr	### Dönen değerler  `(integer/dizi)` Şunlardan birini döndürür:  - bir dizi nesne; - "countOutput" parametresi varsa, alınan nesnelerin sayısı     kullanılmış.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
tr	### Dönüş değerleri  `(tamsayı/dizi)` Şunlardan birini döndürür:  - bir dizi nesne; - `countOutput` parametresi varsa, alınan nesnelerin sayısı     kullanılmış

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
tr	### Dönen değerler  `(integer/dizi)` Şunlardan birini döndürür:  - bir dizi nesne; - "countOutput" parametresi varsa, alınan nesnelerin sayısı     kullanılmış.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
tr	### Dönen değerler  `(integer/dizi)` Şunlardan birini döndürür:  - bir dizi nesne; - "countOutput" parametresi varsa, alınan nesnelerin sayısı     kullanılmış.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
tr	### Dönen değerler  `(integer/dizi)` Şunlardan birini döndürür:  - bir dizi nesne; - "countOutput" parametresi varsa, alınan nesnelerin sayısı     kullanılmış.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
tr	### Dönen değerler  `(integer/dizi)` Şunlardan birini döndürür:  - bir dizi nesne; - "countOutput" parametresi varsa, alınan nesnelerin sayısı     kullanılmış.

en-us	### Return values  `(object)` Returns an object containing the IDs of the cleared items under the `itemids` property.
tr	### Dönen değerler  `(object)` Silinen LLD kurallarının kimliklerini içeren bir nesne döndürür "itemids" özelliği altında.

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.
tr	### Dönen değerler  `(nesne)` Oluşturulan eylemlerin kimliklerini içeren bir nesne döndürür "actionids" özelliği altında. Döndürülen kimliklerin sırası eşleşir geçirilen eylemlerin sırası.

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.
tr	### Dönüş değerleri  `(nesne)` Oluşturulan nesnelerin kimliklerini içeren bir nesne döndürür. 'correlationids' özelliği altındaki korelasyonlar. sipariş döndürülen kimlikler, geçirilen bağıntıların sırası ile eşleşir.

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.
tr	### Dönen değerler  `(object)` Oluşturulanların kimliklerini içeren bir nesne döndürür. "dashboardids" özelliği altındaki panolar. İade sırası Kimlikler, geçirilen panoların sırası ile eşleşir.

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.
tr	### Dönen değerler  `(nesne)` Oluşturulan LLD kurallarının kimliklerini içeren bir nesne döndürür "itemids" özelliği altında. Döndürülen kimliklerin sırası, geçirilen LLD kurallarının sırası.

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.
tr	### Dönüş değerleri  `(object)` Oluşturulan grafiğin kimliklerini içeren bir nesne döndürür `graphids` özelliği altındaki prototipler. İade edilen kimliklerin sırası geçirilen grafik prototiplerinin sırası ile eşleşir.

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.
tr	### Dönüş değerleri  `(object)` Oluşturulan ana bilgisayarların kimliklerini içeren bir nesne döndürür "hostids" özelliği altında. Döndürülen kimliklerin sırası şunlarla eşleşir: geçen ana bilgisayarların sırası.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created host interfaces under the `interfaceids` property.
tr	### Dönüş değerleri  `(object)` Oluşturulan ana bilgisayarın kimliklerini içeren bir nesne döndürür `interfaceids` özelliği altındaki arayüzler.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created host interfaces under the `interfaceids` property.
tr	### Dönüş değerleri  `(object)` Oluşturulan ana bilgisayarın kimliklerini içeren bir nesne döndürür `interfaceids` özelliği altındaki arayüzler.

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.
tr	### Dönüş değerleri  `(object)` Oluşturulanların kimliklerini içeren bir nesne döndürür. "maintenanceids" özelliği altındaki bakımlar. sırası iade edilen kimlikler, geçirilen bakımların sırası ile eşleşir.

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.
tr	### Dönüş değerleri  `(object)` Oluşturulan ana bilgisayarların kimliklerini içeren bir nesne döndürür "hostids" özelliği altında. Döndürülen kimliklerin sırası şunlarla eşleşir: geçen ana bilgisayarların sırası.

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.
tr	### Dönen değerler  `(nesne)` Oluşturulan LLD kurallarının kimliklerini içeren bir nesne döndürür "itemids" özelliği altında. Döndürülen kimliklerin sırası, geçirilen LLD kurallarının sırası.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created maintenances under the `maintenanceids` property. The order of the returned IDs matches the order of the passed maintenances.
tr	### Dönüş değerleri  `(object)` Oluşturulanların kimliklerini içeren bir nesne döndürür. "maintenanceids" özelliği altındaki bakımlar. sırası iade edilen kimlikler, geçirilen bakımların sırası ile eşleşir.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created regular expressions under the `regexpids` property.
tr	### Dönüş değerleri  `(nesne)` Güncellenen grafiklerin kimliklerini içeren bir nesne döndürür "grafikler" özelliği altında.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created template dashboards under the `dashboardids` property. The order of the returned IDs matches the order of the passed template dashboards.
tr	### Dönen değerler  `(object)` Oluşturulanların kimliklerini içeren bir nesne döndürür. "dashboardids" özelliği altındaki panolar. İade sırası Kimlikler, geçirilen panoların sırası ile eşleşir.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created user groups under the `usrgrpids` property. The order of the returned IDs matches the order of the passed user groups.
tr	### Dönüş değerleri  `(object)` Oluşturulan grafiğin kimliklerini içeren bir nesne döndürür `graphids` özelliği altındaki prototipler. İade edilen kimliklerin sırası geçirilen grafik prototiplerinin sırası ile eşleşir.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted actions under the `actionids` property.
tr	### Dönen değerler  `(nesne)` Silinen eylemlerin kimliklerini içeren bir nesne döndürür "actionids" özelliği altında.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted connectors under the `connectorids` property.
tr	### Dönüş değerleri  `(object)` `connectorids` özelliği altındaki silinen bağlayıcıların kimliklerini içeren bir nesneyi döndürür.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted correlations under the `correlationids` property.
tr	### Dönüş değerleri  `(nesne)` Silinenlerin kimliklerini içeren bir nesne döndürür. 'correlationids' özelliği altındaki korelasyonlar.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted dashboards under the `dashboardids` property.
tr	### Dönüş değerleri  `(object)` Silinenlerin kimliklerini içeren bir nesne döndürür. "dashboardids" özelliği altındaki panolar.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted discovery rules under the `druleids` property.
tr	### Dönüş değerleri  `(nesne)` Güncellenen ana bilgisayarın kimliklerini içeren bir nesne döndürür 'groupids' özelliği altındaki gruplar.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted graphs under the `graphids` property.
tr	### Dönüş değerleri  `(nesne)` Silinen grafiklerin kimliklerini içeren bir nesne döndürür "grafikler" özelliği altında.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted items under the `itemids` property.
tr	### Dönen değerler  `(object)` Silinen LLD kurallarının kimliklerini içeren bir nesne döndürür "itemids" özelliği altında.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted template dashboards under the `dashboardids` property.
tr	### Dönüş değerleri  `(object)` Silinenlerin kimliklerini içeren bir nesne döndürür. "dashboardids" özelliği altındaki panolar.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted user groups under the `usrgrpids` property.
tr	### Dönen değerler  `(object)` Silinen LLD kurallarının kimliklerini içeren bir nesne döndürür "itemids" özelliği altında.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted users under the `userids` property.
tr	### Dönen değerler  `(object)` Silinen LLD kurallarının kimliklerini içeren bir nesne döndürür "itemids" özelliği altında.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated actions under the `actionids` property.
tr	### Dönüş değerleri  `(nesne)` Güncellenen eylemlerin kimliklerini içeren bir nesne döndürür "actionids" özelliği altında.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated correlations under the `correlationids` property.
tr	### Dönüş değerleri  `(nesne)` Güncellenen nesnenin kimliklerini içeren bir nesne döndürür. 'correlationids' özelliği altındaki korelasyonlar.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated dashboards under the `dashboardids` property.
tr	### Dönüş değerleri  `(nesne)` Güncellenen nesnenin kimliklerini içeren bir nesne döndürür. "dashboardids" özelliğinin altındaki panolar.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated discovery rules under the `druleids` property.
tr	### Dönüş değerleri  `(nesne)` Güncellenen ana bilgisayarın kimliklerini içeren bir nesne döndürür 'groupids' özelliği altındaki gruplar.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated events under the `eventids` property.
tr	### Dönüş değerleri  `(nesne)` Güncellenen olayların kimliklerini içeren bir nesne döndürür 'eventids' özelliği altında.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated graph prototypes under the `graphids` property.
tr	### Dönüş değerleri  `(nesne)` Güncellenen grafiklerin kimliklerini içeren bir nesne döndürür "grafikler" özelliği altında.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated graphs under the `graphids` property.
tr	### Dönüş değerleri  `(nesne)` Güncellenen grafiklerin kimliklerini içeren bir nesne döndürür "grafikler" özelliği altında.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated host groups under the `groupids` property.
tr	### Dönüş değerleri  `(nesne)` Güncellenen ana bilgisayarın kimliklerini içeren bir nesne döndürür 'groupids' özelliği altındaki gruplar.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated host groups under the `groupids` property.
tr	### Dönüş değerleri  `(nesne)` Güncellenen ana bilgisayarın kimliklerini içeren bir nesne döndürür 'groupids' özelliği altındaki gruplar.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated host prototypes under the `hostids` property.
tr	### Dönüş değerleri  `(nesne)` Güncellenen ana bilgisayarın kimliklerini içeren bir nesne döndürür 'groupids' özelliği altındaki gruplar.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated hosts under the `hostids` property.
tr	### Dönüş değerleri  `(nesne)` Güncellenen olayların kimliklerini içeren bir nesne döndürür 'eventids' özelliği altında.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated images under the `imageids` property.
tr	### Dönüş değerleri  `(nesne)` Güncellenen grafiklerin kimliklerini içeren bir nesne döndürür "grafikler" özelliği altında.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated item prototypes under the `itemids` property.
tr	### Dönüş değerleri  `(nesne)` Güncellenen ana bilgisayarın kimliklerini içeren bir nesne döndürür 'groupids' özelliği altındaki gruplar.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated items under the `itemids` property.
tr	### Dönen değerler  `(object)` Silinen LLD kurallarının kimliklerini içeren bir nesne döndürür "itemids" özelliği altında.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated LLD rules under the `itemids` property.
tr	### Dönen değerler  `(object)` Silinen LLD kurallarının kimliklerini içeren bir nesne döndürür "itemids" özelliği altında.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated maintenances under the `maintenanceids` property.
tr	### Dönüş değerleri  `(nesne)` Güncellenen eylemlerin kimliklerini içeren bir nesne döndürür "actionids" özelliği altında.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated roles under the `roleids` property.
tr	### Dönüş değerleri  `(nesne)` Güncellenen olayların kimliklerini içeren bir nesne döndürür 'eventids' özelliği altında.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated scripts under the `scriptids` property.
tr	### Dönüş değerleri  `(nesne)` Güncellenen grafiklerin kimliklerini içeren bir nesne döndürür "grafikler" özelliği altında.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated templates under the `templateids` property.
tr	### Dönüş değerleri  `(nesne)` Güncellenen grafiklerin kimliklerini içeren bir nesne döndürür "grafikler" özelliği altında.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated templates under the `templateids` property.
tr	### Dönüş değerleri  `(nesne)` Güncellenen grafiklerin kimliklerini içeren bir nesne döndürür "grafikler" özelliği altında.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated web scenarios under the `httptestid` property.
tr	### Dönüş değerleri  `(nesne)` Güncellenen olayların kimliklerini içeren bir nesne döndürür 'eventids' özelliği altında.

en-us	### Return values  `(object)` Returns authentication object.
tr	### Dönüş değerleri  `(nesne)` Otomatik kayıt nesnesini döndürür.

en-us	### Return values  `(object)` Returns autoregistration object.
tr	### Dönüş değerleri  `(nesne)` Otomatik kayıt nesnesini döndürür.

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. :::
tr	### Dönüş değerleri  `(string)` Zabbix API'sinin sürümünü döndürür.  ::: not ipucu API'nin Zabbix 2.0.4 sürümünden başlayarak Zabbix sürümüyle eşleşir. :::

en-us	# role.delete
tr	## role.delete

en-us	# role.get
tr	## role.get

en-us	# Role  This class is designed to work with user roles.  Object references:\  -   [Role](/manual/api/reference/role/object#role) -   [Role rules](/manual/api/reference/role/object#role_rules) -   [UI element](/manual/api/reference/role/object#ui_element) -   [Service](/manual/api/reference/role/object#service) -   [Service tag](/manual/api/reference/role/object#service_tag) -   [Module](/manual/api/reference/role/object#module) -   [Action](/manual/api/reference/role/object#action)  Available methods:\  -   [role.create](/manual/api/reference/role/create) - create new user     roles -   [role.delete](/manual/api/reference/role/delete) - delete user roles -   [role.get](/manual/api/reference/role/get) - retrieve user roles -   [role.update](/manual/api/reference/role/update) - update user roles
tr	# Rol  Bu sınıf, kullanıcı rolleriyle çalışmak üzere tasarlanmıştır.  Nesne başvuruları:\  - [Rol](/manual/api/reference/role/object#role) - [Rol kuralları](/manual/api/reference/role/object#role_rules) - [UI öğesi](/manual/api/reference/role/object#ui_element) - [Hizmet](/manual/api/reference/role/object#service) - [Servis etiketi](/manual/api/reference/role/object#service_tag) - [Modül](/manual/api/reference/role/object#module) - [Eylem](/manual/api/reference/role/object#action)  Kullanılabilir yöntemler:\  - [role.create](/manual/api/reference/role/create) - yeni kullanıcı oluştur     roller - [role.delete](/manual/api/reference/role/delete) - kullanıcı rollerini sil - [role.get](/manual/api/reference/role/get) - kullanıcı rollerini al - [role.update](/manual/api/reference/role/update) - kullanıcı rollerini güncelle

en-us	# role.update
tr	## role.update

en-us	#### Running server
tr	#### Running server

en-us	#### Running Zabbix get  An example of running Zabbix get under UNIX to get the processor load value from the agent:      shell> cd bin     shell> ./zabbix_get -s 127.0.0.1 -p 10050 -k system.cpu.load[all,avg1]  Another example of running Zabbix get for capturing a string from a website:      shell> cd bin     shell> ./zabbix_get -s 192.168.1.1 -p 10050 -k "web.page.regexp[www.example.com,,,\"USA: ([a-zA-Z0-9.-]+)\",,\1]"  Note that the item key here contains a space so quotes are used to mark the item key to the shell. The quotes are not part of the item key; they will be trimmed by the shell and will not be passed to Zabbix agent.  Zabbix get accepts the following command line parameters:        -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 seconds).       -k --key <item key>              Specify key of item to retrieve value of.       -h --help                        Give this help.       -V --version                     Display version number.  See also [Zabbix get manpage](/manpages/zabbix_get) for more information.  Zabbix get on Windows can be run similarly:      zabbix_get.exe [options]
tr	#### Running Zabbix get  An example of running Zabbix get under UNIX to get the processor load value from the agent:      shell> cd bin     shell> ./zabbix_get -s 127.0.0.1 -p 10050 -k system.cpu.load[all,avg1]  Another example of running Zabbix get for capturing a string from a website:      shell> cd bin     shell> ./zabbix_get -s 192.168.1.1 -p 10050 -k "web.page.regexp[www.example.com,,,\"USA: ([a-zA-Z0-9.-]+)\",,\1]"  Note that the item key here contains a space so quotes are used to mark the item key to the shell. The quotes are not part of the item key; they will be trimmed by the shell and will not be passed to Zabbix agent.  Zabbix get accepts the following command line parameters:        -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 seconds).       -k --key <item key>              Specify key of item to retrieve value of.       -h --help                        Give this help.       -V --version                     Display version number.  See also [Zabbix get manpage](/manpages/zabbix_get) for more information.  Zabbix get on Windows can be run similarly:      zabbix_get.exe [options]

en-us	#### Scenario
tr	#### Senaryo

en-us	# script.delete
tr	## script.delete

en-us	# script.execute
tr	## script.execute

en-us	# script.get
tr	## script.get

en-us	# script.getscriptsbyhosts
tr	## script.getscriptsbyhosts

en-us	# script.update
tr	## script.update

en-us	### See also  -   [Action filter](object#action_filter) -   [Action operation](object#action_operation)
tr	### Ayrıca bakınız  - [İşlem filtresi](object#action_filter) - [Eylem işlemi](nesne#eylem_operasyonu)

en-us	### See also  -   [Action filter](object#action_filter) -   [Action operation](object#action_operation)
tr	### Ayrıca bakınız  - [İşlem filtresi](object#action_filter) - [Eylem işlemi](nesne#eylem_operasyonu)

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)
tr	### Ayrıca bakınız  - [Uyarı](/manual/api/reference/alert/object) - [Öğe](/manual/api/reference/item/nesne) - [Ana Bilgisayar](/manual/api/reference/host/nesne) - [LLD kuralı](/manual/api/reference/discoveryrule/object#lld_rule) - [Tetikleyici](/manual/api/reference/trigger/object)

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)
tr	### Ayrıca bakınız  - [Uyarı](/manual/api/reference/alert/object) - [Öğe](/manual/api/reference/item/nesne) - [Ana Bilgisayar](/manual/api/reference/host/nesne) - [LLD kuralı](/manual/api/reference/discoveryrule/object#lld_rule) - [Tetikleyici](/manual/api/reference/trigger/object)

en-us	### See also  -   [Audit log object](/manual/api/reference/auditlog/object)
tr	### Ayrıca bakınız  - [Denetim günlüğü nesnesi](/manual/api/reference/auditlog/object)

en-us	### See also  -   [Correlation filter](object#correlation_filter) -   [Correlation operation](object#correlation_operation)
tr	### Ayrıca bakınız  - [Korelasyon filtresi](object#correlation_filter) - [Korelasyon işlemi](nesne#korelasyon_operasyonu)

en-us	### See also  -   [Correlation filter](object#correlation_filter) -   [Correlation operation](object#correlation_operation)
tr	### Ayrıca bakınız  - [Korelasyon filtresi](object#correlation_filter) - [Korelasyon işlemi](nesne#korelasyon_operasyonu)

en-us	### See also  -   [Correlation filter](object#correlation_filter) -   [Correlation operation](object#correlation_operation)
tr	### Ayrıca bakınız  - [Korelasyon filtresi](object#correlation_filter) - [Korelasyon işlemi](nesne#korelasyon_operasyonu)

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)
tr	### Ayrıca bakınız  - [Kontrol paneli sayfası](object#dashboard_page) - [Gösterge panosu widget'ı](object#dashboard_widget) - [Gösterge panosu widget alanı](object#dashboard_widget_field) - [Dashboard kullanıcısı](object#dashboard_user) - [Dashboard kullanıcı grubu](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)
tr	### Ayrıca bakınız  - [Kontrol paneli sayfası](object#dashboard_page) - [Gösterge panosu widget'ı](object#dashboard_widget) - [Gösterge panosu widget alanı](object#dashboard_widget_field) - [Dashboard kullanıcısı](object#dashboard_user) - [Dashboard kullanıcı grubu](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)
tr	### Ayrıca bakınız  - [Kontrol paneli sayfası](object#dashboard_page) - [Gösterge panosu widget'ı](object#dashboard_widget) - [Gösterge panosu widget alanı](object#dashboard_widget_field) - [Dashboard kullanıcısı](object#dashboard_user) - [Dashboard kullanıcı grubu](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)
tr	### Ayrıca bakınız  -   [Keşfetti     sunucu](/manual/api/reference/dhost/object#discovered_host) - [Keşif     kontrol](/manual/api/reference/dcheck/object#discovery_check)

en-us	### See also  -   [Discovery     check](/manual/api/reference/dcheck/object#discovery_check)
tr	### Ayrıca bakınız  - [Keşif     kontrol et](/manual/api/reference/dcheck/object#discovery_check)

en-us	### See also  -   [Discovery     check](/manual/api/reference/dcheck/object#discovery_check)
tr	### Ayrıca bakınız  - [Keşif     kontrol et](/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}
tr	## AYRICA BAKINIZ  Belgeler <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\_sunucu](zabbix_sunucu)**(8)  -------------------------------------------------- ----------------------  [ ]{#index}

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}
tr	## AYRICA BAKINIZ  Belgeler <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}
tr	## AYRICA BAKINIZ  Belgeler <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\_sunucu](zabbix_sunucu)**(8)  -------------------------------------------------- ----------------------  [ ]{#index}

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}
tr	## AYRICA BAKINIZ  Belgeler <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)**(8), **[zabbix\_js](zabbix_js)**(8), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(8), **[zabbix\_server](zabbix_server)**(8) [ ]{#lbAI}
tr	## AYRICA BAKINIZ  Belgeler <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  -   [Graph item](/manual/api/reference/graphitem/object#graph_item)
tr	### Ayrıca bakınız  - [Grafik](/manual/api/reference/graph/object#graph)

en-us	### See also  -   [Graph item](/manual/api/reference/graphitem/object#graph_item)
tr	### Ayrıca bakınız  - [Grafik](/manual/api/reference/graph/object#graph)

en-us	### See also  -   [Graph](/manual/api/reference/graph/object#graph)
tr	### Ayrıca bakınız  - [Grafik](/manual/api/reference/graph/object#graph)

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)
tr	### Ayrıca bakınız  - [Grafik prototipi](/manual/api/reference/graphprototype/object#graph_prototype) - [Ana Bilgisayar](/manual/api/reference/host/object#host) - [Öğe prototipi](/manual/api/reference/itemprototype/object#item_prototype) - [LLD kural filtresi](object#lld_rule_filter) - [Tetikleyici prototipi](/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)
tr	### Ayrıca bakınız  - [Grup bağlantısı](object#group_link) - [Grup prototipi](nesne#grup_prototipi) - [Ana makine prototip etiketi](object#host_prototype_tag) - [Özel arayüz](object#custom_interface) - [Kullanıcı     makro](/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)
tr	### Ayrıca bakınız  - [Grup bağlantısı](object#group_link) - [Grup prototipi](nesne#grup_prototipi) - [Ana makine prototip etiketi](object#host_prototype_tag) - [Özel arayüz](object#custom_interface) - [Kullanıcı     makro](/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)
tr	### Ayrıca bakınız  -   [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)
tr	### Ayrıca bakınız  -   [hostinterface.create](create) -   [host.massadd](/manual/api/reference/host/massadd) -   [Host](/manual/api/reference/host/object#host)

en-us	### See also  -   [hostinterface.massadd](massadd) -   [host.massadd](/manual/api/reference/host/massadd)
tr	### Ayrıca bakınız  - [hostinterface.massadd](massadd) - [host.massadd](/manual/api/reference/host/massadd)

en-us	### See also  -   [Host](/manual/api/reference/host/object#host) -   [Host group](/manual/api/reference/hostgroup/object#host_group) -   [Time period](object#time_period)
tr	### Ayrıca bakınız  -   [Host](/manual/api/reference/host/object#host) -   [Host group](/manual/api/reference/hostgroup/object#host_group) -   [Time period](object#time_period)

en-us	### See also  -   [Host](/manual/api/reference/host/object#host) -   [Item](/manual/api/reference/item/object#item)
tr	### Ayrıca bakınız  - [Ana Bilgisayar](/manual/api/reference/host/object#host) - [Öğe](/manual/api/reference/item/object#item)

en-us	### See also  -   [Host](/manual/api/reference/host/object#host) -   [Proxy interface](object#proxy_interface)
tr	### Ayrıca bakınız  -   [Host](/manual/api/reference/host/object#host) -   [Proxy interface](object#proxy_interface)

en-us	### See also  -   [host.update](/manual/api/reference/host/update) -   [host.massupdate](/manual/api/reference/host/massupdate)
tr	### Ayrıca bakınız  - [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)
tr	### Ayrıca bakınız  - [host.update](güncelleme) - [Ana bilgisayar grubu](/manual/api/reference/hostgroup/object#host_group) - [Şablon](/manual/api/reference/şablon/nesne#şablon) - [Kullanıcı     makro](/manual/api/reference/usermacro/object#hosttemplate_level_macro) -   [Ev sahibi     arayüz](/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)
tr	### Ayrıca bakınız  - [host.update](güncelleme) - [host.massadd](massadd) - [host.massremove](massremove) - [Ana makine grubu](/manual/api/reference/hostgroup/object#host_group) - [Şablon](/manual/api/reference/template/object#host_group) - [Kullanıcı     makro](/manual/api/reference/usermacro/object#hosttemplate_level_macro) -   [Ev sahibi     arayüz](/manual/api/reference/hostinterface/object#host_interface)

en-us	### See also  -   [Icon map](/manual/api/reference/iconmap/object#icon_map) -   [Map element](object#map_element) -   [Map link](object#map_link) -   [Map URL](object#map_url) -   [Map user](object#map_user) -   [Map user group](object#map_user_group) -   [Map shapes](object#map_shapes) -   [Map lines](object#map_lines)
tr	### Ayrıca bakınız  -   [Icon map](/manual/api/reference/iconmap/object#icon_map) -   [Map element](object#map_element) -   [Map link](object#map_link) -   [Map URL](object#map_url) -   [Map user](object#map_user) -   [Map user group](object#map_user_group) -   [Map shapes](object#map_shapes) -   [Map lines](object#map_lines)

en-us	### See also  -   [Icon mapping](object#icon_mapping)
tr	### Ayrıca bakınız  -   [Icon mapping](object#icon_mapping)

en-us	### See also  -   [Icon mapping](object#icon_mapping)
tr	### Ayrıca bakınız  -   [Icon mapping](object#icon_mapping)

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)
tr	### Ayrıca bakınız  - [LLD kuralı filtresi](object#lld_rule_filter) - [LLD makro yolları](object#lld_macro_path) - [LLD kuralı ön işleme](object#lld_rule_preprocessing)

en-us	### See also  -   [Media](/manual/api/reference/user/object#media) -   [Media type](/manual/api/reference/mediatype/object#media_type) -   [User group](/manual/api/reference/usergroup/object#user_group) -   [Role](/manual/api/reference/role/object#role)
tr	### Ayrıca bakınız  -   [Media](/manual/api/reference/user/object#media) -   [Media type](/manual/api/reference/mediatype/object#media_type) -   [User group](/manual/api/reference/usergroup/object#user_group) -   [Role](/manual/api/reference/role/object#role)

en-us	### See also  -   [Permission](object#permission)
tr	### Ayrıca bakınız  -   [Permission](object#permission)

en-us	### See also  -   [Permission](object#permission)
tr	### Ayrıca bakınız  -   [Permission](object#permission)

en-us	### See also  -   [Role rules](/manual/api/reference/role/object#role_rules) -   [User](/manual/api/reference/user/object#user)
tr	### Ayrıca bakınız  - [Ana Bilgisayar](/manual/api/reference/host/object#host) - [Öğe](/manual/api/reference/item/object#item)

en-us	### See also  -   [Scenario step](object#scenario_step)
tr	### Ayrıca bakınız  -   [Scenario step](object#scenario_step)

en-us	### See also  -   [Template dashboard page](object#template_dashboard_page) -   [Template dashboard widget](object#template_dashboard_widget) -   [Template dashboard widget     field](object#template_dashboard_widget_field)
tr	### Ayrıca bakınız  -   [Template dashboard page](object#template_dashboard_page) -   [Template dashboard widget](object#template_dashboard_widget) -   [Template dashboard widget     field](object#template_dashboard_widget_field)

en-us	### See also  -   [Template dashboard page](object#template_dashboard_page) -   [Template dashboard widget](object#template_dashboard_widget) -   [Template dashboard widget     field](object#template_dashboard_widget_field)
tr	### Ayrıca bakınız  -   [Template dashboard page](object#template_dashboard_page) -   [Template dashboard widget](object#template_dashboard_widget) -   [Template dashboard widget     field](object#template_dashboard_widget_field)

en-us	### See also  -   [template.update](update) -   [User macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro)
tr	### Ayrıca bakınız  -   [template.update](update) -   [User macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro)

en-us	### See also  -   [Time period](object#time_period)
tr	### Ayrıca bakınız  - [Zaman aralığı](object#time_period)

en-us	### See also  -   [Time period](object#time_period)
tr	### Ayrıca bakınız  - [Zaman aralığı](object#time_period)

en-us	### See also  -   [User](/manual/api/reference/user/object#user)
tr	### Ayrıca bakınız  -   [User](/manual/api/reference/user/object#user)

en-us	### See also  -   [Users](/manual/api/reference/user/object#users) -   [User groups](/manual/api/reference/user/object#user_groups)
tr	### Ayrıca bakınız  -   [Users](/manual/api/reference/user/object#users) -   [User groups](/manual/api/reference/user/object#user_groups)

en-us	### See also  -   [Users](object#users) -   [User groups](object#user_groups)
tr	### Ayrıca bakınız  -   [Users](object#users) -   [User groups](object#user_groups)

en-us	#### SELinux configuration  See [SELinux configuration](/manual/installation/install_from_packages/rhel#selinux_configuration) for RHEL.  After the frontend and SELinux configuration is done, restart the Apache web server:      # service apache2 restart
tr	#### SELinux configuration  See [SELinux configuration](/manual/installation/install_from_packages/rhel#selinux_configuration) for RHEL.  After the frontend and SELinux configuration is done, restart the Apache web server:      # service apache2 restart

en-us	# service.delete
tr	## service.delete

en-us	# service.get
tr	## service.get

en-us	# service.update
tr	## service.update

en-us	# settings.get
tr	## settings.get

en-us	# settings.update
tr	## settings.update

en-us	### SLAs  ![](../../../../../assets/en/manual/web_interface/sla_list.png){width="600"}  A list of the configured SLAs is displayed. *Note* that only the SLAs  related to services accessible to the user will be displayed (as read-only,  unless *Manage SLA* is enabled for the user role).   Displayed data:  |Parameter|Description| |--|--------| |*Name*|The SLA name is displayed.<br>The name is a link to [SLA configuration](/manual/it_services/sla#configuration). | |*SLO*|The service level objective (SLO) is displayed. | |*Effective date*|The date of starting SLA calculation is displayed. | |*Reporting period*|The period used in the SLA report is displayed - *daily*, *weekly*, *monthly*, *quarterly*, or *annually*. | |*Time zone*|The SLA time zone is displayed. | |*Schedule*|The SLA schedule is displayed - 24x7 or custom. | |*SLA report*|Click on the link to see the SLA report for this SLA. | |*Status*|The SLA status is displayed - enabled or disabled. |
tr	### SLA'lar  ![](../../../../../assets/en/manual/web_interface/sla_list.png){width="600"}  Yapılandırılan SLA'ların bir listesi görüntülenir. *Not* yalnızca SLA'ların kullanıcının erişebileceği hizmetlerle ilgili olarak görüntülenecektir (salt okunur, kullanıcı rolü için *SLA'yı yönetin* etkinleştirilmemişse).   Görüntülenen veriler:  |Parametre|Açıklama| |--|--------| |*Ad*|SLA adı görüntülenir.<br>Ad, [SLA yapılandırması](/manual/it_services/sla#configuration) için bir bağlantıdır. | |*SLO*|Hizmet düzeyi hedefi (SLO) görüntülenir. | |*Geçerlilik tarihi*|SLA hesaplamasının başlangıç tarihi görüntülenir. | |*Raporlama dönemi*|SLA raporunda kullanılan dönem görüntülenir - *günlük*, *haftalık*, *aylık*, *üç aylık* veya *yıllık*. | |*Zaman dilimi*|SLA zaman dilimi görüntülenir. | |*Program*|SLA programı görüntülenir - 7x24 veya özel. | |*SLA raporu*|Bu SLA için SLA raporunu görmek için bağlantıya tıklayın. | |*Durum*|SLA durumu görüntülenir - etkin veya devre dışı. |

en-us	### Source  CAction::create() in *ui/include/classes/api/services/CAction.php*.
tr	### Kaynak  CAction::create() *ui/include/classes/api/services/CAction.php* içinde.

en-us	### Source  CAction::delete() in *ui/include/classes/api/services/CAction.php*.
tr	### Kaynak  CAction::delete() *ui/include/classes/api/services/CAction.php* içinde.

en-us	### Source  CAction::get() in *ui/include/classes/api/services/CAction.php*.
tr	### Kaynak  CAction::delete() *ui/include/classes/api/services/CAction.php* içinde.

en-us	### Source  CAction::update() in *ui/include/classes/api/services/CAction.php*.
tr	### Kaynak  CAction::update() *ui/include/classes/api/services/CAction.php* içinde.

en-us	### Source  CAPIInfo::version() in *ui/include/classes/api/services/CAPIInfo.php*.
tr	### Kaynak  *ui/include/classes/api/services/CAPIInfo.php* içindeki CAPIInfo::version().

en-us	### Source  CAuditLog::get() in *ui/include/classes/api/services/CAuditLog.php*.
tr	### Kaynak  *ui/include/classes/api/services/CAuditLog.php* içinde CAuditLog::get().

en-us	### Source  CAutoregistration::get() in *ui/include/classes/api/services/CAutoregistration.php*.
tr	### Kaynak  CAutoregistration::get() içinde *ui/include/classes/api/services/CAutoregistration.php*.

en-us	### Source  CAutoregistration::update() in *ui/include/classes/api/services/CAutoregistration.php*.
tr	### Kaynak  CAutoregistration::update() içinde *ui/include/classes/api/services/CAutoregistration.php*.

en-us	### Source  CConnector::delete() in *ui/include/classes/api/services/CConnector.php*.
tr	### Kaynak  *ui/include/classes/api/services/CConnector.php* içindeki CConnector::delete().

en-us	### Source  CCorrelation::create() in *ui/include/classes/api/services/CCorrelation.php*.
tr	### Kaynak  CCorrelation::create() içinde *ui/include/classes/api/services/CCorrelation.php*.

en-us	### Source  CCorrelation::delete() in *ui/include/classes/api/services/CCorrelation.php*.
tr	### Kaynak  CCorrelation::delete() içinde *ui/include/classes/api/services/CCorrelation.php*.

en-us	### Source  CCorrelation::get() in *ui/include/classes/api/services/CCorrelation.php*.
tr	### Kaynak  CCorrelation::create() içinde *ui/include/classes/api/services/CCorrelation.php*.

en-us	### Source  CCorrelation::update() in *ui/include/classes/api/services/CCorrelation.php*.
tr	### Kaynak  CCorrelation::delete() içinde *ui/include/classes/api/services/CCorrelation.php*.

en-us	### Source  CDashboard::create() in *ui/include/classes/api/services/CDashboard.php*.
tr	### Kaynak  CDashboard::create() içinde *ui/include/classes/api/services/CDashboard.php*.

en-us	### Source  CDashboard::delete() in *ui/include/classes/api/services/CDashboard.php*.
tr	### Kaynak  CDashboard::create() içinde *ui/include/classes/api/services/CDashboard.php*.

en-us	### Source  CDashboard::get() in *ui/include/classes/api/services/CDashboard.php*.
tr	### Kaynak  CDashboard::create() içinde *ui/include/classes/api/services/CDashboard.php*.

en-us	### Source  CDCheck::get() in *ui/include/classes/api/services/CDCheck.php*.
tr	### Kaynak  *ui/include/classes/api/services/CDCheck.php* içindeki CDCheck::get().

en-us	### Source  CDHost::get() in *ui/include/classes/api/services/CDHost.php*.
tr	### Kaynak  *ui/include/classes/api/services/CDHost.php* içindeki CDHost::get().

en-us	### Source  CDiscoveryRule::delete() in *ui/include/classes/api/services/CDiscoveryRule.php*.
tr	### Kaynak  CDiscoveryRule::delete() içinde *ui/include/classes/api/services/CDiscoveryRule.php*.

en-us	### Source  CDiscoveryRule::get() in *ui/include/classes/api/services/CDiscoveryRule.php*.
tr	### Kaynak  CDiscoveryRule::delete() içinde *ui/include/classes/api/services/CDiscoveryRule.php*.

en-us	### Source  CDiscoveryRule::update() in *ui/include/classes/api/services/CDiscoveryRule.php*.
tr	### Kaynak  CDiscoveryRule::delete() içinde *ui/include/classes/api/services/CDiscoveryRule.php*.

en-us	### Source  CDRule::create() in *ui/include/classes/api/services/CDRule.php*.
tr	### Kaynak  *ui/include/classes/api/services/CDRule.php* içindeki CDRule::create().

en-us	### Source  CDRule::delete() in *ui/include/classes/api/services/CDRule.php*.
tr	### Kaynak  *ui/include/classes/api/services/CDRule.php* içindeki CDRule::create().

en-us	### Source  CDRule::get() in *ui/include/classes/api/services/CDRule.php*.
tr	### Kaynak  *ui/include/classes/api/services/CDRule.php* içindeki CDRule::get().

en-us	### Source  CDRule::update() in *ui/include/classes/api/services/CDRule.php*.
tr	### Kaynak  *ui/include/classes/api/services/CDRule.php* içindeki CDRule::create().

en-us	### Source  CDService::get() in *ui/include/classes/api/services/CDService.php*.
tr	### Kaynak  *ui/include/classes/api/services/CDService.php* içindeki CDService::get().

en-us	### Source  CEvent::acknowledge() in *ui/include/classes/api/services/CEvent.php*.
tr	### Kaynak  *ui/include/classes/api/services/CEvent.php* içindeki CEvent::acknowledge().

en-us	### Source  CEvent::get() in *ui/include/classes/api/services/CEvent.php*.
tr	### Kaynak  *ui/include/classes/api/services/CDHost.php* içindeki CDHost::get().

en-us	### Source  CEvent::get() in *ui/include/classes/api/services/CProblem.php*.
tr	### Kaynak  *ui/include/classes/api/services/CDHost.php* içindeki CDHost::get().

en-us	### Source  CGraph::create() in *ui/include/classes/api/services/CGraph.php*.
tr	### Kaynak  *ui/include/classes/api/services/CGraph.php* içindeki CGraph::update().

en-us	### Source  CGraph::delete() in *ui/include/classes/api/services/CGraph.php*.
tr	### Kaynak  *ui/include/classes/api/services/CGraph.php* içindeki CGraph::delete().

en-us	### Source  CGraph::get() in *ui/include/classes/api/services/CGraph.php*.
tr	### Kaynak  *ui/include/classes/api/services/CGraph.php* içindeki CGraph::update().

en-us	### Source  CGraphItem::get() in *ui/include/classes/api/services/CGraphItem.php*.
tr	### Kaynak  *ui/include/classes/api/services/CGraph.php* içindeki CGraph::update().

en-us	### Source  CGraphPrototype::create() in *ui/include/classes/api/services/CGraphPrototype.php*.
tr	### Kaynak  CGraphPrototype::create() içinde *ui/include/classes/api/services/CGraphPrototype.php*.

en-us	### Source  CGraphPrototype::delete() in *ui/include/classes/api/services/CGraphPrototype.php*.
tr	### Kaynak  CGraphPrototype::delete() içinde *ui/include/classes/api/services/CGraphPrototype.php*.

en-us	### Source  CGraphPrototype::update() in *ui/include/classes/api/services/CGraphPrototype.php*.
tr	### Kaynak  CGraphPrototype::create() içinde *ui/include/classes/api/services/CGraphPrototype.php*.

en-us	### Source  CGraph::update() in *ui/include/classes/api/services/CGraph.php*.
tr	### Kaynak  *ui/include/classes/api/services/CGraph.php* içindeki CGraph::update().

en-us	### Source  CHaNode::get() in *ui/include/classes/api/services/CHaNode.php*.
tr	### Kaynak  *ui/include/classes/api/services/CDHost.php* içindeki CDHost::get().

en-us	### Source  CHistory::clear() in *ui/include/classes/api/services/CHistory.php*.
tr	### Kaynak  *ui/include/classes/api/services/CDHost.php* içindeki CDHost::get().

en-us	### Source  CHistory::get() in *ui/include/classes/api/services/CHistory.php*.
tr	### Kaynak  *ui/include/classes/api/services/CDHost.php* içindeki CDHost::get().

en-us	### Source  CHost::create() in *ui/include/classes/api/services/CHost.php*.
tr	### Kaynak  *ui/include/classes/api/services/CDHost.php* içindeki CDHost::get().

en-us	### Source  CHost::get() in *ui/include/classes/api/services/CHost.php*.
tr	### Kaynak  *ui/include/classes/api/services/CDHost.php* içindeki CDHost::get().

en-us	### Source  CHostGroup::get() in *ui/include/classes/api/services/CHostGroup.php*.
tr	### Kaynak  CHostGroup::update() içinde *ui/include/classes/api/services/CHostGroup.php*.

en-us	### Source  CHostGroup::massAdd() in *ui/include/classes/api/services/CHostGroup.php*.
tr	### Kaynak  *ui/include/classes/api/services/CHost.php* içindeki CHost::massAdd().

en-us	### Source  CHostGroup::massRemove() in *ui/include/classes/api/services/CHostGroup.php*.
tr	### Kaynak  CHostGroup::update() içinde *ui/include/classes/api/services/CHostGroup.php*.

en-us	### Source  CHostGroup::update() in *ui/include/classes/api/services/CHostGroup.php*.
tr	### Kaynak  CHostGroup::update() içinde *ui/include/classes/api/services/CHostGroup.php*.

en-us	### Source  CHostInterface::create() in *ui/include/classes/api/services/CHostInterface.php*.
tr	### Kaynak  CHostInterface::create() içinde *ui/include/classes/api/services/CHostInterface.php*.

en-us	### Source  CHostInterface::get() in *ui/include/classes/api/services/CHostInterface.php*.
tr	### Kaynak  CHostInterface::get() içinde *ui/include/classes/api/services/CHostInterface.php*.

en-us	### Source  CHostInterface::massAdd() in *ui/include/classes/api/services/CHostInterface.php*.
tr	### Kaynak  CHostInterface::get() içinde *ui/include/classes/api/services/CHostInterface.php*.

en-us	### Source  CHostInterface::massRemove() in *ui/include/classes/api/services/CHostInterface.php*.
tr	### Kaynak  CHostInterface::create() içinde *ui/include/classes/api/services/CHostInterface.php*.

en-us	### Source  CHostInterface::replaceHostInterfaces() in *ui/include/classes/api/services/CHostInterface.php*.
tr	### Kaynak  CHostInterface::create() içinde *ui/include/classes/api/services/CHostInterface.php*.

en-us	### Source  CHost::massAdd() in *ui/include/classes/api/services/CHost.php*.
tr	### Kaynak  *ui/include/classes/api/services/CHost.php* içindeki CHost::massAdd().

en-us	### Source  CHost::massUpdate() in *ui/include/classes/api/services/CHost.php*.
tr	### Kaynak  *ui/include/classes/api/services/CHost.php* içindeki CHost::massAdd().

en-us	### Source  CHostPrototype::create() in *ui/include/classes/api/services/CHostPrototype.php*.
tr	### Kaynak  CHostPrototype::update() içinde *ui/include/classes/api/services/CHostPrototype.php*.

en-us	### Source  CHostPrototype::get() in *ui/include/classes/api/services/CHostPrototype.php*.
tr	### Kaynak  CHostPrototype::update() içinde *ui/include/classes/api/services/CHostPrototype.php*.

en-us	### Source  CHostPrototype::update() in *ui/include/classes/api/services/CHostPrototype.php*.
tr	### Kaynak  CHostPrototype::update() içinde *ui/include/classes/api/services/CHostPrototype.php*.

en-us	### Source  CHousekeeping::update() in *ui/include/classes/api/services/CHousekeeping.php*.
tr	### Kaynak  CHostGroup::update() içinde *ui/include/classes/api/services/CHostGroup.php*.

en-us	### Source  CHttpTest::delete() in *ui/include/classes/api/services/CHttpTest.php*.
tr	### Kaynak  CHttpTest::delete()  içindeki *ui/include/classes/api/services/CHttpTest.php*.

en-us	### Source  CHttpTest::update() in *ui/include/classes/api/services/CHttpTest.php*.
tr	### Kaynak  CHttpTest::update() in *ui/include/classes/api/services/CHttpTest.php*.

en-us	### Source  CIconMap::delete() in *ui/include/classes/api/services/CIconMap.php*.
tr	###Kaynak  CIconMap::delete() içindeki *ui/include/classes/api/services/CIconMap.php*.

en-us	### Source  CIconMap::get() in *ui/include/classes/api/services/CIconMap.php*.
tr	### Kaynak  CIconMap::get() içindeki *ui/include/classes/api/services/CIconMap.php*.

en-us	### Source  CIconMap::update() in *ui/include/classes/api/services/CIconMap.php*.
tr	### Kaynak  CIconMap::update() içinde *ui/include/classes/api/services/CIconMap.php*.

en-us	### Source  CImage::delete() in *ui/include/classes/api/services/CImage.php*.
tr	### Kaynak  *ui/include/classes/api/services/CGraph.php* içindeki CGraph::update().

en-us	### Source  CImage::get() in *ui/include/classes/api/services/CImage.php*.
tr	### Kaynak  *ui/include/classes/api/services/CGraph.php* içindeki CGraph::update().

en-us	### Source  CImage::update() in *ui/include/classes/api/services/CImage.php*.
tr	### Kaynak  *ui/include/classes/api/services/CGraph.php* içindeki CGraph::update().

en-us	### Source  CItem::delete() in *ui/include/classes/api/services/CItem.php*.
tr	### Kaynak  *ui/include/classes/api/services/CItem.php* içindeki CItem::delete().

en-us	### Source  CItem::get() in *ui/include/classes/api/services/CItem.php*.
tr	### Kaynak  *ui/include/classes/api/services/CItem.php* içindeki CItem::delete().

en-us	### Source  CItemPrototype::delete() in *ui/include/classes/api/services/CItemPrototype.php*.
tr	### Kaynak  CItemPrototype::delete() in *ui/include/classes/api/services/CItemPrototype.php*.

en-us	### Source  CItemPrototype::update() in *ui/include/classes/api/services/CItemPrototype.php*.
tr	### Kaynak  CItemPrototype::update() içindeki *ui/include/classes/api/services/CItemPrototype.php*.

en-us	### Source  CItem::update() in *ui/include/classes/api/services/CItem.php*.
tr	### Kaynak  *ui/include/classes/api/services/CItem.php* içindeki CItem::delete().

en-us	### Source  CMaintenance::create() in *ui/include/classes/api/services/CMaintenance.php*.
tr	### Kaynak  CMaintenance::create() içinde *ui/include/classes/api/services/CMaintenance.php*.

en-us	### Source  CMaintenance::get() in *ui/include/classes/api/services/CMaintenance.php*.
tr	### Kaynak  CMaintenance::get() içindeki  *ui/include/classes/api/services/CMaintenance.php*.

en-us	### Source  CMaintenance::update() in *ui/include/classes/api/services/CMaintenance.php*.
tr	### Kaynak  CMaintenance::update() içinde *ui/include/classes/api/services/CMaintenance.php*.

en-us	### Source  CMap::create() in *ui/include/classes/api/services/CMap.php*.
tr	### Kaynak  CMap::create() içindeki *ui/include/classes/api/services/CMap.php*.

en-us	### Source  CMap::delete() in *ui/include/classes/api/services/CMap.php*.
tr	### Kaynak  CMap::delete() içindeki *ui/include/classes/api/services/CMap.php*.

en-us	### Source  CMap::get() in *ui/include/classes/api/services/CMap.php*.
tr	### Kaynak  CMap::get() içindeki *ui/include/classes/api/services/CMap.php*.

en-us	### Source  CMediaType::create() in *ui/include/classes/api/services/CMediaType.php*.
tr	### kaynak  CMediaType::create() içindeki  *ui/include/classes/api/services/CMediaType.php*.

en-us	### Source  CMediaType::get() in *ui/include/classes/api/services/CMediaType.php*.
tr	### Kaynak  CMediaType::get() içindeki *ui/include/classes/api/services/CMediaType.php*.

en-us	### Source  CMediaType::update() in *ui/include/classes/api/services/CMediaType.php*.
tr	### Kaynak  CMediaType::update() içindeki *ui/include/classes/api/services/CMediaType.php*.

en-us	### Source  CProxy::delete() in *ui/include/classes/api/services/CProxy.php*.
tr	### Kaynak  CProxy::delete() içindeki *ui/include/classes/api/services/CProxy.php*.

en-us	### Source  CProxy::update() in *ui/include/classes/api/services/CProxy.php*.
tr	### Kaynak  CProxy::update() içindeki *ui/include/classes/api/services/CProxy.php*.

en-us	### Source  CRegexp::create() in *ui/include/classes/api/services/CRegexp.php*.
tr	### Kaynak  *ui/include/classes/api/services/CRegexp.php* içindeki CRegexp::create().

en-us	### Source  CRegexp::delete() in *ui/include/classes/api/services/CRegexp.php*.
tr	### Kaynak  *ui/include/classes/api/services/CDRule.php* içindeki CDRule::create().

en-us	### Source  CReport::get() in *ui/include/classes/api/services/CReport.php*.
tr	### Kaynak  CReport::get() içindeki *ui/include/classes/api/services/CReport.php*.

en-us	### Source  CReport::update() in *ui/include/classes/api/services/CReport.php*.
tr	### Kaynak  CReport::update() içindeki *ui/include/classes/api/services/CReport.php*.

en-us	### Source  CRole::delete() in *ui/include/classes/api/services/CRole.php*.
tr	### Kaynak  CRole::delete() içindeki *ui/include/classes/api/services/CRole.php*.

en-us	### Source  CRole::get() in *ui/include/classes/api/services/CRole.php*.
tr	### Kaynak  CRole::delete() içindeki *ui/include/classes/api/services/CRole.php*.

en-us	### Source  CRole::update() in *ui/include/classes/api/services/CRole.php*.
tr	### Kaynak  *ui/include/classes/api/services/CDRule.php* içindeki CDRule::create().

en-us	### Source  CScript::delete() in *ui/include/classes/api/services/CScript.php*.
tr	### Kaynak  CScript::delete() içindeki *ui/include/classes/api/services/CScript.php*.

en-us	### Source  CScript::execute() in *ui/include/classes/api/services/CScript.php*.
tr	### Kaynak  CScript::execute() içindeki *ui/include/classes/api/services/CScript.php*.

en-us	### Source  CScript::get() in *ui/include/classes/api/services/CScript.php*.
tr	### Kaynak  CScript::get() içindeki *ui/include/classes/api/services/CScript.php*.

en-us	### Source  CScript::getScriptsByHosts() in *ui/include/classes/api/services/CScript.php*.
tr	### Kaynak  CScript::getScriptsByHosts() içindeki *ui/include/classes/api/services/CScript.php*.

en-us	### Source  CScript::update() in *ui/include/classes/api/services/CScript.php*.
tr	### Kaynak  CScript::update() in *ui/include/classes/api/services/CScript.php*.

en-us	### Source  CService::delete() in *ui/include/classes/api/services/CService.php*.
tr	### Kaynak  CService::delete() içindeki *ui/include/classes/api/services/CService.php*.

en-us	### Source  CService::get() in *ui/include/classes/api/services/CService.php*.
tr	### Kaynak  *ui/include/classes/api/services/CDService.php* içindeki CDService::get().

en-us	### Source  CService::update() in *ui/include/classes/api/services/CService.php*.
tr	### Kaynak  CService::update() içindeki *ui/include/classes/api/services/CService.php*.

en-us	### Source  CSettings::update() in *ui/include/classes/api/services/CSettings.php*.
tr	### Kaynak  CSettings::update() içindeki *ui/include/classes/api/services/CSettings.php*.

en-us	### Source  CTask::get() in *ui/include/classes/api/services/CTask.php*.
tr	### Kaynak   CTask::get()  içindeki *ui/include/classes/api/services/CTask.php*.

en-us	### Source  CTemplate::create() in *ui/include/classes/api/services/CTemplate.php*.
tr	### Kaynak  *ui/include/classes/api/services/CTemplate.php* içindeki CTemplate::create().

en-us	### Source  CTemplateDashboard::create() in *ui/include/classes/api/services/CTemplateDashboard.php*.
tr	### Kaynak  CDashboard::create() içinde *ui/include/classes/api/services/CDashboard.php*.

en-us	### Source  CTemplateDashboard::delete() in *ui/include/classes/api/services/CTemplateDashboard.php*.
tr	### Kaynak  CDashboard::create() içinde *ui/include/classes/api/services/CDashboard.php*.

en-us	### Source  CTemplateDashboard::get() in *ui/include/classes/api/services/CTemplateDashboard.php*.
tr	### Kaynak  CDashboard::create() içinde *ui/include/classes/api/services/CDashboard.php*.

en-us	### Source  CTemplateDashboard::update() in *ui/include/classes/api/services/CTemplateDashboard.php*.
tr	### Kaynak  CTemplateDashboard::update() içindeki *ui/include/classes/api/services/CTemplateDashboard.php*.

en-us	### Source  CTemplate::delete() in *ui/include/classes/api/services/CTemplate.php*.
tr	### Kaynak  CTemplate::delete() içindeki *ui/include/classes/api/services/CTemplate.php*.

en-us	### Source  CTemplate::get() in *ui/include/classes/api/services/CTemplate.php*.
tr	### Kaynak  *ui/include/classes/api/services/CTemplate.php* içindeki CTemplate::create().

en-us	### Source  CTemplate::massAdd() in *ui/include/classes/api/services/CTemplate.php*.
tr	### Kaynak  *ui/include/classes/api/services/CTemplate.php* içindeki CTemplate::create().

en-us	### Source  CTemplate::massRemove() in *ui/include/classes/api/services/CTemplate.php*.
tr	### Kaynak  *ui/include/classes/api/services/CTemplate.php* içindeki CTemplate::create().

en-us	### Source  CTemplate::massUpdate() in *ui/include/classes/api/services/CTemplate.php*.
tr	### Kaynak  *ui/include/classes/api/services/CTemplate.php* içindeki CTemplate::create().

en-us	### Source  CTemplate::update() in *ui/include/classes/api/services/CTemplate.php*.
tr	### Kaynak  *ui/include/classes/api/services/CTemplate.php* içindeki CTemplate::create().

en-us	### Source  CToken::create() in *ui/include/classes/api/services/CToken.php*.
tr	### Kaynak   CToken::create() içindeki *ui/include/classes/api/services/CToken.php*.

en-us	### Source  CToken::get() in *ui/include/classes/api/services/CToken.php*.
tr	### Kaynak  CToken::get() içindeki *ui/include/classes/api/services/CToken.php*.

en-us	### Source  CToken::update() in *ui/include/classes/api/services/CToken.php*.
tr	### Kaynan  CToken::update() içindeki *ui/include/classes/api/services/CToken.php*.

en-us	### Source  CTrend::get() in *ui/include/classes/api/services/CTrend.php*.
tr	### Kaynak  CTrend::get() içindeki *ui/include/classes/api/services/CTrend.php*.

en-us	### Source  CTrigger::delete() in *ui/include/classes/api/services/CTrigger.php*.
tr	### Kaynak  CTrigger::delete() içindeki *ui/include/classes/api/services/CTrigger.php*.

en-us	### Source  CTriggerPrototype::update() in *ui/include/classes/api/services/CTriggerPrototype.php*.
tr	### Kaynak   CTriggerPrototype::update() içindeki  *ui/include/classes/api/services/CTriggerPrototype.php*.

en-us	### Source  CUser::delete() in *ui/include/classes/api/services/CUser.php*.
tr	### Kaynak  *ui/include/classes/api/services/CItem.php* içindeki CItem::delete().

en-us	### Source  CUser::get() in *ui/include/classes/api/services/CUser.php*.
tr	### Kaynak  *ui/include/classes/api/services/CItem.php* içindeki CItem::delete().

en-us	### Source  CUserGroup::create() in *ui/include/classes/api/services/CUserGroup.php*.
tr	### Kaynak  CUserGroup::create() in *ui/include/classes/api/services/CUserGroup.php*.

en-us	### Source  CUserGroup::delete() in *ui/include/classes/api/services/CUserGroup.php*.
tr	### Kaynak  CUserGroup::create() in *ui/include/classes/api/services/CUserGroup.php*.

en-us	### Source  CUserMacro::updateGlobal() in *ui/include/classes/api/services/CUserMacro.php*.
tr	### Kaynak  CUserMacro::updateGlobal() içindeki *ui/include/classes/api/services/CUserMacro.php*.

en-us	### Source  CUser::update() in *ui/include/classes/api/services/CUser.php*.
tr	### Kaynak  CUser::update() içindeki *ui/include/classes/api/services/CUser.php*.

en-us	### Source  CValueMap::create() in *ui/include/classes/api/services/CValueMap.php*.
tr	### Kaynak  CValueMap::create() içindeki *ui/include/classes/api/services/CValueMap.php*.

en-us	### Source  CValueMap::delete() in *ui/include/classes/api/services/CValueMap.php*.
tr	### Kaynak   CValueMap::delete() içindeki *ui/include/classes/api/services/CValueMap.php*.

en-us	### Source  CValueMap::get() in *ui/include/classes/api/services/CValueMap.php*.
tr	### Kaynak   CValueMap::delete() içindeki *ui/include/classes/api/services/CValueMap.php*.

en-us	#### SSH checks     - Some Linux distributions like Debian, Ubuntu do not support encrypted    private keys (with passphrase) if the libssh2 library is installed from    packages. Please see [ZBX-4850](https://support.zabbix.com/browse/ZBX-4850) for more details.     - When using libssh 0.9.x on some Linux distributions with OpenSSH 8, SSH checks may    occasionally report "Cannot read data from SSH server". This is caused    by a libssh [issue](https://gitlab.com/libssh/libssh-mirror/-/merge_requests/101)     ([more detailed report](https://bugs.libssh.org/T231)). The error is expected     to have been fixed by a stable libssh 0.9.5 release. See also     [ZBX-17756](https://support.zabbix.com/browse/ZBX-17756) for details.     - Using the pipe "|" in the SSH script may lead to a     "Cannot read data from SSH server" error. In this case it is recommended     to upgrade the libssh library version. See also [ZBX-21337](https://support.zabbix.com/browse/ZBX-21337)     for details.
tr	#### SSH checks     - Some Linux distributions like Debian, Ubuntu do not support encrypted    private keys (with passphrase) if the libssh2 library is installed from    packages. Please see [ZBX-4850](https://support.zabbix.com/browse/ZBX-4850) for more details.     - When using libssh 0.9.x on some Linux distributions with OpenSSH 8 SSH checks may    occasionally report "Cannot read data from SSH server". This is caused    by a libssh [issue](https://gitlab.com/libssh/libssh-mirror/-/merge_requests/101)     ([more detailed report](https://bugs.libssh.org/T231)). The error is expected     to have been fixed by a stable libssh 0.9.5 release. See also     [ZBX-17756](https://support.zabbix.com/browse/ZBX-17756) for details.     - Using the pipe "|" in the SSH script may lead to a     "Cannot read data from SSH server" error. In this case it is recommended     to upgrade the libssh library version. See also [ZBX-21337](https://support.zabbix.com/browse/ZBX-21337)     for details.

en-us	##### Starting Zabbix server as cluster node  Two parameters are required  in the server [configuration](/manual/appendix/config/zabbix_server)  to start a Zabbix server as cluster node:  -    **HANodeName** parameter must be specified for each Zabbix server  that will be an HA cluster node.   This is a unique node identifier (e.g. `zabbix-node-01`) that the server will be referred to in agent  and proxy configurations. If you do not specify HANodeName, then the server will be  started in standalone mode.  -    **NodeAddress** parameter must be specified for each node.   The NodeAddress parameter (address:port) will be used by Zabbix frontend to connect  to the active server node. NodeAddress must match the IP or FQDN name of the respective Zabbix server.  Restart all Zabbix servers after making changes to the configuration files. They will  now be started as cluster nodes. The new status of the servers can be seen in  *Reports* → *[System information](/manual/web_interface/frontend_sections/reports/status_of_zabbix#status_of_ha_cluster_nodes)*  and also by running:  ``` zabbix_server -R ha_status ```  This runtime command will log the current HA cluster status into the Zabbix server log (and to stdout):  ![](../../../../assets/en/manual/config/runtime_ha_status.png){width="600"}
tr	##### Starting Zabbix server as cluster node  Two parameters are required  in the server [configuration](/manual/appendix/config/zabbix_server)  to start a Zabbix server as cluster node:  -    **HANodeName** parameter must be specified for each Zabbix server  that will be an HA cluster node.   This is a unique node identifier (e.g. `zabbix-node-01`) that the server will be referred to in agent and proxy  configurations. If you do not specify HANodeName, then the server will be started  in standalone mode.  -    **NodeAddress** parameter must be specified for each node.   The NodeAddress parameter (address:port) will be used by Zabbix frontend to connect  to the active server node. NodeAddress must match the IP or FQDN name of the respective Zabbix server.  Restart all Zabbix servers after making changes to the configuration files. They will  now be started as cluster nodes. The new status of the servers can be seen in  *Reports* → *[System information](/manual/web_interface/frontend_sections/reports/status_of_zabbix#status_of_ha_cluster_nodes)*  and also by running:  ``` zabbix_server -R ha_status ```  This runtime command will log the current HA cluster status into the Zabbix server log (and to stdout):  ![](../../../../assets/en/manual/config/runtime_ha_status.png){width="600"}

en-us	##### Start up manually  If the above does not work you have to start it manually. Find the path to the zabbix\_agentd binary and execute:      shell> zabbix_agentd
tr	##### Start up manually  If the above does not work you have to start it manually. Find the path to the zabbix\_agentd binary and execute:      shell> zabbix_agentd

en-us	##### Start up manually  If the above does not work you have to start it manually. Find the path to the zabbix\_proxy binary and execute:      shell> zabbix_proxy  You can use the following command line parameters with Zabbix proxy:      -c --config <file>              path to the configuration file     -f --foreground                 run Zabbix proxy in foreground     -R --runtime-control <option>   perform administrative functions     -h --help                       give this help     -V --version                    display version number  Examples of running Zabbix proxy with command line parameters:      shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf     shell> zabbix_proxy --help     shell> zabbix_proxy -V
tr	##### Start up manually  If the above does not work you have to start it manually. Find the path to the zabbix\_proxy binary and execute:      shell> zabbix_proxy  You can use the following command line parameters with Zabbix proxy:      -c --config <file>              path to the configuration file     -f --foreground                 run Zabbix proxy in foreground     -R --runtime-control <option>   perform administrative functions     -h --help                       give this help     -V --version                    display version number  Examples of running Zabbix proxy with command line parameters:      shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf     shell> zabbix_proxy --help     shell> zabbix_proxy -V

en-us	##### Start up manually  If the above does not work you have to start it manually. Find the path to the zabbix\_server binary and execute:      shell> zabbix_server  You can use the following command line parameters with Zabbix server:      -c --config <file>              path to the configuration file (default is /usr/local/etc/zabbix_server.conf)     -f --foreground                 run Zabbix server in foreground     -R --runtime-control <option>   perform administrative functions     -h --help                       give this help     -V --version                    display version number  Examples of running Zabbix server with command line parameters:      shell> zabbix_server -c /usr/local/etc/zabbix_server.conf     shell> zabbix_server --help     shell> zabbix_server -V
tr	##### Start up manually  If the above does not work you have to start it manually. Find the path to the zabbix\_server binary and execute:      shell> zabbix_server  You can use the following command line parameters with Zabbix server:      -c --config <file>              path to the configuration file (default is /usr/local/etc/zabbix_server.conf)     -f --foreground                 run Zabbix server in foreground     -R --runtime-control <option>   perform administrative functions     -h --help                       give this help     -V --version                    display version number  Examples of running Zabbix server with command line parameters:      shell> zabbix_server -c /usr/local/etc/zabbix_server.conf     shell> zabbix_server --help     shell> zabbix_server -V

en-us	##### Start-up scripts  The scripts are used to automatically start/stop Zabbix processes during system's start-up/shutdown. The scripts are located under directory misc/init.d.
tr	##### Start-up scripts  The scripts are used to automatically start/stop Zabbix processes during system's start-up/shutdown. The scripts are located under directory misc/init.d.

en-us	##### Step 1  To define your own theme you'll need to create a CSS file and save it in the `assets/styles/` folder (for example, *custom-theme.css*). You can either copy the files from a different theme and create your theme based on it or start from scratch.
tr	##### Aşama 1  Kendi temanızı tanımlamak için bir CSS dosyası oluşturmanız ve bunu içine kaydetmeniz gerekir. "assets/styles/" klasörü (örneğin, *özel-tema.css*). Yapabilirsiniz ya dosyaları farklı bir temadan kopyalayın ve temanızı temel alarak oluşturun üzerinde veya sıfırdan başlayın.

en-us	##### Step 2  Add your theme to the list of themes returned by the APP::getThemes() method. You can do this by overriding the ZBase::getThemes() method in the APP class. This can be done by adding the following code before the closing brace in *include/classes/core/APP.php*:        public static function getThemes() {           return array_merge(parent::getThemes(), [               'custom-theme' => _('Custom theme')           ]);       }  ::: noteimportant Note that the name you specify within the first pair of quotes must match the name of the theme file without extension. :::  To add multiple themes, just list them under the first theme, for example:        public static function getThemes() {           return array_merge(parent::getThemes(), [               'custom-theme' => _('Custom theme'),               'anothertheme' => _('Another theme'),               'onemoretheme' => _('One more theme')           ]);       }  Note that every theme except the last one must have a trailing comma.  ::: notetip To change graph colors, the entry must be added in the *graph\_theme* database table. :::
tr	##### Adım 2  Temanızı APP::getThemes() tarafından döndürülen temalar listesine ekleyin yöntem. Bunu, içindeki ZBase::getThemes() yöntemini geçersiz kılarak yapabilirsiniz. APP sınıfı. Bu, önce aşağıdaki kodu ekleyerek yapılabilir. *include/classes/core/APP.php*: içindeki kapanış ayracı        genel statik işlev getThemes() {           return array_merge(parent::getThemes(), [               'özel tema' => _('Özel tema')           ]);       }  ::: notönemli İlk içinde belirttiğiniz adın tırnak çifti, tema dosyasının adıyla eşleşmelidir. eklenti. :::  Birden çok tema eklemek için bunları ilk temanın altında listelemeniz yeterlidir. örnek:        genel statik işlev getThemes() {           return array_merge(parent::getThemes(), [               'özel tema' => _('Özel tema'),               'başka bir tema' => _('Başka bir tema'),               'onemoretheme' => _('Bir tema daha')           ]);       }  Sonuncusu hariç her temanın sonunda bir virgül olması gerektiğini unutmayın.  ::: not ipucu Grafik renklerini değiştirmek için giriş, *graph\_theme* veritabanı tablosu. :::