simple alerts

Author: gingerwizard

docs/use-cases/observability/clickstack/alerts.md

@@ -0,0 +1,42 @@
+---
+slug: /use-cases/observability/clickstack/alerts
+title: 'Search with ClickStack'
+sidebar_label: 'Alerts'
+pagination_prev: null
+pagination_next: null
+description: 'Alerts with ClickStack'
+---
+
+import Image from '@theme/IdealImage';
+import search_alert from '@site/static/images/use-cases/observability/search_alert.png';
+
+
+## Search alerts {#search-alerts}
+
+Aftering entering a [search](/use-cases/observability/clickstack/search), you can create an alert to be
+notified when the number of events (logs or spans) matching the search exceeds or falls below a threshold.
+
+### Creating an Alert {#creating-an-alert}
+
+You can create an alert by clicking the `Alerts` button on the top right of the `Search` page. 
+
+From here, you can name the alert, as well as set the threshold, duration, and notification method for the alert (Slack, Email, PagerDuty or Slack Webhook).
+
+The `grouped by` value allows the search to be subject to an aggregation e.g. `ServiceName`, thus allowing potential multiple alerts to be triggered off the same search.
+
+<Image img={search_alert} alt="Search alerts" size="lg"/>
+
+### Common Alert Scenarios {#common-alert-scenarios}
+
+Here are a few common alert scenarios that you can use HyperDX for:
+
+**Errors:** We first recommend setting up alerts for the default
+`All Error Events` and `HTTP Status >= 400` saved searches to be notified when
+excess error occurs.
+
+**Slow Operations:** You can set up a search for slow operations (ex.
+`duration:>5000`) and then alert when there are too many slow operations
+occuring.
+
+**User Events:** You can also set up alerts for customer-facing teams to be
+notified when new users sign up, or a critical user action is performed.

docs/use-cases/observability/clickstack/example-datasets/remote-demo-data.md

@@ -43,7 +43,7 @@ import edit_connection from '@site/static/images/use-cases/observability/edit_co
 
 This getting started guide uses a dataset available on the demo server that users can access when first deploying HyperDX. The dataset is hosted on the public ClickHouse instance at [sql.clickhouse.com](https://sql.clickhouse.com).
 
-It contains approximately 36 hours of data captured from the ClickHouse version of the official OpenTelemetry (OTel) demo. The data is replayed nightly with timestamps adjusted to the current time window, allowing users to explore system behavior using HyperDX's integrated logs, traces, and metrics.
+It contains approximately 40 hours of data captured from the ClickHouse version of the official OpenTelemetry (OTel) demo. The data is replayed nightly with timestamps adjusted to the current time window, allowing users to explore system behavior using HyperDX's integrated logs, traces, and metrics.
 
 :::note Data variations
 Because the dataset is replayed from midnight each day, the exact visualizations may vary depending on when you explore the demo.
@@ -75,7 +75,9 @@ Further details on the demo can be found in the [official OpenTelemetry document
 
 ### Connect to the demo server {#connect-to-the-demo-server}
 
-**This step can be skipped if you clicked `Connect to Demo Server` when deploying in Local Mode.**
+:::note Local-Only mode
+This step can be skipped if you clicked `Connect to Demo Server` when deploying in Local Mode. If using this mode, sources will be prefixed with `Demo_` e.g. `Demo_Logs`
+:::
 
 Navigate to `Team Settings` and click `Edit` for the `Local Connection`:
 
@@ -92,7 +94,9 @@ Rename the connection to `Demo` and complete the subsequent form with the follow
 
 ### Modify the sources {#modify-sources}
 
-**This step can be skipped if you clicked `Connect to Demo Server` when deploying in Local Mode.**
+:::note Local-Only mode
+This step can be skipped if you clicked `Connect to Demo Server` when deploying in Local Mode. If using this mode, sources will be prefixed with `Demo_` e.g. `Demo_Logs`
+:::
 
 Scroll up to `Sources` and modify each of the sources - `Logs`, `Traces`, `Metrics`, and `Sessions` - to use the `otel_v2` database. 
 

sidebars.js

@@ -1619,8 +1619,8 @@ const sidebars = {
         },
         "use-cases/observability/clickstack/config",
         "use-cases/observability/clickstack/search",
+        "use-cases/observability/clickstack/alerts",
         "use-cases/observability/clickstack/production",
-        
       ]
     },
   ],