Source of acknowledgment.xliff - documentation

|*Suppress*|Mark the checkbox to suppress the problem:&lt;br&gt;**Indefinitely** - suppress indefinitely&lt;br&gt;**Until** - suppress until a given time. Both [absolute and relative](/manual/web_interface/time_period_selector) time formats are supported, for example:&lt;br&gt;`now+1d` - for one day from now (default)&lt;br&gt;`now/w` - until the end of the current week&lt;br&gt;`2022-05-28 12:00:00` - until absolute date/time&lt;br&gt;Note that a simple period (e. g., `1d`, `1w`) is not supported.&lt;br&gt;Availability of this option depends on the "Suppress problems" user role settings.&lt;br&gt;See also: [Problem suppression](/manual/acknowledgment/suppression)|

<?xml version='1.0' encoding='UTF-8'?>

<xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" version="1.2">

  <file source-language="en" target-language="nb-NO" datatype="plaintext" original="manual/acknowledgment.md">

    <body>

      <trans-unit id="61d493ca" xml:space="preserve">

        <source># 13 Problem acknowledgment</source>

      </trans-unit>

      <trans-unit id="79474bd8" xml:space="preserve">

        <source>#### Overview

Problem events in Zabbix can be acknowledged by users.

If a user gets notified about a problem event, they can go to Zabbix

frontend, open the problem update popup window of that problem using one

of the ways listed below and acknowledge the problem. When

acknowledging, they can enter their comment for it, saying that they are

working on it or whatever else they may feel like saying about it.

This way, if another system user spots the same problem, they

immediately see if it has been acknowledged and the comments so far.

This way the workflow of resolving problems with more than one system

user can take place in a coordinated way.

Acknowledgment status is also used when defining [action

operations](/manual/config/notifications/action/operation). You can

define, for example, that a notification is sent to a higher level

manager only if an event is not acknowledged for some time.

To acknowledge events and comment on them, a user must have at least

read permissions to the corresponding triggers. To change problem

severity or close problem, a user must have read-write permissions to

the corresponding triggers.

There are **several** ways to access the problem update popup window,

which allows acknowledging a problem.

-   You may select problems in *Monitoring* → *Problems* and then click

    on *Mass update* below the list

-   You can click on *Update* in the *Update* column of a problem in:

    -   *Dashboards* (*Problems* and *Problems by severity*

        widgets)

    -   *Monitoring → Problems*

    -   *Monitoring → Problems → Event details*

-   You can click on an unresolved problem cell in:

    -   *Dashboards* (*Trigger overview* widget)

The popup menu contains an *Update* option that will take you to

the problem update window.</source>

      </trans-unit>

      <trans-unit id="fa7fdaab" xml:space="preserve">

        <source>#### Updating problems

The problem update popup allows to:

-   comment on the problem

-   view comments and actions so far

-   change problem severity

-   suppress/unsuppress problem

-   acknowledge/unacknowledge problem

-   change symptom problem to cause problem

-   manually close problem