[ZBX-4963] lld trigger prototypes missing half the information on hosts Created: 2012 May 08 Updated: 2017 May 30 Resolved: 2015 Feb 23 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | API (A) |
Affects Version/s: | 2.0.0rc3, 2.0.1 |
Fix Version/s: | 2.0.2rc1, 2.1.0 |
Type: | Incident report | Priority: | Critical |
Reporter: | Igor Urazov | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 0 |
Labels: | lld, trigger | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Issue Links: |
|
Description |
I have template with discovery rule for vfs.fs.discovery and rule has trigger for checking low free space. Trigger has severity "Average". If I check discovery rule in host configuration which has this template linked, it has severity "Not classified". The same severity then applies to generated triggers. |
Comments |
Comment by richlv [ 2012 May 08 ] |
seems to be same as |
Comment by richlv [ 2012 May 08 ] |
btw, might have been created by |
Comment by Igor Urazov [ 2012 May 09 ] |
Hmm, unlinking template, and linking it again generated triggers with correct severity. But I have two hundred hosts linked to this template and I'd like not to lose trends due to relinking as template holds a lot of other items and graphs. Is there any other solution? Maybe some non-common SQL query? |
Comment by richlv [ 2012 May 09 ] |
actually, seems to happen in a setup here as well, and dependencies haven't been set at all. will try to investigate a bit more |
Comment by Alexandru Nica [ 2012 May 29 ] |
I can confirm the bug in version 2.0.0. Unlinking and linking again works. |
Comment by richlv [ 2012 May 30 ] |
does anybody have exact steps to reproduce this ? |
Comment by Attilla de Groot [ 2012 Jun 08 ] |
Ik can confirm the behavior but not reproduce it yet. It currently seems to happen randomly, because I've added two triggers rougly at the same time. For the first everything is inherited and for the second not. |
Comment by Alexandru Nica [ 2012 Jun 27 ] |
Another related issue with LLD is that sometimes you get orphaned graphs. I have a prototype graph named "VOL {#VOLDRIVE} ({#VOLLABEL}) free space" which populates multiple hosts with graphs like "Vol C: (System) free space". In one instance I changed the volume label from "System" to "Windows". |
Comment by richlv [ 2012 Jun 27 ] |
could you please open a new issue about the graph problem ? |
Comment by richlv [ 2012 Jul 10 ] |
the problem here is that we have an issue (and i've seen it myself), but we don't have exact steps to reproduce it. does anybody have simple, specific steps (starting with "create template, create host"...) that always exhibits this problem ? |
Comment by Aristarkh Zagorodnikov [ 2012 Jul 10 ] |
For me it happens with linked templates. I spent around 4 hours debugging the problem, and it appears that certain trigger information is "baked" into linked template and the not updated when the other linked template changes. |
Comment by richlv [ 2012 Jul 11 ] |
arrgh. the steps to reproduce turned out to be very simple after all... thanks to sandra for sending them in just create a new trigger prototype in a template that is already linked to a host. prototype in template is correct, but prototype in host is broken (wondering why would the logic differ here...) interestingly, query for creating prototype on template is like this : but the one for host : as can be seen, it's not just the severity (but it makes it easier to spot) - "Multiple PROBLEM events generation", "URL" and "status" would also be missing on host |
Comment by richlv [ 2012 Jul 12 ] |
if anybody is suffering from this issue, updating (changing) severity in the template trigger prototype should fix it in the host trigger prototype (same with other affected fields) |
Comment by Pavels Jelisejevs (Inactive) [ 2012 Jul 13 ] |
RESOLVED in svn://svn.zabbix.com/branches/dev/ZBX-4963. |
Comment by Pavels Jelisejevs (Inactive) [ 2012 Jul 16 ] |
Fixed in 2.0.2rc1 r28891 and 2.1.0 r28892. CLOSED. |
Comment by Matthias Ronge [ 2013 Dec 13 ] |
Updating / changing severity in the template trigger prototype fixes the problem for currently detected file systems, but new ones being detected will get ‘not classified’ again. |
Comment by Alexander Vladishev [ 2014 Nov 06 ] |
Please confirm the issue with latest 2.0.x, 2.2.x or 2.4.x versions. |
Comment by Alexander Vladishev [ 2015 Feb 23 ] |
I close the issue. Feel free to reopen if the issue still reproducible in latest releases. |