Skip to content

Commit

Permalink
Proofread Cloud section (#2704)
Browse files Browse the repository at this point in the history 
* getting started, installation, CIAM, graph views

* Update cloud/getting-started/monitor-windows-server-with-snmp.md

* Update cloud/getting-started/monitor-windows-server-with-snmp.md

* Update monitor-windows-server-with-snmp.md

* monitoring (cloud)

* proofread cloud alerts-notifications

* metrology

* resources

* corrected status/state

* security, service-mapping, users

* Update cloud/alerts-notifications/acknowledge.md

* Update cloud/alerts-notifications/downtimes.md

* Update cloud/alerts-notifications/manage-alerts.md

* Update cloud/alerts-notifications/other.md

* Update cloud/alerts-notifications/other.md

* Update cloud/monitoring/discovery/hosts-discovery.md

* Update cloud/monitoring/discovery/services-discovery.md

* Update cloud/resources/glossary.md

* Update cloud/resources/glossary.md

* Update cloud/security/security.md

---------

Co-authored-by: cg-tw <[email protected]>
  • Loading branch information
@KA-Foster @cg-tw
KA-Foster and cg-tw authored Oct 12, 2023
1 parent 538249a commit 58196cd
Show file tree
Hide file tree
Showing 60 changed files with 963 additions and 963 deletions.
58 changes: 29 additions & 29 deletions cloud/alerts-notifications/acknowledge.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -8,28 +8,28 @@ import TabItem from '@theme/TabItem';

### Principle

When a host or a service presents an incident and this incident is
confirmed, the notification process is triggered, it can generate a
notification sent to a contact. If the problem persists and depending on
When a host or a service has an incident and this incident is
confirmed, the notification process is triggered. This can generate a
notification sent to a contact. If the problem persists, and depending on
the configuration produced (resend a notification at regular time
intervals, escalation of notification, etc.), it is possible that other notifications are sent.

The acknowledgment of an alert can be used to stop the notification
process (sending of notifications) until the host or the service
recovers its nominal status.
resumes its nominal status.

Example of use:

A service is charged with checking the health of the hard disks in a
disc array. A hard disk goes down on a disk array, a notification is
sent. The monitoring operator acknowledges the service specifying that a
A service is in charge of checking the health of the hard disks in a
disk array. A hard disk on a disk array goes down, and a notification is
sent. The monitoring operator acknowledges the service, specifying that a
team is in the process of dealing with the problem. Notifications are no
longer sent. The service will return to its nominal state after a change
of disk.

> The acknowledgment of an alert signifies the taking into account of
> the problem by a user of the monitoring - and not the correction of
> the incident which can only be effective when the check returns to its
> The acknowledgment of an alert means that a monitoring user
> has taken the problem into account - not that the incident has been
> corrected; this can only take effect when the check returns to its
> nominal state.
### Practice
Expand All @@ -50,12 +50,12 @@ To acknowledge an alert, there are several solutions:

![image](../assets/alerts/resources-status/ack-popup.png)

- The **Comment** field is generally used to provide the reason of the
- The **Comment** field is generally used to provide the reason for the
acknowledgment. It is mandatory.

- If the **Notify** box is checked, a notification is sent to the
contacts linked to the object to warn that the incident on the
resource has been acknowledged (in the situation the contact
contacts linked to the object to warn them that the incident on the
resource has been acknowledged (if the contact
possesses the activity acknowledgment notification filter).

- If the **Persistent** box is checked, the acknowledgment will be
Expand All @@ -64,7 +64,7 @@ To acknowledge an alert, there are several solutions:
reactivated.

- If the **Sticky** box is checked, the acknowledgment will be
maintained in case of a change of Not-OK status (E.g.: DOWN to
maintained in case of a change of Not-OK status (e.g.: DOWN to
UNREACHABLE or WARNING to CRITICAL). Otherwise, the acknowledgment
disappears and the notification process is reactivated.

Expand All @@ -73,27 +73,27 @@ To acknowledge an alert, there are several solutions:

1. Go to **Monitoring > Status Details > Hosts** (or **Services**).
2. Select the object(s) that you want to acknowledge.
3. In the menu: **More actions** click on **Hosts: Acknowledge** or on
3. In the **More actions** menu, click **Hosts: Acknowledge** or
**Services: Acknowledge**.

The following window appears:

![image](../assets/alerts/acknowledged.png)

- If the **Sticky** box is checked, the acknowledgment will be
maintained in case of a change of Not-OK status (E.g.: DOWN to
maintained in case of a change of Not-OK status (e.g.: DOWN to
UNREACHABLE or WARNING to CRITICAL). Otherwise, the acknowledgment
disappears and the notification process is reactivated.
- If the **Notify** box is checked, a notification is sent to the
contacts linked to the object to warn that the incident on the
resource has been acknowledged (in the situation the contact
contacts linked to the object to warn them that the incident on the
resource has been acknowledged (if the contact
possesses the activity acknowledgment notification filter).
- If the **Persistent** box is checked, the acknowledgment will be
maintained in the case of a restart of the scheduler. Otherwise, the
acknowledgment disappears and the notification process is
reactivated.
- The **Comment** field is generally used to provide the reason of the
acknowledgment, it is mandatory
- The **Comment** field is generally used to provide the reason for the
acknowledgment. It is mandatory.
- If the **Acknowledge services attached to hosts** box is checked,
all the services linked to the host will be acknowledged (option
visible only if we acknowledge a host).
Expand All @@ -103,27 +103,27 @@ To acknowledge an alert, there are several solutions:
</TabItem>
<TabItem value="From the detailed sheet of an object" label="From the detailed sheet of an object">

From of the detail page of an object, click on the icon |enabled| associated
From of the detail page of an object, click the icon |enabled| associated
with the **Acknowledged** field in the **Options** frame.

The following window appears:

![image](../assets/alerts/acknowledged.png)

- If the **Sticky** box is checked, the acknowledgment will be
maintained in case of a change of Not-OK status (E.g.: DOWN to
maintained in case of a change of Not-OK status (e.g.: DOWN to
UNREACHABLE or WARNING to CRITICAL). Otherwise, the acknowledgment
disappears and the notification process is reactivated.
- If the **Notify** box is checked, a notification is sent to the
contacts linked to the object to warn that the incident on the
resource has been acknowledged (in the situation the contact
contacts linked to the object to warn them that the incident on the
resource has been acknowledged (if the contact
possesses the activity acknowledgment notification filter).
- If the **Persistent** box is checked, the acknowledgment will be
maintained in the case of a restart of the scheduler. Otherwise, the
acknowledgment disappears and the notification process is
reactivated.
- The **Comment** field is generally used to provide the reason of the
acknowledgment, it is mandatory
- The **Comment** field is generally used to provide the reason for the
acknowledgment. It is mandatory.
- If the **Acknowledge services attached to hosts** box is checked,
all the services linked to the host will be acknowledged (option
visible only if we acknowledge a host).
Expand All @@ -142,15 +142,15 @@ To delete the acknowledgment of an incident on an object:

1. Go to **Monitoring > Resources Status**.
2. Select the objects you want to disacknowledge.
3. On the **More actions** menu, click **Disacknowledge**.
3. In the **More actions** menu, click **Disacknowledge**.

</TabItem>
<TabItem value="From real time monitoring" label="From real time monitoring">

1. Go to **Monitoring > Status Details > Hosts** (or **Services**).
2. Select the objects you want to disacknowledge.
3. In the **More actions** menu, click on **Hosts: Disacknowledge** or
on **Services: Disacknowledge**
3. In the **More actions** menu, click **Hosts: Disacknowledge** or
**Services: Disacknowledge**

</TabItem>
</Tabs>
10 changes: 5 additions & 5 deletions cloud/alerts-notifications/concepts.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -38,15 +38,15 @@ In addition to their status, resources can be in several states:

- [Acknowledged](acknowledge.md): indicates that the incident on the service or on the host
has been taken into account by a user. Acknowledged resources have a yellow background.
- [In downtime](downtimes.md): indicates that notifications are temporarily stopped. A downtime can be [planned in advance](downtimes.md#recurrent-downtimes) to avoid receiving alerts during maintenance periods, or be set following an incident. Resources in downtime have a purple background.
- [In downtime](downtimes.md): indicates that notifications are temporarily stopped. Downtime can be [planned in advance](downtimes.md#recurrent-downtimes) to avoid receiving alerts during maintenance periods, or can be set following an incident. Resources in downtime have a purple background.

## Status types

The status of a resource can have one of these 2 types:
The status of a resource can be one of these two types:

- SOFT: Signifies that an incident has just been detected and that it
- SOFT: Means that an incident has just been detected and that it
has to be confirmed.
- HARD: Signifies that the status of the incident is confirmed. Once
- HARD: Means that the status of the incident is confirmed. Once
the status is confirmed, the notification process is engaged
(sending of an email, SMS, etc.).

Expand Down Expand Up @@ -84,5 +84,5 @@ Let us imagine the following scenario:
| t+22 | 1/3 | OK | HARD | Yes | Service experiences a HARD recovery. Event handlers execute and a recovery notification is sent out. |
| t+27 | 1/3 | OK | HARD | No | Service is still OK. |
| t+32 | 1/3 | UNKNOWN | SOFT | Yes | Service is detected as changing to a SOFT non-OK state. Event handlers execute. |
| t+33 | 2/3 | OK | SOFT | Yes | Service experiences a SOFT recovery. Event handlers execute, but notification are not sent, as this wasn't a "real" problem. State type is set HARD and check # is reset to 1 immediately after this happens. |
| t+33 | 2/3 | OK | SOFT | Yes | Service experiences a SOFT recovery. Event handlers are executed, but no notification is sent, as this wasn't a "real" problem. State type is set to HARD and check # is reset to 1 immediately after this happens. |
| t+34 | 1/3 | OK | HARD | No | Service stabilizes in an OK state. |
6 changes: 3 additions & 3 deletions cloud/alerts-notifications/custom-views.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ To edit a widget, click the wrench icon in the top right corner of the widget: !

### Rearranging widgets

To move a widget, click the title bar of the widget and drag it to the place you want.
To move a widget, click the title bar of the widget and drag it to the desired location.

## Sharing custom views

Expand Down Expand Up @@ -92,7 +92,7 @@ Once you have created several custom views, you can make all views be displayed

You can choose which view to display when you access the **Home > Custom Views** page.

1. Click on the view you want.
1. Click the desired view.
2. On the control bar, click **Set default**.

## List of widgets
Expand All @@ -102,7 +102,7 @@ You can choose which view to display when you access the **Home > Custom Views**
| Engine status | Display the statistics for a poller. (Select a poller in the settings.) |
| Global health | Displays a pie chart showing the status of hosts. |
| Graph monitoring | Displays the RRD graph for a service. You must select a service that uses performance data. You can define the timeperiod and the refresh time for the graph in the settings. |
| Grid-map | Display services as coloured squares. To configure this widget, select a hostgroup and fill in the "Name services" field, using commas between services (do not use special characters, e.g. slashes, in this widget). |
| Grid-map | Display services as colored squares. To configure this widget, select a hostgroup and fill in the "Name services" field, using commas between services (do not use special characters, e.g. slashes, in this widget). |
| Host monitoring | Displays the list of hosts as well as their status and related information. You can filter the list using the criteria you want. |
| Hostgroup monitoring | Displays host groups. It can show a detailed view of services. |
| HTTP loader | Displays a web page. |
Expand Down
Loading

0 comments on commit 58196cd

Please sign in to comment.