Could you please provide more information on how exactly to reproduce the problem?

2 trigger a confirmation message test1
again, those same triggers confirmation message test2
test2 message is not saved
confirm only 1 trigger message test2 - - the message is saved

Ah, thank you for the detailed description, now I understand.

The thing is that the acknowledge controls are currently inconsistent. When you use bulk acknowledge for triggers, it acknowledges all unacknowledged problem events for the selected triggers. Since the second time you bulk acknowledge a trigger, all of its events are acknowledged, it doesn't do anything.

As for the "Acknowledge" link. If a trigger has unacknowledged problem events, it will act the same way as the bulk acknowledged button, that is, acknowledge all unacknowledged events. But if it doesn't have any unacknowledged problem events, it will acknowledge the last event of the trigger.

I guess we'll need to rethink this feature in the next release, this is extremely confusing. And document this in the current releases.

Is there any workaround for this? This is really needed by our project.

ZBX-7589 could be also taken into account to develop them together.

Related issue: ZBX-2622

Available in the development branch svn://svn.zabbix.com/branches/dev/ZBX-8820

(1) String changes?

Strings added:

• %1$s event
• %1$s events
• Cannot acknowledge events
• Events acknowledged
• Incorrect value for field "%1$s": %2$s.
• Only selected event
• Only selected events
• Selected and all unacknowledged PROBLEM events
• Selected and all unacknowledged events
• cannot be empty

Strings deleted:

• ----[BULK ACKNOWLEDGE]----
• Acknowledge added
• Acknowledge alarm by
• Acknowledge and return
• Add comment by
• List
• No events to acknowledge
• Update and return

oleg.egorov CLOSED

API validation issue added under ZBX-3783 (20)

Also

{
    "eventids": [
        219883,
        219856
    ],
    "message": 0,
    "acknowledge_type": "test"
}

Return success message, and action it the same as acknowledge_type = null

(2) Minor coding style improvement in r55204
Please review

sasha Thanks! CLOSED

(3) Performance issue
I have an installation with 109499 unacknowledged events, but real users sometimes have 1 000 000+ unacknowledged events (discussed with dotneft).
I try to acknowledge problem trigger with 109499 events and I get the following error:

Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 41 bytes) in C:\xampp\htdocs\ZBX-8820\frontends\php\include\classes\debug\CProfiler.php on line 211

sasha Works fine for 500K events and memory_limit = 1GB. Please try again without Debug mode.

sasha RESOLVED in r55212.

3:30 minutes for 1M acknowledges and memory_limit = 128M.

oleg.egorov CLOSED

TESTED

Available in:

• pre-3.0.0alpha2 (trunk) r55249.

(4) Documentation

martins-v Updated sections:

• https://www.zabbix.com/documentation/3.0/manual/introduction/whatsnew300#bulk_acknowledgement_made_more_flexible
• https://www.zabbix.com/documentation/3.0/manual/acknowledges#acknowledgment_screen

Please review. RESOLVED.

sasha

• Bulk acknowledge now allowed from all these pages: Dashboard->Last 20 issues, Dashboard->System status, Monitoring->Overview (triggers), Monitoring->Status of triggers, Monitoring->Events, Monitoring->Event details, Screens->Host group issues, Screens->Host issues, Screens->System status, Screens->Triggers overview. It must be mentioned.

• "brackets" are not used in 3.0.0. Please remove this word.

  A 'Yes' may also have a number with it in brackets, indicating the number of comments for the problem so far.

REOPENED

martins-v Updated:

• https://www.zabbix.com/documentation/3.0/manual/acknowledges

RESOLVED.

sasha Thanks! CLOSED

<richlv> let's mention the removal of the hardcoded bulk acknowledge message in the upgrade notes

martins-v RESOLVED: https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300#frontend_changes

<richlv> thank you, looks good

CLOSED

(5) An empty acknowledge can be created now. It should be fixed.

sasha TESTED Take a look at my changes in r55751.

vitalijs.cemeris CLOSED

FIXED IN 3.0.0alpha3(trunk) r55762
CLOSED

(6) The following comment has a couple of typos:

Trims all elements values that have currect selector and are inside Jquery object first element.

The word "currect" is somewhere between "current" and "correct", and the proper capitalization for "Jquery" is "jQuery".

sasha RESOLVED in r55821.

asaveljevs According to martins-v, "Trims selected element values." is more correct than "Trims selected elements values."

sasha Thanks for pointing me to the right side. RESOLVED in r56001.

CLOSED

(7) the changelog entry currently talks about "functionality to trim multiple JS elements" - was there no user-visible angle to this change, for example, didn't it disallow adding empty acknowledgement messages ? if it did, that would be nice to use in the changelog entry as per the development guidelines :

Changelog entries should try to describe the fix from user perspective

sasha RESOLVED in r56002.

<richlv> for the record, changelog message was changed to "fixed trimming of new acknowledge messages" - thanks
CLOSED

The message handling caused ZBX-10140