Greetings!
While building a template, I make an error or two along the way, and for example let's say I used dynamic items with SNMP OIDs that detect a value from a text string which I got wrong. It will show as "not supported", meanwhile all I had to do was fix the string so it picks it up correctly.
Well, if I click the "not supported" text, it displays "disabled". Click on the "disabled" and it goes back to "not supported". It literally permanently bans my item, meanwhile I DID fix the string so it should be picking it up correctly. Even if I unlink and re-add the template, it still won't work. I have to unlink and CLEAR all data, then re-add the template, and it will work perfectly.
When building a template, I can understand this. But what if I am trying to dynamically detect a process which has multiple identical hrSWRunName and hrSWRunParameters values, but the hrSWRunPath is unique. I can monitor them using that, but what if the path changes, I have to correct it and lose ALL data across the entire host for one character of a single item? and this is not special to just this example, I get this frequently on a daily basis with other situations so I had to finally ask you guys to see if you have a work-around for this perma-item-ban.
I was thinking "well, in this case, I'll just manually flip the switch in the database to re-enable an item in these rare cases." Still is the plan. But I can't find the exact location of this in the DB. I was sure a column in the items table would change, but it doesn't seem to be the case, one "not supported" and one fully-enabled item row seem to be virtually identical. No other table is jumping out as a suspect here, does anyone know how zabbix handles this?
While building a template, I make an error or two along the way, and for example let's say I used dynamic items with SNMP OIDs that detect a value from a text string which I got wrong. It will show as "not supported", meanwhile all I had to do was fix the string so it picks it up correctly.
Well, if I click the "not supported" text, it displays "disabled". Click on the "disabled" and it goes back to "not supported". It literally permanently bans my item, meanwhile I DID fix the string so it should be picking it up correctly. Even if I unlink and re-add the template, it still won't work. I have to unlink and CLEAR all data, then re-add the template, and it will work perfectly.
When building a template, I can understand this. But what if I am trying to dynamically detect a process which has multiple identical hrSWRunName and hrSWRunParameters values, but the hrSWRunPath is unique. I can monitor them using that, but what if the path changes, I have to correct it and lose ALL data across the entire host for one character of a single item? and this is not special to just this example, I get this frequently on a daily basis with other situations so I had to finally ask you guys to see if you have a work-around for this perma-item-ban.
I was thinking "well, in this case, I'll just manually flip the switch in the database to re-enable an item in these rare cases." Still is the plan. But I can't find the exact location of this in the DB. I was sure a column in the items table would change, but it doesn't seem to be the case, one "not supported" and one fully-enabled item row seem to be virtually identical. No other table is jumping out as a suspect here, does anyone know how zabbix handles this?
Comment