Bug(s) Multiple :: Item Linkage - 1.1beta6 & Create trigger on status.last(0)
This is really two separate issues:
1) I was speaking to James Wells today because I was trying to create a trigger on status in the documentation example. After a bit of mocking about together we realized the value/item is no longer supported or has been changed. What happened to this? I feel it is the penultimate test as it would indicate if the server could talk to the client (even if the communication was garbled) is different from agent.ping which requires an intelligent response. This is even more critical when a host has a unknown status, suppose you add a host, how do you create an alert on that host if it not does connect? If a host is defined and Monitored and has a trigger for agent.ping.last(0)#1&agent.ping.prev(0)#1 then it should DEFINITELY alert even if it is an active zabbix_agent check and this is NOT the case on my running instance.
2) Is encountered in the following scenario. Create a template host (A), ad items to it. Create a template host (B) and make his parent (A) and all the items in (A) do not get assigned to (B). He also commented (and he apologizes for not being online because his internet is down) that there used to be a copy all button which would workaround this issue.
I feel this is a critical problem in the templating structure. In effect, I have to know ALL of my children BEFORE I have identified AND and linked them to the parents. That is a bit difficult to forsee especially when you are working with hundreds of hosts/items. So I cannot just drop my tables and rebuild, I have hundreds of item entries to recreate and what if I decide to reorganize and add a new template?
Is there any progress on this problem? Is there a workaround? Does anybody have any suggestions? I presume this would be resolved before Zabbix enters RC status.
1) I was speaking to James Wells today because I was trying to create a trigger on status in the documentation example. After a bit of mocking about together we realized the value/item is no longer supported or has been changed. What happened to this? I feel it is the penultimate test as it would indicate if the server could talk to the client (even if the communication was garbled) is different from agent.ping which requires an intelligent response. This is even more critical when a host has a unknown status, suppose you add a host, how do you create an alert on that host if it not does connect? If a host is defined and Monitored and has a trigger for agent.ping.last(0)#1&agent.ping.prev(0)#1 then it should DEFINITELY alert even if it is an active zabbix_agent check and this is NOT the case on my running instance.
2) Is encountered in the following scenario. Create a template host (A), ad items to it. Create a template host (B) and make his parent (A) and all the items in (A) do not get assigned to (B). He also commented (and he apologizes for not being online because his internet is down) that there used to be a copy all button which would workaround this issue.
I feel this is a critical problem in the templating structure. In effect, I have to know ALL of my children BEFORE I have identified AND and linked them to the parents. That is a bit difficult to forsee especially when you are working with hundreds of hosts/items. So I cannot just drop my tables and rebuild, I have hundreds of item entries to recreate and what if I decide to reorganize and add a new template?
Is there any progress on this problem? Is there a workaround? Does anybody have any suggestions? I presume this would be resolved before Zabbix enters RC status.