Wrong {TRIGGER.URL} in Pushover notifications

[barannikov]

I am struggling with trigger URLs which are coming with notifications from Pushover. My Zabbix URL is correct: www.zabbixserver.com/zabbix/ but trigger URLs are sent like https://www.zabbixserver.com/tr_even...blah-blah-blah instead of https://www.zabbixserver.com/zabbix/...blah-blah-blah.

How can I bulk change trigger URLs to make it work?

Zabbix documentation is ether lacks it or the search is doomed.

TRANSLATE with x
English

Arabic	Hebrew	Polish
Bulgarian	Hindi	Portuguese
Catalan	Hmong Daw	Romanian
Chinese Simplified	Hungarian	Russian
Chinese Traditional	Indonesian	Slovak
Czech	Italian	Slovenian
Danish	Japanese	Spanish
Dutch	Klingon	Swedish
English	Korean	Thai
Estonian	Latvian	Turkish
Finnish	Lithuanian	Ukrainian
French	Malay	Urdu
German	Maltese	Vietnamese
Greek	Norwegian	Welsh
Haitian Creole	Persian

TRANSLATE with
COPY THE URL BELOW

Back

EMBED THE SNIPPET BELOW IN YOUR SITE

Enable collaborative features and customize widget: Bing Webmaster Portal
Back

[barannikov]

Thanks for giving me the idea to check macros! It turned out that my {$ZABBIX.URL} is used for concatenating trigger/event links and it lacked the full path, thus causing broken URLs. Kudos!

[Brambo]

Did you set the frontend URL correct?
Administration > General > Other

[barannikov]

It was wrong, indeed, but fixing it didn't fix {TRIGGER.URL} in Pushover notifications.

[Brambo]

I do it like this in the media template: paramater ServerTrigger =

{$ZINSTANCE}tr_events.php?triggerid={TRIGGER.ID}&eventid={EVENT.ID}

Where the macro ZINSTANCE is the URL including a / at the end example: http://examplezabbix.com/ or in your scenario: https://www.zabbixserver.com/zabbix/
The macro is set as a global macro in the administration section.
In the media type I set a parameter to the earlier mentioned value and in the script of this media template I used it where I need it.

[barannikov]

Thanks for giving me the idea to check macros! It turned out that my {$ZABBIX.URL} is used for concatenating trigger/event links and it lacked the full path, thus causing broken URLs. Kudos!

[barannikov]

Hm, it turned out to be too early to open the champagne. After I changed global {$ZABBIX.URL} from https://example.com/ to https://example.com/zabbix/ pushover sends me https://example.com/zabbix/ in the end of the message instead of event/trigger URL though message template contains {TRIGGER.URL}:

Problem started at {EVENT.TIME} on {EVENT.DATE}
Host: {HOST.NAME}
Problem name: {EVENT.NAME}
Severity: {EVENT.SEVERITY}
{TRIGGER.URL}​

Weird.

[Brambo]

Looking at the default pushover media type the trigger.url should be atleast something like:

so zabbix URL/tr_events etc etc. If you get something else i think you change things away from default.
You could change the media type and add Zabbix.log lines to troubleshoot.

[barannikov]

Thank you for looking into it. My url pushover media variable was missing, leaving only url_title variable, thus causing unclickable wrong link in the end of every message. Thanks a million!

[irontmp]

I had a similar issue and found that the easiest solution is to check the Zabbix frontend URL configuration first. Make sure it includes the /zabbix/ path, for example https://www.zabbixserver.com/zabbix/. If you have many URLs to review, Bulk URL Opener can also be useful for checking multiple generated links quickly. If the frontend URL is correct but {TRIGGER.URL} is still generating the wrong path, the URLs are probably defined in the trigger configuration or notification template. Rather than editing them one by one, you can update them in bulk through the Zabbix API.