From de50b7b559377b959bb95bdee42b67502fb9dc20 Mon Sep 17 00:00:00 2001 From: Maayan-s Date: Wed, 3 Jul 2024 15:16:10 +0300 Subject: [PATCH] change log --- docs/changelog.mdx | 478 ++++++++++++++++++ .../alerts-and-incidents/alert-rules.mdx | 18 +- docs/mint.json | 7 +- 3 files changed, 494 insertions(+), 9 deletions(-) create mode 100644 docs/changelog.mdx diff --git a/docs/changelog.mdx b/docs/changelog.mdx new file mode 100644 index 000000000..94dbe76d2 --- /dev/null +++ b/docs/changelog.mdx @@ -0,0 +1,478 @@ +--- +title: Elementary Changelog +description: "See what's new in the cloud platform" +--- + +## May 2024 + +### Add any dbt test via UI + +
+
+
+ Test configuration + Data tests +
+
+ Elementary now supports adding any dbt test in bulk and directly from the UI! + We added support for dbt-expectation and dbt-utils packages, and you can use it to add your own custom generic tests to tables and columns. + + + +
+
+
+ +### Column anomalies by dimensions + +
+
+
+ Anomaly detection monitors +
+
+ You can now add a new parameter to your column anomaly tests - `dimensions`. + + This will calculate the column metrics for every time bucket and table dimension values, allowing you to detect anomalies in specific segments of your data. + + For example, if you want to detect anomalies in a revenue column and you have multiple apps in different countries - now you can detect anomalies in revenue in a specific country. + + Here is an example of how this can be configured - + + ```yaml + columns: + - name: in_app_purchase_revenue + tests: + - elementary.column_anomalies: + column_anomalies: + - sum + dimensions: + - app_name + - country + ``` +
+
+ +
+ +### Column level test results in lineage + +
+
+
+ Data lineage +
+
+ You can now investigate test results right on top of your column level lineage graph. + With this new release you can filter the lineage graph on a specific column that has an issue, and see if upstream or downstream columns + have similar test failures to understand the root cause fast. + + + +
+
+ +
+ +### Monitor test durations + +
+
+
+ Performance monitoring + Data tests +
+
+ We added test durations to the Test Execution History (the command and control center for your tests). You can now monitor your tests performance and see which tests are taking the longest or if there was any degradation in performance of specific tests. + + Easily sort your tests by execution duration and see which ones are taking the longest and choose the most promising candidates for optimization. This can also be used for cost analysis as slow tests tend to be more expensive. + + Check it out: + + + +
+
+ +
+ +### Sync now + +
+
+
+ Environments +
+
+ We are excited to launch a new `Sync Now` button right in your environments page. You can think of is as a "refresh now" button for your environment. + If you introduced a change in your environment and you want to see it in Elementary immediately - just click ‘sync now’. + + Here is what it looks like - + + + +
+
+ +
+ +## April 2024 + +### Status and assignee for alerts + +
+
+
+ Alerts +
+
+ An alert is just the start of a triage and response process. We have big plans for making this process much more effective. + The first step was alert rules, and now we are introducing status and assignee selection in our alerts. + + This should help you manage incidents and collaborate more effectively with your team. + + + ![Status and assignee for alerts](pics/changelog/status-and-assignee-for-alerts.png) + + +
+ +
+
+ +### Custom SQL tests in UI + +
+
+
+ Test configuration +
+
+ Custom query testing is a must-have to validate business logic specific to your data team. You can now create custom SQL tests with Elementary, which will be translated into singular tests in your dbt project. + + + + + +
+
+ +
+ +### Model runs in dashboard + +
+
+
+ Dashboard +
+
+ The results of your jobs are critical to the data health. These are now included in the Elementary dashboard, for you to get a complete overview of the status of your pipelines. We added a breakdown of the latest result of each model, and the aggregated failures over time. + + + + + +
+
+ +
+ +### DAG subset in Lineage + +
+
+
+ Data lineage +
+
+ To improve UX and performance, we changed the default behavior in the lineage. + When a node or group of nodes is chosen, only the first hop in both directions is loaded. To see the rest of the hops you can use the +/- buttons (see video). + + + + + +
+
+ +
+ +### Role-based access control + +
+
+
+ Security and permissions +
+
+ Elementary now allows creating users with different roles. + This will allow you to add more users from your team to Elementary, allowing them to view results without giving them the ability to change environment settings. + + + + +
+
+ +
\ No newline at end of file diff --git a/docs/features/alerts-and-incidents/alert-rules.mdx b/docs/features/alerts-and-incidents/alert-rules.mdx index f54201191..16c262c68 100644 --- a/docs/features/alerts-and-incidents/alert-rules.mdx +++ b/docs/features/alerts-and-incidents/alert-rules.mdx @@ -2,6 +2,8 @@ title: "Alert rules" --- + + Elementary Cloud allows you to create rules to route your alerts. Each rule is a combination of a filter and a destination. @@ -10,13 +12,6 @@ or incident management ([PagerDuty](/cloud/integrations/alerts/pagerduty), [Opsg [integration](/features/alerts-and-incidents/alerts-and-incidents-overview#supported-alert-integrations), and for supporting tools a specific channel. -### Default alert rule - -The channel you choose when connecting your messaging app ([Slack](/cloud/integrations/alerts/slack), [Microsoft Teams](/cloud/integrations/alerts/ms-teams), etc.) -is automatically added as a default alert rule, that sends all the failures to that channel without any filtering. -By default, warnings do not send alerts. -To modify, deactivate or add more rules, simply navigate to the `Alert Rules` page in the menu. - The order of rules matters! @@ -33,4 +28,11 @@ frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen alt="Elementary Alert Rules" -> \ No newline at end of file +> + +### Default alert rule + +The channel you choose when connecting your messaging app ([Slack](/cloud/integrations/alerts/slack), [Microsoft Teams](/cloud/integrations/alerts/ms-teams), etc.) +is automatically added as a default alert rule, that sends all the failures to that channel without any filtering. +By default, warnings do not send alerts. +To modify, deactivate or add more rules, simply navigate to the `Alert Rules` page in the menu. \ No newline at end of file diff --git a/docs/mint.json b/docs/mint.json index a4b1acf83..c54ddd02b 100644 --- a/docs/mint.json +++ b/docs/mint.json @@ -53,8 +53,14 @@ "name": "Join Slack", "icon": "slack", "url": "https://elementary-data.com/community" + }, + { + "name": "Changelog", + "icon": "list", + "url": "http://localhost:3000/changelog" } ], + "navigation": [ { "group": "Getting Started", @@ -184,7 +190,6 @@ "group": "Send Slack alerts", "pages": [ "cloud/guides/enable-slack-alerts", - "cloud/guides/alert-rules", "cloud/guides/alerts-configuration" ] },