Merge branch 'master' into brokenlinks

docs/_include/general-shipping/allowed-ips.md

@@ -12,6 +12,7 @@ If necessary, allowlist the relevant IPs in your firewalls. These depend on the
 | ca-central-1 | 3.97.162.114 | AWS |
 | eu-west-2 | 18.168.65.253 | AWS |
 | ap-southeast-2 | 3.104.195.194 | AWS |
+| ap-northeast-1 | 54.238.45.227 | AWS |
 
 <!--  21 Oct 2021: These table entries are on hold until the issue with Azure regions is resolved
 | westeurope | x.x.x.x | Azure |

docs/user-guide/admin/sso/aws-sso.md

@@ -38,9 +38,19 @@ Under **Application properties**, enter the **Application start URL** given to y
 
 ![Download certificate](https://dytvr9ot2sszz.cloudfront.net/logz-docs/sso-providers/aws/application-properties-aws.png)
 
-Next, in **Application metadata**, click on the link located underneath the browse button. Enter the ACS URL and Application SAML audience given to you by Logz.io support.
+Next, in **Application metadata**, click on the link located underneath the browse button. Enter the ACS URL and Application SAML audience given to you by Logz.io support. You'll need to paste the Single Sign-on URL to the Application ACS URL, and Audience URI to Application audience.
 
-![Set entity ID](https://dytvr9ot2sszz.cloudfront.net/logz-docs/sso-providers/aws/application-metadata.gif)
+![Set entity ID](https://dytvr9ot2sszz.cloudfront.net/logz-docs/sso-providers/aws/new-saml-screen.png)
+
+Click on the **Attribute mappings** tab. 
+
+Add a new attribute called **email** and the variable `${user:email}`.
+
+To configure groups you'll need to add another attribute mapping called **groups** and the variable `${user:groups}`.
+
+[Read more about attribute mapping for AWS](https://docs.aws.amazon.com/singlesignon/latest/userguide/attributemappingsconcept.html). 
+
+![Adding attributes](https://dytvr9ot2sszz.cloudfront.net/logz-docs/sso-providers/aws/adding-attribute-aws.png)
 
 Click on **Save changes** to create your app.
 

docs/user-guide/distributed-tracing/service-list.md

@@ -63,6 +63,26 @@ Hovering over the graphs provides values for the specific time point, allowing y
 
 You can toggle your view between pods and nodes inside the service.
 
+## Track Deployment Data
+
+You can enrich your Service Overview graphs by adding an indication of recent deployments, helping you determine if a deployment has increased response times for end-users, altered your application's memory/CPU footprint, or introduced any other performance-related changes.
+
+To enable deployment tracking ability, run the [**Telemetry Collector**](https://app.logz.io/#/dashboard/send-your-data/agent/new) on your Kubernetes clusters. You can also activate this process **manually** by installing [Logz.io Kubernetes events Helm chart](https://app.logz.io/#/dashboard/integrations/Kubernetes:~:text=user%20guide.-,Send%20your%20deploy%20events%20logs,-This%20integration%20sends) and sending Kubernetes deploy events logs.
+
+Once enabled, navigate to [Services](https://app.logz.io/#/dashboard/spm/service-list/table?timeFrame=2h&compareTo=1d) and choose one of your running services. The deployment marker will appear in your graphs, marked by a dotted vertical line.
+
+![deployment popup](https://dytvr9ot2sszz.cloudfront.net/logz-docs/services/deplyment-popup.png)
+
+You can view additional deployment data by clicking on the line. This data includes the deployment time, the associated service and environment, and a quick link to view the commit in your logs.
+
+Click **Go to commit** to access and view your own code related to this deployment, allowing you to probe deeper into the relevant data.
+
+:::caution Important
+To activate the **Go to Commit** button, go to **your app or service** and add the following annotation to the metadata of each resource's versioning you want to track: `logzio/commit_url: ""`, and the URL structure should be: "`https://github.com/<account>/<repository>/commit/<commit-hash>`". [Learn more](https://github.com/logzio/logzio-helm/tree/master/charts/logzio-k8s-events#deployment-events-versioning).
+:::
+
+
+
 <!-- ### Logs overview
 
 All of the logs related to the service are shown at the bottom of the page. This view includes a graph view of the log levels and a table view with the following:

docs/user-guide/k8s-360/overview.md

@@ -470,6 +470,27 @@ Node and pod views include the **Open Livetail** button, which opens Logz.io's L
 
 The Deployment view includes the **See Traces** button, which opens Jaeger with the relevant data needed to deep dive into it. Gain a system-wide view of your distributed architecture, detect failed or high latency requests, and quickly drill into end-to-end call sequences of selected requests of intercommunicating microservices. 
 
+## Track Deployment Data
+
+You can enrich your Kubernetes 360 graphs by adding an indication of recent deployments, helping you determine if a deployment has increased response times for end-users, altered your application's memory/CPU footprint, or introduced any other performance-related changes.
+
+To enable deployment tracking ability, run the [**Telemetry Collector**](https://app.logz.io/#/dashboard/send-your-data/agent/new) on your Kubernetes clusters. You can also activate this process **manually** by installing [Logz.io Kubernetes events Helm chart](https://app.logz.io/#/dashboard/integrations/Kubernetes:~:text=user%20guide.-,Send%20your%20deploy%20events%20logs,-This%20integration%20sends). 
+
+Once enabled, the graphs will include a deployment marker, marked by a dotted vertical line.
+
+You can view additional deployment data by clicking on the line. This data includes the deployment time, the associated service and environment, and a quick link to view the commit in your logs.
+
+Click **Go to commit** to access and view your own code related to this deployment, allowing you to probe deeper into the relevant data.
+
+:::caution Important
+To activate the **Go to Commit** button, go to **your app or service** and add the following annotation to the metadata of each resource's versioning you want to track: `logzio/commit_url: ""`, and the URL structure should be: "`https://github.com/<account>/<repository>/commit/<commit-hash>`". [Learn more](https://github.com/logzio/logzio-helm/tree/master/charts/logzio-k8s-events#deployment-events-versioning).
+:::
+
+
+![deployment menu](https://dytvr9ot2sszz.cloudfront.net/logz-docs/k360/k360-deploy.png)
+
+
+
 
 <!-- ##### Locate
 {:.no_toc}

docusaurus.config.js

@@ -10,7 +10,7 @@ const config = {
   favicon: 'https://logz.io/wp-content/themes/Avada-Child-Theme-logz/theme_favicon/apple-touch-icon.png',
 
   // Set the production url of your site here
-  url: 'https://your-docusaurus-test-site.com',
+  url: 'https://docs.logz.io',
   // Set the /<baseUrl>/ pathname under which your site is served
   // For GitHub pages deployment, it is often '/<projectName>/'
   baseUrl: '/',

static/_redirects

@@ -149,6 +149,7 @@
 /user-guide/log-shipping/built-in-log-types.html		/docs/user-guide/data-hub/log-parsing/default-parsing
 /user-guide/mapping-and-parsing/split-json-array.html		/docs/user-guide/data-hub/log-parsing/split-json-array
 /user-guide/mapping-and-parsing/sawmill-parsing.html		/docs/user-guide/data-hub/log-parsing/sawmill-parsing
+/user-guide/mapping-and-parsing/sawmill-parsing		/docs/user-guide/data-hub/log-parsing/sawmill-parsing
 /user-guide/mapping-and-parsing/data-parsing-wizard.html		/docs/user-guide/data-hub/log-parsing/sawmill-parsing
 /user-guide/logs/mapping/		/docs/user-guide/data-hub/field-mapping/
 /user-guide/logs/mapping/field-not-indexed/		/docs/user-guide/data-hub/field-mapping/field-not-indexed