diff --git a/docs/_snippets/cloud/integrations/cards-groups/cloud-integrations-cards.mdx b/docs/_snippets/cloud/integrations/cards-groups/cloud-integrations-cards.mdx deleted file mode 100644 index 121020434..000000000 --- a/docs/_snippets/cloud/integrations/cards-groups/cloud-integrations-cards.mdx +++ /dev/null @@ -1,23 +0,0 @@ -### Data warehouses - - - -### Transformation and orchestration - - - -### Data visualization - - - -### Reverse ETL - - - -### Code repositories - - - -### Alerts & incidents - - \ No newline at end of file diff --git a/docs/_snippets/dwh/bigquery/cli_service_account.mdx b/docs/_snippets/dwh/bigquery/cli_service_account.mdx deleted file mode 100644 index 2d66aba18..000000000 --- a/docs/_snippets/dwh/bigquery/cli_service_account.mdx +++ /dev/null @@ -1,3 +0,0 @@ - - - diff --git a/docs/_snippets/dwh/bigquery/cloud_service_account.mdx b/docs/_snippets/dwh/bigquery/cloud_service_account.mdx deleted file mode 100644 index 703186db4..000000000 --- a/docs/_snippets/dwh/bigquery/cloud_service_account.mdx +++ /dev/null @@ -1,4 +0,0 @@ - - - - diff --git a/docs/_snippets/faq/question-schema.mdx b/docs/_snippets/faq/question-schema.mdx deleted file mode 100644 index 5a80fc069..000000000 --- a/docs/_snippets/faq/question-schema.mdx +++ /dev/null @@ -1,5 +0,0 @@ - - - - - diff --git a/docs/cloud/features.mdx b/docs/cloud/features.mdx index 4a27276bb..ae375317f 100644 --- a/docs/cloud/features.mdx +++ b/docs/cloud/features.mdx @@ -3,4 +3,8 @@ title: "Platform features" icon: "browsers" --- - \ No newline at end of file +import Features from '/snippets/cloud/features.mdx'; + + + + \ No newline at end of file diff --git a/docs/cloud/features/alerts-and-incidents/alert-rules.mdx b/docs/cloud/features/alerts-and-incidents/alert-rules.mdx index 6ecd26666..70daab05b 100644 --- a/docs/cloud/features/alerts-and-incidents/alert-rules.mdx +++ b/docs/cloud/features/alerts-and-incidents/alert-rules.mdx @@ -2,7 +2,11 @@ title: "Alert rules" --- - +import CloudFeatureTag from '/snippets/cloud/cloud-feature-tag.mdx'; + + + + **Alert Rules** help you control where alerts are sent and when they are triggered, so you can stay focused on the incidents that matter most. In Elementary Cloud, each rule combines **filters** (what to alert on) and **destinations** (where to send the alert). diff --git a/docs/cloud/features/alerts-and-incidents/alerts-and-incidents-overview.mdx b/docs/cloud/features/alerts-and-incidents/alerts-and-incidents-overview.mdx index 41e3eec25..5bfbc9b60 100644 --- a/docs/cloud/features/alerts-and-incidents/alerts-and-incidents-overview.mdx +++ b/docs/cloud/features/alerts-and-incidents/alerts-and-incidents-overview.mdx @@ -3,6 +3,11 @@ title: Alerts and Incidents Overview sidebarTitle: Alerts & incidents overview --- +import AlertTypes from '/snippets/cloud/features/alerts-and-incidents/alert-types.mdx'; +import AlertsDestinationCards from '/snippets/cloud/integrations/cards-groups/alerts-destination-cards.mdx'; + + + Alerts and incidents in Elementary are designed to shorten your time to response and time to resolution when data issues occur. - **Alert -** Notification about an event that indicates a data issue. @@ -51,8 +56,8 @@ you will be able to track all open and historical incidents, and get metrics on ## Alert types - + ## Supported alert integrations - + diff --git a/docs/cloud/features/alerts-and-incidents/incident-management.mdx b/docs/cloud/features/alerts-and-incidents/incident-management.mdx index e85a80c2d..4b1b69d0d 100644 --- a/docs/cloud/features/alerts-and-incidents/incident-management.mdx +++ b/docs/cloud/features/alerts-and-incidents/incident-management.mdx @@ -3,7 +3,11 @@ title: Incident Management sidebarTitle: Incident management --- - +import CloudFeatureTag from '/snippets/cloud/cloud-feature-tag.mdx'; + + + + The `Incidents` page is designed to enable your team to stay on top of open incidents and collaborate on resolving them. The page gives a comprehensive overview of all current and previous incidents, where users can view the status, prioritize, assign and resolve incidents. diff --git a/docs/cloud/features/alerts-and-incidents/incidents.mdx b/docs/cloud/features/alerts-and-incidents/incidents.mdx index 10809c345..d11752de6 100644 --- a/docs/cloud/features/alerts-and-incidents/incidents.mdx +++ b/docs/cloud/features/alerts-and-incidents/incidents.mdx @@ -3,7 +3,11 @@ title: Incidents in Elementary sidebarTitle: Incidents --- - +import CloudFeatureTag from '/snippets/cloud/cloud-feature-tag.mdx'; + + + + One of the challenges data teams face is tracking and understand and collaborate on the status of data issues. Tests fail daily, pipelines are executed frequently, alerts are sent to different channels. diff --git a/docs/cloud/features/alerts-and-incidents/owners-and-subscribers.mdx b/docs/cloud/features/alerts-and-incidents/owners-and-subscribers.mdx index 362615eea..4486f302c 100644 --- a/docs/cloud/features/alerts-and-incidents/owners-and-subscribers.mdx +++ b/docs/cloud/features/alerts-and-incidents/owners-and-subscribers.mdx @@ -2,6 +2,11 @@ title: "Owners and subscribers" --- +import Owner from '/snippets/alerts/owner.mdx'; +import Subscribers from '/snippets/alerts/subscribers.mdx'; + + + We highly recommend configuring owners and subscribers for your models and/or tests. An owner is the person responsible for the model, and subscribers are the people who are interested in getting the alerts on the model or test. Owners and subscribers will be mentioned (tagged) in the Slack alerts. Also their name will appear in the alerts and the UI. @@ -12,8 +17,8 @@ configuring owners and subscribers: Owners can be easily added or edited in the Catalog screen. [Learn more about managing your assets' metadata.](/cloud/features/data-governance/manage-metadata) #### Configuting owners in code: - + ### Subscribers - + diff --git a/docs/cloud/features/anomaly-detection/automated-freshness.mdx b/docs/cloud/features/anomaly-detection/automated-freshness.mdx index 8b0357e0e..c86e0f77a 100644 --- a/docs/cloud/features/anomaly-detection/automated-freshness.mdx +++ b/docs/cloud/features/anomaly-detection/automated-freshness.mdx @@ -3,6 +3,11 @@ title: Automated Freshness Monitor sidebarTitle: "Automated freshness" --- +import FreshnessConfiguration from '/snippets/cloud/features/anomaly-detection/freshness-configuration.mdx'; +import AllAnomaliesConfiguration from '/snippets/cloud/features/anomaly-detection/all-anomalies-configuration.mdx'; + + + The purpose of the Freshness monitor is to alert when a data asset hasn't been updated in a period of time that exceeds the update SLA of that table. Freshness monitors are by default created for all sources in your dbt project. They can be created for additional tables upon request. @@ -59,5 +64,5 @@ Use the `Anomaly settings` and `result feedback` buttons to impact the monitor. ### Anomaly settings - - + + diff --git a/docs/cloud/features/anomaly-detection/automated-monitors.mdx b/docs/cloud/features/anomaly-detection/automated-monitors.mdx index 428bce61d..588cbcd95 100644 --- a/docs/cloud/features/anomaly-detection/automated-monitors.mdx +++ b/docs/cloud/features/anomaly-detection/automated-monitors.mdx @@ -3,9 +3,15 @@ title: Automated Freshness & Volume Monitors sidebarTitle: "Introduction" --- - +import CloudFeatureTag from '/snippets/cloud/cloud-feature-tag.mdx'; +import AutomatedMonitorsIntro from '/snippets/cloud/features/anomaly-detection/automated-monitors-intro.mdx'; +import AutomatedMonitorsCards from '/snippets/cloud/features/anomaly-detection/automated-monitors-cards.mdx'; - + + + + + Once your environment is set up, we automatically collect metadata from your warehouse, which our ML models run on. The models are operational when the initial backfill is completed, there is no "loading / training period" - Elementary will collect enough historical data after setup to train the models. @@ -36,7 +42,7 @@ You can fine tune the [configuration](/cloud/features/anomaly-detection/monitors ## Automated Monitors - + ## Alerts on Failures diff --git a/docs/cloud/features/anomaly-detection/automated-volume.mdx b/docs/cloud/features/anomaly-detection/automated-volume.mdx index 15b66da75..6e45c285a 100644 --- a/docs/cloud/features/anomaly-detection/automated-volume.mdx +++ b/docs/cloud/features/anomaly-detection/automated-volume.mdx @@ -3,6 +3,11 @@ title: Automated Volume Monitor sidebarTitle: "Automated volume" --- +import VolumeConfiguration from '/snippets/cloud/features/anomaly-detection/volume-configuration.mdx'; +import AllAnomaliesConfiguration from '/snippets/cloud/features/anomaly-detection/all-anomalies-configuration.mdx'; + + + The volume monitor tracks the **total row count** of a table over time, rather than individual table updates. This means that Elementary will not consider a single update as anomalous, but rather a continuous anomalous trend occurring over a period of time. @@ -31,8 +36,8 @@ Use the `Anomaly settings` and `result feedback` buttons to impact the monitor. ### Anonmaly settings - - + +