Folks,
Doing some tests with 3.2, but in reality this happens from the 3.0. I came across an uncomfortable situation. Already researched on the official forums and found nothing useful.
Windows has some services that are started automatically, but they stop when fulfill their role, and can be started again by a trigger (Windows itself) if necessary - https://drive.google.com/file/d/0B_O...ew?usp=sharing
The Zabbix LLD finds all the services marked to start automatically (nice!), but when this particular type of service stops, the trigger happens - https://drive.google.com/file/d/0B_O...ew?usp=sharing
But I don't want to see the trigger happening, because this is normal behavior for this type of service. I've tested the keys available and haven't found a way to filter these services, any idea to avoid this kind of problem?
Doing some tests with 3.2, but in reality this happens from the 3.0. I came across an uncomfortable situation. Already researched on the official forums and found nothing useful.
Windows has some services that are started automatically, but they stop when fulfill their role, and can be started again by a trigger (Windows itself) if necessary - https://drive.google.com/file/d/0B_O...ew?usp=sharing
The Zabbix LLD finds all the services marked to start automatically (nice!), but when this particular type of service stops, the trigger happens - https://drive.google.com/file/d/0B_O...ew?usp=sharing
But I don't want to see the trigger happening, because this is normal behavior for this type of service. I've tested the keys available and haven't found a way to filter these services, any idea to avoid this kind of problem?

Comment