Updating links - Sitebase removed, added missing pages

docs/_include/api-cookbook/replace-vars.html

@@ -28,4 +28,4 @@
 
 * Replace `<<API-TOKEN>>` with an [API token](https://app.logz.io/#/dashboard/settings/manage-tokens/api) from the account you want to use
 * Replace `<<API-URL>>` with your region's base API URL.
-  For more information on finding your account's region, see [Account region]({{site.baseurl}}/user-guide/accounts/account-region.html).
+  For more information on finding your account's region, see [Account region](/docs/user-guide/admin/hosting-regions/account-region).

docs/shipping/AWS/1aws-native.md

@@ -84,7 +84,7 @@ If you've used the `services` field, you'll have to **wait 6 minutes** before cr
 
 Give your logs some time to get from your system to ours, and then open [Open Search Dashboards](https://app.logz.io/#/dashboard/osd).
 
-If you still don't see your logs, see [log shipping troubleshooting]({{site.baseurl}}/user-guide/log-shipping/log-shipping-troubleshooting.html).
+If you still don't see your logs, see [log shipping troubleshooting](/docs/user-guide/log-management/troubleshooting/log-shipping-troubleshooting/).
 
 ## Metrics
 

docs/shipping/AWS/aws-amplify.md

@@ -90,7 +90,7 @@ If you've used the `services` field, you'll have to **wait 6 minutes** before cr
 
 Give your logs some time to get from your system to ours, and then open [Open Search Dashboards](https://app.logz.io/#/dashboard/osd).
 
-If you still don't see your logs, see [log shipping troubleshooting]({{site.baseurl}}/user-guide/log-shipping/log-shipping-troubleshooting.html).
+If you still don't see your logs, see [log shipping troubleshooting](/docs/user-guide/log-management/troubleshooting/log-shipping-troubleshooting/).
 
 
 
@@ -192,4 +192,4 @@ git clone https://github.com/logzio/logzio_aws_serverless.git \
 
 Give your logs some time to get from your system to ours, and then open [Open Search Dashboards](https://app.logz.io/#/dashboard/osd).
 
-If you still don't see your logs, see [log shipping troubleshooting](https://docs.logz.io/user-guide/log-shipping/log-shipping-troubleshooting.html).
+If you still don't see your logs, see [log shipping troubleshooting](/docs/user-guide/log-management/troubleshooting/log-shipping-troubleshooting/).

docs/shipping/AWS/aws-api-gateway.md

@@ -89,7 +89,7 @@ If you've used the `services` field, you'll have to **wait 6 minutes** before cr
 
 Give your logs some time to get from your system to ours, and then open [Open Search Dashboards](https://app.logz.io/#/dashboard/osd).
 
-If you still don't see your logs, see [log shipping troubleshooting]({{site.baseurl}}/user-guide/log-shipping/log-shipping-troubleshooting.html).
+If you still don't see your logs, see [log shipping troubleshooting](/docs/user-guide/log-management/troubleshooting/log-shipping-troubleshooting/).
 
 ## Metrics
 

docs/shipping/AWS/aws-app-elb.md

@@ -23,7 +23,7 @@ When you set Logz.io to fetch Elastic Load Balancing (ELB) logs, Logz.io will pe
 
 
 **Before you begin, you'll need**:
-`s3:ListBucket` and `s3:GetObject` [permissions](https://docs.logz.io/user-guide/give-aws-access-with-iam-roles/) for the required S3 bucket (one bucket per region)
+`s3:ListBucket` and `s3:GetObject` [permissions](/docs/user-guide/admin/give-aws-access-with-iam-roles) for the required S3 bucket (one bucket per region)
 
 
 
@@ -49,7 +49,7 @@ Log into the app to use the dedicated Logz.io [configuration wizard](https://app
 
 Give your logs some time to get from your system to ours, and then open [Open Search Dashboards](https://app.logz.io/#/dashboard/osd).
 
-If you still don't see your logs, see [log shipping troubleshooting]({{site.baseurl}}/user-guide/log-shipping/log-shipping-troubleshooting.html).
+If you still don't see your logs, see [log shipping troubleshooting](/docs/user-guide/log-management/troubleshooting/log-shipping-troubleshooting/).
 
 
 ## Configure AWS to forward metrics to Logz.io

docs/shipping/AWS/aws-athena.md

@@ -84,7 +84,7 @@ If you've used the `services` field, you'll have to **wait 6 minutes** before cr
 
 Give your logs some time to get from your system to ours, and then open [Open Search Dashboards](https://app.logz.io/#/dashboard/osd).
 
-If you still don't see your logs, see [log shipping troubleshooting]({{site.baseurl}}/user-guide/log-shipping/log-shipping-troubleshooting.html).
+If you still don't see your logs, see [log shipping troubleshooting](/docs/user-guide/log-management/troubleshooting/log-shipping-troubleshooting/).
 
 ## Metrics
 

docs/shipping/AWS/aws-classic-elb.md

@@ -29,7 +29,7 @@ When you set Logz.io to fetch Elastic Load Balancing (ELB) logs, Logz.io will pe
 
 
 **Before you begin, you'll need**:
-`s3:ListBucket` and `s3:GetObject` [permissions](https://docs.logz.io/user-guide/give-aws-access-with-iam-roles/) for the required S3 bucket (one bucket per region)
+`s3:ListBucket` and `s3:GetObject` [permissions](/docs/user-guide/admin/give-aws-access-with-iam-roles) for the required S3 bucket (one bucket per region)
 
 
 
@@ -55,7 +55,7 @@ Log into the app to use the dedicated Logz.io [configuration wizard](https://app
 
 Give your logs some time to get from your system to ours, and then open [Open Search Dashboards](https://app.logz.io/#/dashboard/osd).
 
-If you still don't see your logs, see [log shipping troubleshooting]({{site.baseurl}}/user-guide/log-shipping/log-shipping-troubleshooting.html).
+If you still don't see your logs, see [log shipping troubleshooting](/docs/user-guide/log-management/troubleshooting/log-shipping-troubleshooting/).
 
 
 

docs/shipping/AWS/aws-cloudfront.md

@@ -32,7 +32,7 @@ CloudFront logs are useful for auditing/security monitoring and business intelli
 
 **Before you begin, you'll need**:
 
-* `s3:ListBucket` and `s3:GetObject` [permissions](https://docs.logz.io/user-guide/give-aws-access-with-iam-roles/) for the required S3 bucket
+* `s3:ListBucket` and `s3:GetObject` [permissions](/docs/user-guide/admin/give-aws-access-with-iam-roles) for the required S3 bucket
 
 * {@include: ../../_include/log-shipping/s3-bucket-file-order.md}
 
@@ -57,7 +57,7 @@ Log into the app to use the dedicated Logz.io [configuration wizard](https://app
 
 Give your logs some time to get from your system to ours, and then open [Open Search Dashboards](https://app.logz.io/#/dashboard/osd).
 
-If you still don't see your logs, see [log shipping troubleshooting]({{site.baseurl}}/user-guide/log-shipping/log-shipping-troubleshooting.html).
+If you still don't see your logs, see [log shipping troubleshooting](/docs/user-guide/log-management/troubleshooting/log-shipping-troubleshooting/).
 
 
 ## Metrics

docs/shipping/AWS/aws-cloudtrail.md

@@ -23,7 +23,7 @@ drop_filter: []
 
 **Before you begin**:
 
-* If you plan on using an access key to authenticate your connection, you'll need to set the `s3:ListBucket` and `s3:GetObject` [permissions](https://docs.logz.io/user-guide/give-aws-access-with-iam-roles/) for the required S3 bucket.
+* If you plan on using an access key to authenticate your connection, you'll need to set the `s3:ListBucket` and `s3:GetObject` [permissions](/docs/user-guide/admin/give-aws-access-with-iam-roles) for the required S3 bucket.
 
 * If you plan on using an IAM role to authenticate your connection, you can get the role policy by filling out the bucket information and clicking the "Get the role policy" button.
 
@@ -105,7 +105,7 @@ Logz.io cannot fetch past logs retroactively.
 
 Give your logs some time to get from your system to ours, and then open [Open Search Dashboards](https://app.logz.io/#/dashboard/osd).
 
-If you still don't see your logs, see [log shipping troubleshooting]({{site.baseurl}}/user-guide/log-shipping/log-shipping-troubleshooting.html).
+If you still don't see your logs, see [log shipping troubleshooting](/docs/user-guide/log-management/troubleshooting/log-shipping-troubleshooting/).
 
 
 ## Troubleshooting

docs/shipping/AWS/aws-control-tower.md

@@ -153,7 +153,7 @@ If want to delete the S3 Hook Stack - you'll need to detach the policy "LambdaAc
 
 Give your logs some time to get from your system to ours, and then open [Open Search Dashboards](https://app.logz.io/#/dashboard/osd).
 
-If you still don't see your logs, see [log shipping troubleshooting]({{site.baseurl}}/user-guide/log-shipping/log-shipping-troubleshooting.html).
+If you still don't see your logs, see [log shipping troubleshooting](/docs/user-guide/log-management/troubleshooting/log-shipping-troubleshooting/).
 
 
 

docs/shipping/AWS/aws-cost-and-usage-report.md

@@ -85,7 +85,7 @@ All logs that were sent from the Lambda function will be under the type **billin
 
 To get more out of this functionality, you can enable a dedicated AWS cost and usage dashboard in [ELK Apps](https://app.logz.io/#/dashboard/elk-apps).
 
-If you still don't see your logs, see [log shipping troubleshooting]({{site.baseurl}}/user-guide/log-shipping/log-shipping-troubleshooting.html).
+If you still don't see your logs, see [log shipping troubleshooting](/docs/user-guide/log-management/troubleshooting/log-shipping-troubleshooting/).
 
 
 

docs/shipping/AWS/aws-dynamodb.md

@@ -20,7 +20,7 @@ drop_filter: []
 
 **Before you begin**:
 
-* If you plan on using an access key to authenticate your connection, you'll need to set the `s3:ListBucket` and `s3:GetObject` [permissions](https://docs.logz.io/user-guide/give-aws-access-with-iam-roles/) for the required S3 bucket.
+* If you plan on using an access key to authenticate your connection, you'll need to set the `s3:ListBucket` and `s3:GetObject` [permissions](/docs/user-guide/admin/give-aws-access-with-iam-roles) for the required S3 bucket.
 
 * If you plan on using an IAM role to authenticate your connection, you can get the role policy by filling out the bucket information and clicking the "Get the role policy" button.
 
@@ -102,7 +102,7 @@ Logz.io cannot fetch past logs retroactively.
 
 Give your logs some time to get from your system to ours, and then open [Open Search Dashboards](https://app.logz.io/#/dashboard/osd).
 
-If you still don't see your logs, see [log shipping troubleshooting]({{site.baseurl}}/user-guide/log-shipping/log-shipping-troubleshooting.html).
+If you still don't see your logs, see [log shipping troubleshooting](/docs/user-guide/log-management/troubleshooting/log-shipping-troubleshooting/).
 
 
 ## Troubleshooting

docs/shipping/AWS/aws-ec2-auto-scaling.md

@@ -21,7 +21,7 @@ drop_filter: []
 
 **Before you begin**:
 
-* If you plan on using an access key to authenticate your connection, you'll need to set the `s3:ListBucket` and `s3:GetObject` [permissions](https://docs.logz.io/user-guide/give-aws-access-with-iam-roles/) for the required S3 bucket.
+* If you plan on using an access key to authenticate your connection, you'll need to set the `s3:ListBucket` and `s3:GetObject` [permissions](/docs/user-guide/admin/give-aws-access-with-iam-roles) for the required S3 bucket.
 
 * If you plan on using an IAM role to authenticate your connection, you can get the role policy by filling out the bucket information and clicking the "Get the role policy" button.
 
@@ -103,7 +103,7 @@ Logz.io cannot fetch past logs retroactively.
 
 Give your logs some time to get from your system to ours, and then open [Open Search Dashboards](https://app.logz.io/#/dashboard/osd).
 
-If you still don't see your logs, see [log shipping troubleshooting]({{site.baseurl}}/user-guide/log-shipping/log-shipping-troubleshooting.html).
+If you still don't see your logs, see [log shipping troubleshooting](/docs/user-guide/log-management/troubleshooting/log-shipping-troubleshooting/).
 
 
 ## Troubleshooting

docs/shipping/AWS/aws-fsx.md

@@ -84,7 +84,7 @@ If you've used the `services` field, you'll have to **wait 6 minutes** before cr
 
 Give your logs some time to get from your system to ours, and then open [Open Search Dashboards](https://app.logz.io/#/dashboard/osd).
 
-If you still don't see your logs, see [log shipping troubleshooting]({{site.baseurl}}/user-guide/log-shipping/log-shipping-troubleshooting.html).
+If you still don't see your logs, see [log shipping troubleshooting](/docs/user-guide/log-management/troubleshooting/log-shipping-troubleshooting/).
 
 ## Metrics
 

docs/shipping/AWS/aws-guardduty.md

@@ -91,7 +91,7 @@ In the _Environment variables_ section, set your Logz.io account token, URL, and
 | TOKEN (Required) | Your Logz.io account token. {@include: ../../_include/log-shipping/log-shipping-token.html} | Required  |
 | REGION | Two-letter region code, or blank for US East (Northern Virginia). This determines your listener URL (where you're shipping the logs to) and API URL.    You can find your region code in the [Regions and URLs](https://docs.logz.io/user-guide/accounts/account-region.html#regions-and-urls) table. | Default: *blank* (US East)|
 | URL  (Deprecated)| Use REGION instead. Protocol, listener host, and port (for example, `https://<<LISTENER-HOST>>:8071`). {@include: ../../_include/log-shipping/listener-var.html}  | Required |
-| TYPE | The log type you'll use with this Lambda. This can be a [built-in log type]({{site.baseurl}}/user-guide/log-shipping/built-in-log-types.html), or a custom log type.    You should create a new Lambda for each log type you use. | `"guardduty"` |
+| TYPE | The log type you'll use with this Lambda. This can be a [built-in log type](/docs/user-guide/data-hub/log-parsing/default-parsing/#built-in-log-types), or a custom log type.    You should create a new Lambda for each log type you use. | `"guardduty"` |
 | FORMAT | `"json"` or `"text"`. If `"json"`, the Lambda function will attempt to parse the message field as JSON and populate the event data with the parsed fields. | `"text"` |
 | COMPRESS | Set to `true` to compress logs before sending them. Set to `false` to send uncompressed logs. | `false` |
 
@@ -122,7 +122,7 @@ Click **Add**, and then click **Save** at the top of the page.
 
 Give your logs some time to get from your system to ours, and then open [Open Search Dashboards](https://app.logz.io/#/dashboard/osd).
 
-If you still don't see your logs, see [log shipping troubleshooting]({{site.baseurl}}/user-guide/log-shipping/log-shipping-troubleshooting.html).
+If you still don't see your logs, see [log shipping troubleshooting](/docs/user-guide/log-management/troubleshooting/log-shipping-troubleshooting/).
 
 
 
@@ -182,7 +182,7 @@ Specify the stack details as per the table below and select **Next**.
 | KinesisStream                 | The name of the Kinesis stream where this function will listen for updates.                                                                                                                                                                                                                        | Required                   |
 | LogzioREGION                  | Two-letter region code, or blank for US East (Northern Virginia). This determines your listener URL (where you're shipping the logs to) and API URL. You can find your region code in the [Regions and URLs](https://docs.logz.io/user-guide/accounts/account-region.html#regions-and-urls) table. | Default: _blank_ (US East) |
 | LogzioURL (Deprecated)        | Use LogzioREGION instead. Protocol, listener host, and port (for example, `https://<<LISTENER-HOST>>:8071`). {@include: ../../_include/log-shipping/listener-var.html}                                                                                                                                          | Required                   |
-| LogzioTYPE                    | The log type you'll use with this Lambda. This can be a [built-in log type]({{site.baseurl}}/user-guide/log-shipping/built-in-log-types.html), or a custom log type. You should create a new Lambda for each log type you use.                                                                     | `guardduty`                |
+| LogzioTYPE                    | The log type you'll use with this Lambda. This can be a [built-in log type](/docs/user-guide/data-hub/log-parsing/default-parsing/#built-in-log-types), or a custom log type. You should create a new Lambda for each log type you use.                                                                     | `guardduty`                |
 | LogzioFORMAT                  | `"json"` or `"text"`. If `"json"`, the Lambda function will attempt to parse the message field as JSON and populate the event data with the parsed fields.                                                                                                                                         | `"text"`                   |
 | LogzioCOMPRESS                | Set to `true` to compress logs before sending them. Set to `false` to send uncompressed logs.                                                                                                                                                                                                      | `false`                    |
 | KinesisStreamBatchSize        | The largest number of records to read from your stream at one time.                                                                                                                                                                                                                                | `100`                      |
@@ -205,7 +205,7 @@ Confirm that you acknowledge that AWS CloudFormation might create IAM resources
 
 Give your logs some time to get from your system to ours, and then open [Open Search Dashboards](https://app.logz.io/#/dashboard/osd).
 
-If you still don't see your logs, see [log shipping troubleshooting]({{site.baseurl}}/user-guide/log-shipping/log-shipping-troubleshooting.html).
+If you still don't see your logs, see [log shipping troubleshooting](/docs/user-guide/log-management/troubleshooting/log-shipping-troubleshooting/).
 
 
 

docs/shipping/AWS/aws-kinesis-firehose.md

@@ -90,7 +90,7 @@ Give your logs some time to get from your system to ours, and then open [Open Se
 
 
 
-If you still don't see your logs, see [log shipping troubleshooting]({{site.baseurl}}/user-guide/log-shipping/log-shipping-troubleshooting.html).
+If you still don't see your logs, see [log shipping troubleshooting](/docs/user-guide/log-management/troubleshooting/log-shipping-troubleshooting/).
 
 
 

docs/shipping/AWS/aws-mq.md

@@ -83,7 +83,7 @@ If you've used the `services` field, you'll have to **wait 6 minutes** before cr
 
 Give your logs some time to get from your system to ours, and then open [Open Search Dashboards](https://app.logz.io/#/dashboard/osd).
 
-If you still don't see your logs, see [log shipping troubleshooting]({{site.baseurl}}/user-guide/log-shipping/log-shipping-troubleshooting.html).
+If you still don't see your logs, see [log shipping troubleshooting](/docs/user-guide/log-management/troubleshooting/log-shipping-troubleshooting/).
 
 ## Metrics
 

docs/shipping/AWS/aws-msk.md

@@ -83,7 +83,7 @@ If you've used the `services` field, you'll have to **wait 6 minutes** before cr
 
 Give your logs some time to get from your system to ours, and then open [Open Search Dashboards](https://app.logz.io/#/dashboard/osd).
 
-If you still don't see your logs, see [log shipping troubleshooting]({{site.baseurl}}/user-guide/log-shipping/log-shipping-troubleshooting.html).
+If you still don't see your logs, see [log shipping troubleshooting](/docs/user-guide/log-management/troubleshooting/log-shipping-troubleshooting/).
 
 ## Metrics
 

docs/shipping/AWS/aws-network-elb.md

@@ -30,7 +30,7 @@ When you set Logz.io to fetch Elastic Load Balancing (ELB) logs, Logz.io will pe
 
 
 **Before you begin, you'll need**:
-`s3:ListBucket` and `s3:GetObject` [permissions](https://docs.logz.io/user-guide/give-aws-access-with-iam-roles/) for the required S3 bucket (one bucket per region)
+`s3:ListBucket` and `s3:GetObject` [permissions](/docs/user-guide/admin/give-aws-access-with-iam-roles) for the required S3 bucket (one bucket per region)
 
 
 
@@ -56,7 +56,7 @@ Log into the app to use the dedicated Logz.io [configuration wizard](https://app
 
 Give your logs some time to get from your system to ours, and then open [Open Search Dashboards](https://app.logz.io/#/dashboard/osd).
 
-If you still don't see your logs, see [log shipping troubleshooting]({{site.baseurl}}/user-guide/log-shipping/log-shipping-troubleshooting.html).
+If you still don't see your logs, see [log shipping troubleshooting](/docs/user-guide/log-management/troubleshooting/log-shipping-troubleshooting/).
 
 
 

docs/shipping/AWS/aws-rds.md

@@ -88,7 +88,7 @@ docker run -d \
 
 Give your logs some time to get from your system to ours, and then open [Open Search Dashboards](https://app.logz.io/#/dashboard/osd).
 
-If you still don't see your logs, see [log shipping troubleshooting]({{site.baseurl}}/user-guide/log-shipping/log-shipping-troubleshooting.html).
+If you still don't see your logs, see [log shipping troubleshooting](/docs/user-guide/log-management/troubleshooting/log-shipping-troubleshooting/).