Merge branch 'main' into feature/better-celpy-perf

keephq · Sep 25, 2024 · 365d8c6 · 365d8c6
2 parents 0ee4975 + 4689b42
commit 365d8c6
Show file tree

Hide file tree

Showing 10 changed files with 24 additions and 162 deletions.
diff --git a/docs/mint.json b/docs/mint.json
@@ -86,12 +86,9 @@
       "group": "Platform",
       "pages": [
         "platform/overview",
-        "platform/providers",
         "platform/alerts",
         "platform/alertseverityandstatus",
-        "platform/workflows",
         "platform/settings",
-        "platform/metrics",
         "platform/support"
       ]
     },
@@ -188,7 +185,6 @@
       "group": "Workflows",
       "pages": [
         "workflows/overview",
-        "workflows/getting-started",
         {
           "group": "Syntax",
           "pages": [

diff --git a/docs/overview/examples.mdx b/docs/overview/examples.mdx
@@ -14,7 +14,7 @@ In this example we will utilze:
 
 This example consists of two steps:
 1. Connect your tools - Datadog, OpsGenie and Postgres.
-2. Create a workflow that is triggered by the alert, runs an SQL query, and decides whether to create an incident.  Once the workflow is created, you can upload it via the [Workflows](/platform/workflows) page.
+2. Create a workflow that is triggered by the alert, runs an SQL query, and decides whether to create an incident.  Once the workflow is created, you can upload it via the [Workflows](https://docs.keephq.dev/workflows/overview) page.
 ```yaml
 alert:
   id: enterprise-tier-alerts

diff --git a/docs/overview/introduction.mdx b/docs/overview/introduction.mdx
@@ -23,4 +23,4 @@ Keep helps with every step of the alert lifecycle:
 5. Summarization - Keep summarizes incidents based on past incidents and a knowledge base (Keep Enterprise only).
 
 ## How does Keep integrate with alerts?
-Alerts can either be [pulled](/platform/alerts#pulled-alerts) by Keep or [pushed](/platform/alerts#pushed-alerts) into it. Keep also offers zero-click alert instrumentation through [webhook installation](/platform/providers#webhook-integration).
+Alerts can either be [pulled](/platform/alerts#pulled-alerts) by Keep or [pushed](/platform/alerts#pushed-alerts) into it. Keep also offers zero-click alert instrumentation through [webhook installation](/providers/overview).
diff --git a/docs/overview/keyconcepts.mdx b/docs/overview/keyconcepts.mdx
@@ -27,7 +27,7 @@ For example, consider Promethues. If you want to push alerts from Promethues to
 'https://api.keephq.dev/alerts/event/prometheus' using API key authentication. Each Provider implements Push mechanism and is documented under the specific Provider page.
 
 #### Push alerts to Keep (Automatic)
-In compatible tools, Keep can automatically integrate with the alerting policy of the source tool and add itself as an alert destination. You can learn more about Webhook Integration [here](/platform/providers#webhook-integration).
+In compatible tools, Keep can automatically integrate with the alerting policy of the source tool and add itself as an alert destination. You can learn more about Webhook Integration [here](/providers/overview).
 Please note that this will slightly modify your monitors/notification policy.
 
 ### Pull alerts by Keep

diff --git a/docs/platform/overview.mdx b/docs/platform/overview.mdx
@@ -9,7 +9,7 @@ The platform is accessible on https://platform.keephq.dev and let you start the
 
 The platform is currently built on top of:
 
-1. [Providers](/platform/providers) - connect your stack to Keep.
+1. [Providers](/providers/overview) - connect your stack to Keep.
 2. [Alerts](/platform/alerts) - single pane of glass for your alerts.
-3. [Workflows](/platform/workflows) - create automations on top of your alerts (or regardless).
+3. [Workflows](/workflows/overview) - create automations on top of your alerts (or regardless).
 4. [Settings](/platform/settings) - the settings page (add users, etc).
diff --git a/docs/platform/providers.mdx b/docs/platform/providers.mdx
diff --git a/docs/platform/workflows.mdx b/docs/platform/workflows.mdx
diff --git a/docs/workflows/getting-started.mdx b/docs/workflows/getting-started.mdx
diff --git a/keep-ui/next.config.js b/keep-ui/next.config.js
@@ -41,8 +41,8 @@ const nextConfig = {
       : [
           {
             source: "/",
-            destination: "/providers",
-            permanent: true,
+            destination: "/incidents",
+            permanent: process.env.ENV === "production",
           },
         ];
   },

diff --git a/tests/e2e_tests/test_end_to_end.py b/tests/e2e_tests/test_end_to_end.py
@@ -45,9 +45,23 @@
 
 
 def test_sanity(browser):
-    browser.goto("http://localhost:3000/providers")
-    browser.wait_for_url("http://localhost:3000/providers")
-    assert "Keep" in browser.title()
+    try:
+        browser.goto("http://localhost:3000/")
+        browser.wait_for_url("http://localhost:3000/incidents")
+        assert "Keep" in browser.title()
+    except Exception:
+        # Current file + test name for unique html and png dump.
+        current_test_name = (
+            "playwright_dump_"
+            + os.path.basename(__file__)[:-3]
+            + "_"
+            + sys._getframe().f_code.co_name
+        )
+
+        browser.screenshot(path=current_test_name + ".png")
+        with open(current_test_name + ".html", "w") as f:
+            f.write(browser.content())
+        raise
 
 
 def test_insert_new_alert(browser):