We're using Zabbix 2.4.5 on Linux server and Linux and Windows clients.
We've done custom items, including items that accept parameters, before on Linux hosts, and it works well. If you're not familar with custom items, they're described here:
Now we want to do the same thing on a Windows host: pass a Windows path to a custom item, for it to do some checking and then report back.
Built-in items will accept a Windows path, but for custom items, the UnsafeUserParameters pretty much rules out having any parameter that looks like a Windows path. You can't use \ or " in a parameter, which pretty much rules out paths like
"C:\Program Files\Windows"
and we tried to be tricky and use the 8.3 equivalent to that path, but even ~ is included in the UnsafeUserParameters list, so even that doesn't work.
Is it really necessary to enable UnsafeUserParameters just to be able to use Windows paths? It seems like the Windows agent could (and should) relax some of the character restrictions for the UnsafeUserParameters. For example, ~ and \ are "normal" parts of paths on a Windows system, not something special like they are on a UNIX or Linux box.
Tim
We've done custom items, including items that accept parameters, before on Linux hosts, and it works well. If you're not familar with custom items, they're described here:
Now we want to do the same thing on a Windows host: pass a Windows path to a custom item, for it to do some checking and then report back.
Built-in items will accept a Windows path, but for custom items, the UnsafeUserParameters pretty much rules out having any parameter that looks like a Windows path. You can't use \ or " in a parameter, which pretty much rules out paths like
"C:\Program Files\Windows"
and we tried to be tricky and use the 8.3 equivalent to that path, but even ~ is included in the UnsafeUserParameters list, so even that doesn't work.
Is it really necessary to enable UnsafeUserParameters just to be able to use Windows paths? It seems like the Windows agent could (and should) relax some of the character restrictions for the UnsafeUserParameters. For example, ~ and \ are "normal" parts of paths on a Windows system, not something special like they are on a UNIX or Linux box.
Tim