-
Problem report
-
Resolution: Workaround proposed
-
Major
-
None
-
4.0.4
-
Ubuntu 16.04.1 LTS
Steps to reproduce:
I have a function called "dnsverify" which takes a domain and an IP and this functions checks if they match up and does this by checking the authorative server to get an early warning.
**Host is IP-based, but a DNS is entered and with a templated item/trigger it is compared with the IP of the host using the self-defined function dnsverify[\{HOST.DNS}, \{IPADDRESS} ]
This function is properly working. The problem with old values of trigger macros is present in all triggers.
Both domains "htnk.mr-wolf.nl" and "remote.htnk.nl" do not yet exist at time of writing. This function is used as an example because it currently shows as trigger in my dashboard.
Trigger is supposed to show "DNS of {HOST.DNS} does not resolve"
{HOST.DNS} starts out with value htnk.mr-wolf.nl
Trigger shows "DNS of htnk.mr-wolf.nl does not resolve" (this is good)
I then decide to use a different DNS name, namely remote.htnk.nl
The trigger in my dashboard keeps saying
"DNS of htnk.mr-wolf.nl does not resolve"
it should say
"DNS of remote.htnk.nl does not resolve"
- part of
-
ZBXNEXT-4942 Final fix for {ITEM.LASTVALUE1} in Monitoring–>Problems as a live view
- Closed