Close Problem manually

[amirmb]

Hi there,

I have installed and configured Zabbix 3.2, added couple of hots and assign default windows OS template.
Now I am trying to close some problems (i.e. Service "RemoteRegistry" (Remote Registry) is not running (startup type automatic)) manually. Here are the steps I took:

I went to Configuration=> Templates => Template OS Windows => Discovery Rules => Windows service discovery => Trigger prototypes => Service "{#SERVICE.NAME}" ({#SERVICE.DISPLAYNAME}) is not running (startup type {#SERVICE.STARTUPNAME}).

From there I enabled "Allow manual Close" and hit Update.

After this I went to Monitoring => Ack the problem => filled the message section, However the "Close problem" is still grayed out.

Any one has the same experience? or I am missing some part of the process?

Thank you all in advance.

[julianmd]

Bump +1 - Missing Manual Close

Hi,

I don't know if this is a bug, or something I am missing, but I do not have the Close option enabled

Please see attachment

Any thoughts?

[julianmd]

Bump +1

Anyone? Any idea why I cannot close issues manually?
Is there a workaround to remove them from the db/backend?
Thanks

[Atsushi]

Hi julianmd,
Your attached screen is not Zabbix 3.2.
Manual close is a new feature from 3.2.

https://www.zabbix.com/documentation/3.2/manual/introduction/whatsnew320#close_problems_manually

https://www.zabbix.com/documentation/3.2/manual/config/triggers/trigger

[glebs.ivanovskis]

Also, you need to "Enable event acknowledgement" in Administration->General->GUI

[brinkdogg]

Help

Ok so I can't edit the trigger to enable "Allow manual close". Is there a global option to enable it? Not sure where to event start

[gessel]

Also can't succesfully enable manually close of Trigger Prototypes

I set enabled "Allow manual close" on the Trigger prototype definition


The check shows and is persistent after update. However, it does not show as checked if one selects configuration->hosts->triggers and can't be selected there.

The box is visible (not grayed) but not selectable in the acknowledge problem screen:

[ovas]

I set enabled "Allow manual close" on the Trigger prototype definition

The check shows and is persistent after update. However, it does not show as checked if one selects configuration->hosts->triggers and can't be selected there.

The box is visible (not grayed) but not selectable in the acknowledge problem screen:

Hello!

It is a discovery trigger and, by default, manual closure is not available in it. Therefore, you are currently dealing with host triggers that were created at the time, when manual closure was not available.
If trigger prototype is adjusted and saved, old discovered triggers deleted from host, then, upon a new discovery, new trigger will be created from adjusted discovery with manual closure attribute working fine.

[gessel]

Thanks! Solved

You're right, it works exactly that way.

[onallion]

Joining in here...

Is it needed to delete the old triggers, or will they get updated once discovery runs again? If it requires manual deletion I'm in for a long ride

[gessel]

manual deletion of triggers for update

Good question - I don't know, I didn't wait.

[SBrassard]

Triggers will update at next discovery

Joining in here...

Is it needed to delete the old triggers, or will they get updated once discovery runs again? If it requires manual deletion I'm in for a long ride

Late but for everybody's knowledge:

I updated Trigger Prototype to 'allow manual close = yes', then forced a discovery and existing triggers updated to 'allow manual close = yes'.

[AlexBG]

Late but for everybody's knowledge:

I updated Trigger Prototype to 'allow manual close = yes', then forced a discovery and existing triggers updated to 'allow manual close = yes'.

How did you force discovery to run again?

[Reikidude]

Triggers will update at next discovery



Late but for everybody's knowledge:

I updated Trigger Prototype to 'allow manual close = yes', then forced a discovery and existing triggers updated to 'allow manual close = yes'.

I also have this problem., How did you force discovery to run again?

[Atsushi]

If you want to execute the discovery process immediately with Zabbix 4.0 or later, check the discovery rule of the target host and click the check now button.