Zabbix Documentation 5.0

3.04.04.45.0 (current)| In development:5.2 (devel)| Unsupported:1.82.02.22.43.23.44.2Guidelines

User Tools

Site Tools


manual:web_interface:frontend_sections:administration:scripts

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
manual:web_interface:frontend_sections:administration:scripts [2020/05/12 14:22]
martins-v enableremotecommands status clarified (ZBX-17367, ZBX-17586, ZBX-17700)
manual:web_interface:frontend_sections:administration:scripts [2020/05/12 14:23] (current)
martins-v fixing link target
Line 54: Line 54:
 |//​Name// ​ |Unique name of the script.\\ Since Zabbix 2.2 the name can be prefixed with the desired path, for example, ''​Default/'',​ putting the script into the respective directory. When accessing scripts through the menu in monitoring sections, they will be organized according to the given directories.\\ A script cannot have the same name as an existing directory (and vice versa). A script name must be unique within its directory.\\ Unescaped script names are validated for uniqueness, i.e. "​Ping"​ and "​\Ping"​ cannot be added in the same folder. A single backslash escapes any symbol directly after it. For example, characters '/'​ and '​\'​ can be escaped by backslash, i.e. \/ or \\.  | |//​Name// ​ |Unique name of the script.\\ Since Zabbix 2.2 the name can be prefixed with the desired path, for example, ''​Default/'',​ putting the script into the respective directory. When accessing scripts through the menu in monitoring sections, they will be organized according to the given directories.\\ A script cannot have the same name as an existing directory (and vice versa). A script name must be unique within its directory.\\ Unescaped script names are validated for uniqueness, i.e. "​Ping"​ and "​\Ping"​ cannot be added in the same folder. A single backslash escapes any symbol directly after it. For example, characters '/'​ and '​\'​ can be escaped by backslash, i.e. \/ or \\.  |
 |//​Type// ​ |Click the respective button to select script type - [[:​manual/​config/​notifications/​action/​operation/​remote_command#​ipmi_remote_commands|IPMI command]] or Script. ​ | |//​Type// ​ |Click the respective button to select script type - [[:​manual/​config/​notifications/​action/​operation/​remote_command#​ipmi_remote_commands|IPMI command]] or Script. ​ |
-|//Execute on//  |Click the respective button to execute the script on:\\ **Zabbix agent** - the script will be executed by Zabbix agent (if enabled by [[:​manual/​appendix/​config/​zabbix_agent|EnableRemoteCommands]]/​if system.run item is allowed) on the host\\ **Zabbix server (proxy)** - the script will be executed by Zabbix server or proxy (if enabled by [[:​manual/​appendix/​config/​zabbix_proxy|EnableRemoteCommands]] - depending on whether the host is monitored by server or proxy\\ **Zabbix server** - the script will be executed by Zabbix server only  |+|//Execute on//  |Click the respective button to execute the script on:\\ **Zabbix agent** - the script will be executed by Zabbix agent (if enabled by [[:​manual/​appendix/​config/​zabbix_agentd|EnableRemoteCommands]]/​if system.run item is allowed) on the host\\ **Zabbix server (proxy)** - the script will be executed by Zabbix server or proxy (if enabled by [[:​manual/​appendix/​config/​zabbix_proxy|EnableRemoteCommands]] - depending on whether the host is monitored by server or proxy\\ **Zabbix server** - the script will be executed by Zabbix server only  |
 |//​Commands// ​ |Enter full path to the commands to be executed within the script.\\ The following macros are supported in the commands: {HOST.CONN},​ {HOST.IP}, {HOST.DNS}, {HOST.HOST},​ {HOST.NAME}. If a macro may resolve to a value with spaces (for example, host name), don't forget to quote as needed.\\ Since Zabbix 2.2, [[manual:​config:​macros:​usermacros|user macros]] are supported in script commands. ​ | |//​Commands// ​ |Enter full path to the commands to be executed within the script.\\ The following macros are supported in the commands: {HOST.CONN},​ {HOST.IP}, {HOST.DNS}, {HOST.HOST},​ {HOST.NAME}. If a macro may resolve to a value with spaces (for example, host name), don't forget to quote as needed.\\ Since Zabbix 2.2, [[manual:​config:​macros:​usermacros|user macros]] are supported in script commands. ​ |
 |//​Description// ​ |Enter a description for the script. ​  | |//​Description// ​ |Enter a description for the script. ​  |