Keep lost resources period zabbix. Scheduling is supported since Zabbix 3.

Keep lost resources period zabbix Could you please help me to try to understand where i'm wrong? Thank you very much. So far so good, but I'm looking for a way to automatically delete these servers from Zabbix one they're shut down. It is better to use formula like "Now + Keep lost resources period (in days)" to avoid any issues. According to Zabbix 5. discovery; Keep lost resources period (in days): 0. If there is a new item in master data, discovery will add it. Joined: May 2018; Posts: 71 #2. "Keep lost resources period (in days)" defines how long item will be kept until removed from list. 2 upgrade with MySQL upgrades. " I assume that the Items/Triggers was created by Discovery Mounted Filesystem process. Export. Isso quer dizer que elas só existem dentro do escopo de outro elemento do Zabbix, assim sendo elas podem ser acessadas ao clicar no link Descoberta do elemento de origem. By obsolete, I mean: resources that belong to the prototype, but is no longer discovered (for example we delete VLAN); resources that have ceased to pass through the I added about 50 switches to my zabbix via the Mikrotik SNMP Template and now it monitors a ton of customer interfaces which it doesnt need to (about 30k items which I dont need monitored) I don't want to delete them by hand because it would take ages. It is better to use Keep lost resources period is an arbitrary value here – once again, depending on your policies regarding LLD entities. There is also no limit for custom low-level discovery rules. Buttons below the list offer some mass-editing options: Enable - change the low-level discovery rule status to Enabled; Disable - change the low-level discovery rule status to Disabled; Delete - delete the low-level discovery rules Zabbix Template Guidelines. Now you Scheduling is supported since Zabbix 3. Preprocessing, Prometheus to JSON. Buttons below the list offer some mass-editing options: Enable - change the low-level discovery rule status to Enabled; Disable - change the low-level discovery rule status to Disabled; Delete - delete the low-level discovery rules If you want to remove previously discovered disks, temporarily set "Keep lost resources period" to 0 in your discovery rules, then in case of active agents wait for 1 hour (discovery period) or in case of passive ones run the discovery rule manually, it will delete all disks except "0 C:". ) This is dependent on the discovery rule setting "Keep lost resources period". So triggers will fire up for 30 more days, if the default period is set. When discovered entities become 'Not discovered anymore', an orange lifetime indicator is displayed in the item list Atlassian Jira Project Management Software; About Jira; Report a problem; Powered by a free Atlassian Jira open source license for SIA Zabbix. 6). 2h, 1d, since Zabbix 3. Type: New Feature Request Status: To configure a new low-level discovery rule, click on the Create discovery rule button at the top right corner. Need to come up with a mechanism for automatic/manual removal of obsolete resources. Version: 20. To configure a new low-level discovery rule, click on the Create discovery rule button at the top right corner. Keep lost resources period: This field allows you to specify the duration for how long the discovered entity will be retained (won't be deleted) once its discovery status becomes "Not discovered anymore" (between 1 hour to 25 years; or "0"). 2) and graphs (until Zabbix 2. 0 online manual, "When discovered entities become 'Not discovered anymore', a lifetime indicator is displayed in the item list. Any suggestion will be This tool aggregates status information of entities in some cases to the managing entity to improve the practical usage with zabbix (example: aggregation of the pod statuses to the deployment which manages the pods) Disappearing entities Keep lost resources period is how long it will keep them. 18). Type: Change Request Resolution: Won't Do Priority: Trivial . Example, incorrect clock may cause the following: "The item is not discovered anymore and will be deleted in 19y To configure a new low-level discovery rule, click on the Create discovery rule button at the top right corner. I've just set it to use the macros for filesystem types instead, which should ignore /proc /dev etc. So I'm guessing it's either not running or something isn't configured correctly. does not pass the filter anymore or is not discovered at all. 2 User macros supported by location Overview. Log In. Restart the Zabbix Agent and test your new custom item keys with zabbix_get. In this case, we will discard the lost resource immediately – Keep Lost Hi, All discovered entities will be removed automatically if you remove the corresponding item/trigger/graph prototype. The Keep lost resources period is the value, which indicates how long an item should retain the resources when they are To configure a new low-level discovery rule, click on the Create discovery rule button in the top right-hand corner. vm. To start viewing messages, select the forum that you want to visit from the selection below. User-definable macros are supported in the following locations:. ; Check now - perform discovery based on the discovery rules If think if the services were already discovered before you added the regular expression, they won't disappear until the 'keep lost resources period' has expired. In the Preprocessing tab, there is a new preprocessing step called Prometheus to Next, we create a discovery rule. Discovered hosts are prefixed with the name of the discovery rule that created them, in the host list. Sometimes it can lead for triggers to go into problem state. 2. As regras de descoberta (LLD) são entidades derivadas. 08. ; Disable - change the low-level discovery rule status to Disabled. I'm a bit confused as to what this Thanks cyber Can you help me find where to find where items are marked as "not discovered any more" I was able to find and adjust the keep lost resources period in Templates -> Linux by Zabbix agent -> Discovery (column) -> Network interface discovery. Help us make it better. o campo só aceita dias se setar para 0 ele remove automaticamente __ ZABBIX FEATURE REQUESTS; ZBXNEXT-7679; Remove/disable trigger because of item not discovered anymore You can try this: Configuration -> Template (or Host) -> Discovery -> Name When in Discovery Rule set Keep lost resources period (in days) to 0 Don't forget to save :-) Let me know if it worked. Hosts Interface IP/DNS; Interface port; Passive proxy Interface port; Items and item prototypes Default value 7d (current corresponding field " Keep lost resources period ") b. This is because the return values are processed without being stored in a database. I have created the following regex on my environment: ZABBIX FEATURE REQUESTS; ZBXNEXT-7679; Remove/disable trigger because of item not discovered anymore ZABBIX FEATURE REQUESTS; ZBXNEXT-8313 "Keep lost resources period" option for network discovery To configure a new low-level discovery rule, click on the Create discovery rule button at the top right corner. i have 2 custom discovery rules whose items will most of the time show not discovered as these items are only present for short time periods. However, for "Keep lost resources period" in the discovery rule settings It may not have been deleted by the setting. Note that items no longer discovered (e. Like other discovered entities applications follow the lifetime defined in discovery rule ('keep lost resources period' setting) - they are removed after not being discovered for the specified number of days. It's not "now" but it's Hi, if I understand correctly your problem is that you have modified the LLD filter but Zabbix still keeps monitoring the excluded disks. Junior Member. I usually delete these services manually after I add a service to the global Regex to clean them up quickly. Key: Linked Applications. I figure out that too, because of the vmware tools. Only graph can be manually deleted - i think tis is bug. The Keep lost resources period is the value, which indicates how long an item should retain the resources when they are no longer being discovered. Nothing happen. Tags: None. If an entity is discovered by LLD, and then is either: removed; lost; or excluded by a filter, it is still kept in Zabbix for the duration of time defined by the Keep Lost Resources parameter (default is 30 days). how can i exclude the backup disks from zabbix discovery so it will stop reporting it greetings Locdoc Tags: hdd, zabbix. Look's like it worked as expected and there is no indication of a bug so I am going to close this ticket Hi, Please check "Keep lost resources period" parameter. i have 2 custom discovery rules whose items will most of the time show not discovered as these items are only The only alternative, (depending on the number discovered items / hosts) is to delete the unwanted items manually after increasing the "Keep lost resources period" value. Also, depending on settings, not discovered items may be kept for predefined time, setting "keep lost resources" to 0 shoudl delete them right when they are not discovered any more. Current issues are accumulated since Zabbix version 1. Back on the discovery rule page, note the "Keep lost resources period". if you start filtering and eliminate some) are removed after the "Keep lost resources period (in days)" on the discovery rule. Buttons below the list offer some mass-editing options: Enable - change the low-level discovery rule status to Enabled; Disable - change the low-level discovery rule status to Disabled; Delete - delete the low-level discovery rules To configure a new low-level discovery rule, click on the Create discovery rule button at the top right corner. Buttons below the list offer some mass-editing options: Enable - change the low-level discovery rule status to Enabled; Disable - change the low-level discovery rule status to Disabled; Check now - perform discovery based on the discovery rules They were created by a Discovery rule on a host, which i used the Clear and unlink but forgot to place the 0 on keep lost resources. Buttons below the list offer some mass-editing options: Enable - change the low-level discovery rule status to Enabled; Disable - change the low-level discovery rule status to Disabled; Check now - perform discovery based on the discovery rules ZABBIX FEATURE REQUESTS; ZBXNEXT-7679; Remove/disable trigger because of item not discovered anymore Good afternoon I am a relative newcomer to Zabbix, having just taken up a role at a company that uses Zabbix as its monitoring software. discovery Update interval: 7200 Keep lost resource period: 0 Filter macro: {#IFNAME} Regexp: @Network-discovery. For instance, Zabbix can automatically start monitoring file systems or network interfaces on your machine, without the need to create items for each file system or network interface See more I was able to do this by setting the "Keep lost resources period" field in the LLD rule to 0. Scheduling is supported since Zabbix 3. But there is still a problem why the items “vmware. Here I'm trying to monitor the pod status. Already discovered resources which are no longer found will be deleted after Keep lost resources period days (can be found in discovery rule settings) Also you can go to the host and manually delete unneeded items if you don't want to wait x days to get rid of them. ZABBIX FEATURE REQUESTS; ZBXNEXT-7679; Remove/disable trigger because of item not discovered anymore To configure a new low-level discovery rule, click on the Create discovery rule button at the top right corner. Zabbix approach to monitoring. There is no limit for low-level discovery rule JSON data if it is received directly by Zabbix server. This is a translation of the original English documentation page. Loading Dashboards In this case the items, triggers and graphs will be deleted after the days defined in the Keep lost resources period field pass. Member. Contents. ZABBIX FEATURE REQUESTS; ZBXNEXT-1974; LLD Graph/Trigger prototypes saving. When a resource is not discovered anymore, if it was related to a trigger in PROBLEM state, the trigger never comes back to OK state. If it is set >0, items will be deleted only when LLD rule runs again when "Keep lost resources" period is over. Closed. Buttons below the list offer some mass-editing options: Enable - change the low-level discovery rule status to Enabled; Disable - change the low-level discovery rule status to Disabled; Delete - delete the low-level discovery rules Steps to reproduce: Create new LLD rule; Type name, key and set 1 in "Keep lost resources period" Try save LLD; Result: Get message "Incorrect value for field "lifetime": must be between "3600" and "788400000". It should remove all such items right away, when they are not discovered any more (next discovery run) And after they are gone, you can set it back to some more reasonable They all have Zabbix Agent installed, and they auto-register to the Zabbix Server. If you want to delete items or triggers that you no longer need to monitor quickly, try temporarily setting a shorter time. To do a rediscover now, just set the discovery period to a short value, like 1m. Buttons below the list offer some mass-editing options: Enable - change the low-level discovery rule status to Enabled; Disable - change the low-level discovery rule status to Disabled; Delete - delete the low-level discovery rules Specifically to the Keep lost resources period (in days) parameter. ZABBIX FEATURE REQUESTS; ZBXNEXT-7679; Remove/disable trigger because of item not discovered anymore ZABBIX FEATURE REQUESTS; ZBXNEXT-7679; Remove/disable trigger because of item not discovered anymore Linked Applications. 6>1. Is there a way to delete the item "Windows services discovery: State of service "TrustedInstaller" (Windows ZABBIX FEATURE REQUESTS; ZBXNEXT-8313 "Keep lost resources period" option for network discovery. vfs. " However sometimes an item discovered by. After the external HDD was disconnected, LLD didn't discover it anymore and had to delete it (Items and Triggers and Graphs) (after the period of To configure a new low-level discovery rule, click on the Create discovery rule button at the top right corner. Leaving "keep lost resource period" as 0 is not recommended in production environment. Low-level discovery provides a way to automatically create items, triggers, and graphs for different entities on a computer. Zabbix uses received value for clock to calculate "delete date" for not discovered items (LLD). Mass editing options. What does it take to become a g Setzt vorher Keep lost resources period (in days) auf 0 - so löscht er die alten Dienste sofort - und kann die neuen auch wieder sofort anlegen; Eventuell setzt Ihr auch den Intervall runter - aber nicht vergessen den hinterher wieder hoch Keep lost resources period: then you will need only the 4th line without the 5th. ZABBIX FEATURE REQUESTS; ZBXNEXT-8313 "Keep lost resources period" option for network discovery If I look at the "latest data" for the item, its still getting updated every 60s, so I do not think it helps adjust the lost resources period ? Keep lost resources period was 30days, i've tried to lower if to see if it helps. Now I also have noticed something, the application prototypes are being In conclusion, on traditional switches/routers, it is fair to set "Keep lost resources period" to be 7 (default). It is wise when changing the filters to set this to something larger than 0, then review the items for a device to see which are not discovered and being deleted (they appear What it means, that yes, your change in template works, but already present item will be monitored what you can do, is to set (temporarily) "Keep lost resources" in discovery config to 0. " But "Keep lost resources period" can also accept 0 value to delete entities immediately Expected: Something like "Incorrect value for field "lifetime": must be For those who don't know where to find it like dlogan, example - Configuration > Templates > Linux filesystems by Zabbix agent > Discovery rules > Mounted filesystem discovery > Keep lost resources period, default value is "30d", after setting it to "0d" all our former zfs snapshots were cleared after next discovery, like was mentioned by mattrk. But maybe old ones are marked now as "not discovered any more" and you can just delete old ones. If an application is not discovered anymore all discovered items are automatically removed from it, even if the application itself is not yet removed because of the 'lost resources Zabbix server crashing when linking w Closed causes ZBX-18014: Memory leak when message is not in ac Closed causes ZBX-14875: Escalations for autoregistration and Closed causes ZBX-13368: Outdated units of History storage per Closed causes ZBX-13595: Adding Zabbix API validation of Media Closed causes ZBX-14771: Memory leak if scheduling Name: Windows Network Discovery Type: Zabbix agent (active) Key: net. one. I can not wait 30 days as it becomes unmanageable. Must support User macr os c. The trigger stays in PROBLEM even after the "Keep lost resources period". Details. Most of the configuration options are read-only, except for enabling Already discovered services will stay Keep lost resources period specified in discovery rule, even if they are no longer discovered. (All clients ZAB, SNMP,IPMI all in red collor). 13-08-2020, 17:59. I think it's not possible with internal vfs. 3) are deleted immediately. You can set to Keep lost resources period. Introduction3. You should see orange icon behind items that aren't discovered any more. I have modified the Keep Lost resources value from 30 to 3. LLD rule update interval > "After" or LLD rule " Custom intervals " is used: 1. the items created are for watching the size of files (based on similar names) and IP connections when over a specific count. Steps to reproduce: Create new LLD rule; Type name, key and set 1 in "Keep lost resources period" Try save LLD; Result: Get message "Incorrect value for field "lifetime": must be between "3600" and "788400000". tikkami. Note that if you unlink and relink the template, any trigger actions you have with any items will be removed. add ability to set no deletion for discovery rule lost resources. Another thing that helps is that you can disable the item IN the discovery rule. dynux If an application is not discovered anymore, the application itself may not be removed because of the 'lost resources period' setting, however: items that are still discovered are automatically removed from it; items that are no longer discovered are not removed from it (note that they would be removed before Zabbix 4. EDIT: Disregard this, I'm thinking of the setting in discovery rules"Keep lost resources period" I vaguely recall seeing something regarding how long to keep orphaned data for or something like that and it was 30d from memory, but I can't find that setting now. Discovered hosts will also be automatically deleted, based on the Keep lost resources period (in days) value of the discovery rule. 0>2. discovery. Basically this database got lot's of foreign key errors and I have plan to re-create Zabbix on clean system. NOTE. Joined: Aug 2020; Posts: 1 #2. So even if you shorten that "Keep lost resources" period, you also need to wait until next discovery. Setting "Keep lost resources period" to be 0 and redo discovery didnt help me in my case. The thing is i want to create the same host but zabbix says the items already exists so it cant create them again, I cannot find them anywhere not even in the DB as the original host is long gone. If this is your first visit, be sure to check out the FAQ by clicking the link above. Is there a way it keeps lost resources that amount of time AFTER it has done discovery and not finding it any more. But under Windows Services discovery rule, there's a setting for "Keep lost resources period". ; Execute now - perform discovery based on the discovery rules "Keep lost resources period (in days)=0" makes no difference because all autodiscovered items does not have association to Template. My pod `test-postgres-k8sdev-cluster-pooler-repl-6f797d558-n86gs` in `crashloopback`, I fixed it and then it started as different Not sure if it's a bug or the documentation doesn't point it out clearly: "Items (similarly, triggers and graphs) created by a low-level discovery rule [] will be deleted automatically if a discovered entity [] stops being discovered [] they will be deleted after the days defined in the Keep lost resources period field pass. Keep lost resources period is an arbitrary value here – once again, depending on your policies regarding LLD entities. In case if your "important" service somehow gets to the state "unsupported" then the service by itself will be removed prety much Hi guys. LLD rule for SSL monitoring. . Go to Configuration > Templates > Create Template. ArtemK. now its been set to This does not seem to have had any affect and they still get rediscovered. Create a Discovery Rule: Name: Domain Expiry Discovery. If something is not there any more, it will be marked as "not discovered any more" and will be removed later (after the "keep lost resources" period). Installing "Keep lost resources period=0" is not an option. Name: Domain Monitoring Template. Keep lost resources period is set to ‘0’, which is a regular way for low-level discovery. "Disable lost "Keep lost resources period" affects only item prototypes, but graph and trigger prototypes disappear as soon as item becomes "not discovered". ; Check now - perform discovery based on the discovery rules I am trying to automatically delete inactive hosts in zabbix 6. 17-12-2014, 10:21. This value can vary from one hour to 25 years, or it can be set to Zabbix uses received value for clock to calculate "delete date" for not discovered items (LLD). Resource vs service3. Example, incorrect clock may cause the following: "The item is not discovered anymore and will be deleted in 19y Greetings Zabbix user! I am trying to turn off alerting for the following services, Problem name: Service "wuauserv" (Windows Update) is not running (startup type automatic) Problem name: Service "WinHttpAutoProxySvc" (WinHTTP Web Proxy Auto-Discovery Service) is not running (startup 5 Descoberta (LLD) Visão geral. Keep lost resources period (in days) To configure a new low-level discovery rule, click on the Create discovery rule button at the top right corner. After reading some Scheduling is supported since Zabbix 3. It would be nice to keep them too. You may have to REGISTER before you can post. size” are becoming unsupported. XML Word Printable. Their documentation is fairly helpful. When not discovered (client off) during the next discovery , the item gets status "Not supported" and respecitve graph is Found a workaround for you You can create a new regular expression for the LLD which includes the LLD key strings you want items removed for and apply it to the LLD with the "Keep Lost Resources Period value set to 0 to remove immediately. (There is a possibility for misunderstanding here because I don't do SMART monitoring myself. I reloaded the zabbix config cache but inactive hosts (hosts that lost zabbix agent) still wait 30 days before being deleted. I too am having this same problem. Perhaps, they've been recreated under different names. 2019_2_draft. Senior Member. Look's like it worked as expected and there is no indication of a bug so I am going to close this ticket If the above network interface is not discovered anymore while the above trigger was in the problem state, then the Trigger state will change to "Unknown" but it will keep showing in the dashboard until the "Keep lost resources period" in the Discovery rule passes which will delete the item on which the trigger is based. " For instant cleanup you can temporary set discovery to 1m and 'Keep lost resources period' resources to 0: Once you accomplish clean system, please change back these settings to Update interval: 1h Keep lost resources I guess, it is not reflected right away, as there are discoveries, which need to run to "not discover" some services any more. protocol6v. It may be improved by temporarily setting a short "Keep lost resources period" period so that unnecessary things are deleted early. Discovered hosts can be manually deleted. 11#940011-sha1:6ded4e0d7ce2259c0cf27cdf1902fca142716752. 4. This cleared the old stuff out the next time the discovery ran. I tried this, with restarting the Zabbix server afterwards, and still it does not work. Perhaps I can create some sort of trigger, like when Zabbix Agent is not communicating for more than 5 minutes, invoke an API call to remove it? If that's doable, any change the Keep lost resources period to 0 for few minutes and bring back to default But nothing service trigger hit again I can't figure it out what I'm doing wrong Thanks everyone in advance Tags: None. If you “Mounted filesystem discovery” Keep lost resources period = 0 (zero). In my Zabbix environment, we are often making changes resulting in items no longer being discovered. Open. The items will be deleted in the future, after the "Keep lost resources period" have expired, but I was wondering if there was a way to list all those items? i got a problem with zabbix that it will report warnings on the backup disks. In this case, we will discard the lost resource immediately – Keep Lost resources (0). I then put it back to 30 add ability to set no deletion for discovery rule lost resources. 0 after 3 days. Buttons below the list offer some mass-editing options: Enable - change the low-level discovery rule status to Enabled. Try Jira - bug tracking software for your team. Buttons below the list offer some mass-editing options: Enable - change the low-level discovery rule status to Enabled; Disable - change the low-level discovery rule status to Disabled; Delete - delete the low-level discovery rules 1) is not a solution. if. Maybe setting a "keep lost resources" period for shorter time might avoid such thing in the future To configure a new low-level discovery rule, click on the Create discovery rule button at the top right corner. The issue here is that when discovered - item is created, supported and respective graph is available. Fix Version/s: None Affects Version/s I also should mention that Keep Lost Resources period is set to 1 hour, since I'd have 20 or 15 items no longer discovered in the 24 hour period. You could probably write your own Not sure if it's a bug or the documentation doesn't point it out clearly: "Items (similarly, triggers and graphs) created by a low-level discovery rule [] will be deleted automatically if a discovered entity [] stops being discovered [] they will be deleted after the days defined in the Keep lost resources period field pass. And this is why the values are deleted sometimes daily. Cleaning up old is quickest if you set the "keep lost resources period" to zero. Buttons below the list offer some mass-editing options: Enable - change the low-level discovery rule status to Enabled; Disable - change the low-level discovery rule status to Disabled; Delete - delete the low-level discovery rules I guess this is somekind of discovery and index of discovered items is changed, so what previously was #4, is now #5 New items/triggers are created. I wanted to exclude the edgeupdate service from the list of services from 5 Descoberta (LLD) Visão geral. Solution could be to implement additional functionality to disable or remove trigger right after ZABBIX FEATURE REQUESTS; ZBXNEXT-8313 "Keep lost resources period" option for network discovery Within the Zabbix webinterface, you can create the discovery rule. Quick update the RegExp was working correct, I found the issue under Template OS Windows > Windows Service Discovery > * Keep lost resources period: 365d as soon I reset the value to 0 days all was working as it should. " But "Keep lost resources period" can also accept 0 value to delete entities immediately Expected: Something like "Incorrect value for field "lifetime": must be The chances are your device does not have these interfaces anymore. 0. fs. If an application is not discovered anymore, the application itself may not be removed because of the 'lost resources period' setting, however: items that are still discovered are automatically removed from it; items that are no longer discovered are not removed from it (note that they would be removed before Zabbix 4. ; Check now - perform discovery based on the discovery rules Scheduling is supported since Zabbix 3. 8>2. Items created by a LLD rule are deleted automatically if a discovered file system or interface, etc. Details ZABBIX FEATURE REQUESTS; ZBXNEXT-8313 "Keep lost resources period" option for network discovery To configure a new low-level discovery rule, click on the Create discovery rule button at the top right corner. Show yellow information icon when i. Create a new template and setup a Discovery rule: Type: Zabbix Agent; Key: custom. Sometimes in linux/windows VMs vmware tools stop working or Use case: LLD rule executes, it respects "Keep lost resources period" grace period and, if we have not found the JSON node anymore, it will mark item for deletion. Joined: May 2013; Posts: 232 #2. Hi, I'm using my prometheus integration with zabbix. Buttons below the list offer some mass-editing options: Enable - change the low-level discovery rule status to Enabled; Disable - change the low-level discovery rule status to Disabled; Check now - perform discovery based on the discovery rules You do not need to query data for each item separately. Loading Dashboards Generated at Sat Feb 24 14:28:34 EET 2024 using Jira 9. O link para as descobertas podem sem encontrados em: - Type: `Zabbix agent` - Key: `lld. Move your mouse pointer over it and a message will be displayed indicating how many days are left until the item is deleted. Show "Disable lost resources" when " Never " or "After" is selected ii. Why? Because of Windows 🙂 For testing you can keep both and then later remove the unnecessary one as well as the number suffix. ; Check now - perform discovery based on the discovery rules So it should have run between now and when I posted this issue but again the IaasVmProvider service and problem is reported in Zabbix. ; Execute now - perform discovery based on the discovery rules See Time period specification page for description of the Period format. Now the auto-added resources (items, triggers) can not be deleted. On software defined networking hosts where interfaces change rapidly, it'd be better to set "Keep lost resources period" to be 0. Type: Zabbix Agent. Time suffixes are supported, e. It is very common to be set to 14 ZABBIX FEATURE REQUESTS; ZBXNEXT-8771; usermacro for Keep lost resources period in LLD rules. Then you can set period back to 30 days. This determines (in days) how long the previously discovered item will stay around. In this case, we will discard the lost resource immediately – Keep Lost I have modified my discovery template to exclude monitoring certain services but Zabbix has already discovered over 200 hosts and are all reporting the "TrustedInstaller" service is not running. Editing the template and changing the discovery rule "Keep lost resources period" allowed all the trigger actions to stay intact. All item entities that are no longer discovered, will be cleaned up automatically after keep lost resources days period. If that's not fast enough (and you do not mind losing history for that template) just "unlink and clear" and then re-apply the template to remove all old items. Olá meu caro, Só ajustar o campo keep lost resources period no LLD. Note: If set to '0', the item will not be polled during the flexible interval duration and will resume polling according to the Update interval once the flexible interval period is over. g. null XML Word Printable. You ZABBIX BUGS AND ISSUES; ZBX-12002; Applications created from LLD prototype empty if LLD items not discovered anymore Hi, Please check "Keep lost resources period" parameter. Next, we create a discovery rule. Discovery rule. You can set this period temporarily to 0 to clean up all lost items immediately. Best regards, Kaspars To configure a new low-level discovery rule, click on the Create discovery rule button in the top right-hand corner. You can delete such stale items manually and also decrease "Keep lost resources period" in the discovery rule so such items get deleted sooner. key[HOST-KVM]` - Update interval: `1h` - Keep lost resource period: `7d` - Description: `This LLD rule will gather the LLD Macros for OpenNebula HOST-KVM IDs defined in json format, from the orchestrator [Made by Franco]` Creating the item prototype for *HOST-KVM* Step 3: Create a Discovery Rule in Zabbix. Now to get the host prototype changes to take effect on existing hosts (since it doesn't appear that changes made to a prototype will push down to hosts that were already previously discovered and created from that prototype), I went to the definition of the Discover VMware Hypervisor discovery rule and unchecked the "discovery" box there (make sure your I try set StartPollersUnreachable=250 and restart server. After this I found another post which said you need to set "Keep lost resources period (in days)" to zero and have it clear everything before setting it back to a couple of days. As there is no way to manually reset or clear a trigger created by a LLD rule, we have add ability to set no deletion for discovery rule lost resources. Added functionality similar to LLD's "Keep lost resources period", so if the host or service is no longer discovered, it is removed within a period of time. ways to speed up things - delete not discovered items manually (they are marked with yellow !sign), they will not reappear - shorten for a while this period in template to I have also set the Keep lost resources period to 0 and deleted the Items and Triggers created before but the services keep showing in the Problems section. I've been beating my head against this To configure a new low-level discovery rule, click on the Create discovery rule button at the top right corner. Maybe some script which does To configure a new low-level discovery rule, click on the Create discovery rule button at the top right corner. Normally there items would be managed by the 'Keep lost resources period' and get cleaned out, but there are this option is not on the data item or the prototype item, only on the lld item that isnt really linked to the prototype item since the If an application is not discovered anymore, the application itself may not be removed because of the 'lost resources period' setting, however: items that are still discovered are automatically removed from it; items that are no longer discovered are not removed from it (note that they would be removed before Zabbix 4. 04-03-2022, 23:22. Tool-tip text: The value should be greater than LLD rule update interval 4. Disclaimer3. I really do not know, how long period that is set in default templates. The current formula is "Received clock + Keep lost resources period (in days)". To configure a new low-level discovery rule, click on the Create discovery rule button in the top right-hand corner. Note that triggers (until Zabbix 2. If an application is not discovered anymore all discovered items are automatically removed from it, even if the application itself is not yet removed because of the 'lost resources ZABBIX FEATURE REQUESTS; ZBXNEXT-7679; Remove/disable trigger because of item not discovered anymore ZABBIX FEATURE REQUESTS; ZBXNEXT-7679; Remove/disable trigger because of item not discovered anymore How long is the "Keep lost resources period" time in the discovery rule? The default setting is 30 days, so it will not be deleted until 30 days have passed. When I DISABLE unreachable clients in Configuration / Hosts then "Zabbix busy unreachable poller processes" drop on 27%. O link para as descobertas podem sem encontrados em: There is an annoying behavior of Zabbix with LLD. eyhpty nzyttr lngtypg ulgsq bvmx ygni jldw eqffj tix jjjsmlp