Windows service discovery - changing name of a service

[APCal]

I have a number of services on some servers I have zabbix monitoring which have frequent name changes. The names are normally service.1.20260227183529, this changes when they get updated. Zabbix discovery handles this so they're always monitored, but there's always an alert generated at the cutover.

Is there a way to easily change the item prototype or discovery to just detect these services as service.1? I've tried looking this up and can't find anything other than a suggestion to make my own specific service monitoring using a script to do discovery. It seems like there should be a place to put a regex filter to change the name, I can't figure out where it'd work though.

[Ayana1]

Hi APCal,

This is a common issue with dynamic Windows service names in Zabbix. One approach you can try is modifying the LLD (Low-Level Discovery) rule filter using a regex so it matches only the stable part of the service name (for example, ^service\.1). This way, Zabbix will treat all versions of the service as the same logical item and prevent alert noise during updates.

If that doesn’t fully solve it, using a custom discovery script or PowerShell-based service filtering can give you more control over how services are detected and named. There are some helpful examples and resources you can visit for ideas on structuring custom monitoring workflows and automation logic.

Hope this helps reduce unnecessary alerts and simplifies your monitoring setup!