Timezone setting for alerts/monitors

blog-service/2023-11-07-monitors.md

@@ -0,0 +1,15 @@
+---
+title: Time Zone Settings for Monitors (Alerts)
+image: https://www.sumologic.com/img/logo.svg
+keywords:
+  - monitors
+  - alerts
+hide_table_of_contents: true
+authors:
+  - url: https://help.sumologic.com/release-notes-service/rss.xml
+    image_url: /img/release-notes/rss-orange.png
+---
+
+import useBaseUrl from '@docusaurus/useBaseUrl';
+
+We've rolled out the ability to designate a **Preferred Time Zone** when you're setting up alert monitor notifications. [Learn more](/docs/alerts/monitors/create-monitor#step-3-notifications-optional).

docs/alerts/monitors/alert-response.md

@@ -1,7 +1,6 @@
 ---
 id: alert-response
 title: Alert Response
-sidebar_label: Alert Response
 description: Quickly investigate and resolve issues you've been alerted about with the context provided by Sumo Logic.
 ---
 
@@ -19,7 +18,7 @@ import Iframe from 'react-iframe';
 
 :::sumo Micro Lesson
 
-Using Alert Response.
+Learn how to use Alert Response.
 
 <Iframe url="https://www.youtube.com/embed/3FHomBuFyV8?rel=0"
         width="854px"
@@ -80,11 +79,12 @@ To resolve an alert, click a row to select it, then click **Resolve**.
 
 ### Translating Thresholds
 
- Threshold translating allows you to open the Alert Response Page in the **Metrics Explorer** that helps you to easily view the threshold associated with an alert. This also helps you to understand how your monitor's thresholds are translating into metrics and compare the threshold values set in a monitor with the data displayed in the Metrics Explorer chart.
+Threshold translating allows you to open the Alert Response Page in the **Metrics Explorer** that helps you to easily view the threshold associated with an alert. This also helps you to understand how your monitor's thresholds are translating into metrics and compare the threshold values set in a monitor with the data displayed in the Metrics Explorer chart.
 
- For example, when you open an alert response page in Metrics Explorer, you can see critical thresholds defined with some number. You can then see that this threshold is also applied and enabled in the Metrics Explorer view, with exactly the same number defined.<br/> <img src={useBaseUrl('img/alerts/arp-metrics-explorer.png')} alt="arp-metrics-explorer" width="800"/>
+For example, when you open an alert response page in Metrics Explorer, you can see critical thresholds defined with some number. You can then see that this threshold is also applied and enabled in the Metrics Explorer view, with exactly the same number defined.<br/> <img src={useBaseUrl('img/alerts/arp-metrics-explorer.png')} alt="arp-metrics-explorer" width="800"/>
+
+To view the Alert Response chart in Metrics Explorer, follow the steps below:
 
- To view the Alert Response chart in Metrics Explorer, follow the steps Below:
 1. Navigate to the **Alert lists** and select the alert for which you want to view the corresponding metrics and threshold values.
 1. Open the **Alert Response Page**.
 1. Click the **View in Metrics Explorer** button for that alert. You can click on either of the two buttons, and they both function the same way.

docs/alerts/monitors/create-monitor.md

@@ -262,20 +262,20 @@ Alert Name allows you to customize the name that appears on the Alert Page. By d
 ### Evaluation Delay
 Collection delays may occur due to your environment and it takes a couple of minutes for data to be processed into Sumo Logic. Since Monitors run on data from the most current time period, it's possible for Monitors to evaluate against incomplete data. As a result, Monitors can generate false positives or negatives that can cause confusion. Set an evaluation delay in seconds to delay the evaluation of a Monitor, so it doesn't look at the most current time (where data can be incomplete) and instead looks at an older period of time, where you have more complete data.<br/> ![additional settings evaluation delay.png](/img/monitors/additional-settings-evaluation-delay.png)<br/>If your data is coming from the [Amazon CloudWatch Source for Metrics](/docs/send-data/hosted-collectors/amazon-aws/amazon-cloudwatch-source-metrics.md) we recommend a setting of 900 seconds.
 
-## Step 3: Notifications
-When a trigger condition is met you can send notifications to other people and services. To add notifications, click on the **Add Notification** button. You can add more than one notification channel for a Monitor.<br/>  ![monitor notifications input.png](/img/monitors/monitor-notifications-input.png)
+## Step 3: Notifications (optional)
 
-Metric Monitors have an option to send notifications either as a group or separately. **Group Notifications** define whether you want single notifications per time series that match the Monitor query or you want group notifications where you receive a single notification for the entire Monitor. Log Monitors always group notifications.
+When a trigger condition is met, you can send notifications to other people and services. Metrics monitors have an option to send notifications either as a group or separately. **Group Notifications** define whether you want single notifications per time series that match the Monitor query or you want group notifications where you receive a single notification for the entire Monitor. Log monitors always group notifications.
 
-The **Connection Type** specifies the notification channel where you want to get notified, such as an email or webhook. See [Connections](/docs/manage/connections-integrations) for details. Monitor notifications support variables to reference its configuration settings or your raw data. See [alert variables](/docs/alerts/monitors/alert-variables) for a table of the available variables.
-* **Email**: Provide 1-100 recipient email addresses. You can customize the email subject and body.
-* **Webhook**: By default, the payload defined on the Connection is used. You can customize your payload for each notification if needed.
+To add notifications, click the **Add Notification** button. You can add more than one notification channel for a Monitor.
 
+<img src={useBaseUrl('img/monitors/monitor-notifications-input.png')} alt="monitor notifications input.png" style={{border: '1px solid black'}} width="500"/>
+
+1. Set your **Preferred Notification Time Zone** for your monitor's alert notifications. If you don't select anything, it will default to the time zone specified in your user preferences.
+1. The **Connection Type** specifies the notification channel where you want to get notified, such as an email or webhook. See [Connections](/docs/manage/connections-integrations) for details. Monitor notifications support variables to reference its configuration settings or your raw data. See [alert variables](/docs/alerts/monitors/alert-variables) for a table of the available variables.
+   * **Email**: Provide 1-100 recipient email addresses. You can customize the email subject and body.
+   * **Webhook**: By default, the payload defined on the Connection is used. You can customize your payload for each notification if needed.
 1. Select the **Alert** and **Recovery** checkboxes for each trigger type based on when you want to send a notification.  You can have different Trigger Conditions send a notification to different channels. For example, you can get notified on PagerDuty for critical Incidents and get an email or Slack notification for warning incidents.
-   :::tip
-   See the [Notifications section](#notifications) for details on alert and recovery notifications.
-   :::
-   If your connection type is Lambda, Microsoft Teams, OpsGenie, PagerDuty, Slack, or a generic webhook, the **Recovery** checkbox enables an automatic resolution process that updates the connection when an alert has recovered within Sumo Logic. Support for other connection types is coming soon.
+   * If your connection type is Lambda, Microsoft Teams, OpsGenie, PagerDuty, Slack, or a generic webhook, the **Recovery** checkbox enables an automatic resolution process that updates the connection when an alert has recovered within Sumo Logic. Support for other connection types is coming soon.
    * **Add Notifications** to add additional notification channels as needed. You can configure different notifications for each trigger type, critical, warning, and missing data.
 
 ## Step 4: Monitor Details

docs/alerts/monitors/settings.md

@@ -22,9 +22,9 @@ Open the [Alert List](alert-response.md) to view all of the triggered alerts fr
 
 At the top of the page, you can:
 * **Search Monitors**. Use the search field to filter Monitors by name and status. For example, you can view all Monitors that are currently triggered in the system by clicking the **Status: All Triggered**. <br/><img src={useBaseUrl('img/monitors/search-monitors-input.png')} alt="search monitors input" width="175"/>
-* **Add** > **New Folder**: create a folder to organize your Monitors.
-* **Add** > **New Monitor**: create a [new Monitor](#add-a-monitor).
-* **Add** > **Import**: import Monitors from the exported JSON you copied from the **More Actions** menu in the [Details pane](#details-pane) of the original monitor.<br/><img src={useBaseUrl('img/monitors/Add-monitors-page.png')} alt="Add monitors page" width="115"/>
+* **Add** > **New Folder**. Create a folder to organize your Monitors.
+* **Add** > **New Monitor**. Create a [new Monitor](#add-a-monitor).
+* **Add** > **Import**. Import Monitors from the exported JSON you copied from the **More Actions** menu in the [Details pane](#details-pane) of the original monitor.<br/><img src={useBaseUrl('img/monitors/Add-monitors-page.png')} alt="Add monitors page" width="115"/>
 
 :::important
 The **Import** function is provided for you to transfer data immediately. The Sumo Logic JSON format may change without notice. There is no guarantee that you will be able to import the JSON in the future.
@@ -46,9 +46,9 @@ In the details pane, you'll see the following details for a Monitor:
 * **Type**. Shows the type of Monitor, either Logs or Metrics.
 * **Path**. Shows the Library location where the monitor is located.
 * **Query**. It is used to track your data. 
-* **Trigger Conditions** Thresholds value that must met for Monitor to trigger an alert. These values are set when you create a monitor and can be based on a variety of metrics such as CPU usage, network latency, application response time. . Applicable values include Critical, Warning, and Missing Data.
+* **Trigger Conditions** Thresholds value that must met for Monitor to trigger an alert. These values are set when you create a monitor and can be based on a variety of metrics such as CPU usage, network latency, application response time. Applicable values include Critical, Warning, and Missing Data.
 * **Notifications**. These are configured on the Monitor.
-* The timestamp and user that **Created** and last **Modified** the Monitor.
+* The timestamp and user that **Created** and last **Modified** the Monitor. The alert response page will show alert details in the time zone designated in your user preferences.
 
 ### View in Metrics Explorer