Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trigger Panel Info Column URL with Macros not resolving #190

Closed
mdiorio opened this issue Apr 8, 2016 · 5 comments
Closed

Trigger Panel Info Column URL with Macros not resolving #190

mdiorio opened this issue Apr 8, 2016 · 5 comments

Comments

@mdiorio
Copy link

mdiorio commented Apr 8, 2016

This seems to be a Zabbix issue but wanted to make you aware of it.

So my Triggers for website monitoring are all templated and working properly. I have a URL on the trigger with a Macro in it and it works fine within Zabbix. I can view the trigger and open the URL and it processes the macro

http://{HOST.HOST}/content-check/checknow.cfm?mode=all

The Trigger Panel is not getting the macro converted. I'm getting an URL encoded, un-converted macro

http://%7Bhost.host%7D/content-check/checknow.cfm?mode=all

In the API, there are flags for:
expandComment flag Expand macros in the trigger comment.
expandDescription flag Expand macros in the name of the trigger.
expandExpression flag Expand functions and macros in the trigger expression.

But there is no equivalent for expandURL, so as you can see, macros don't get expanded when requested through the API.

I cross posted in the Zabbix forum as well:
https://www.zabbix.com/forum/showthread.php?p=181416#post181416

Hope this gets implemented on the Zabbix side quickly.

Thanks.

Max

@volter
Copy link
Contributor

volter commented Jun 21, 2016

Which version of Zabbix is that?

@mchihi
Copy link

mchihi commented Sep 1, 2016

any update please regarding this issue. using Macros instead of host name.
http://{HOST.HOST}/content-check/checknow.cfm?mode=all

@alexanderzobnin alexanderzobnin added this to the Grafana-Zabbix 3.3 milestone Feb 10, 2017
@alexanderzobnin
Copy link
Collaborator

This is Zabbix API limitations.

@timyllym
Copy link

I have the same problem. I think there won't be any fixes to Zabbix API in near future. I fixed this by utilizing existing code and made a PR #759.

@alexanderzobnin
Copy link
Collaborator

@timyllym Thank! I'll take a look.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants