Merge pull request #270 from logzio/brokenlinksfixing

Fixing links

docs/_include/p8s-shipping/dotnet-core-troubleshooting.md

@@ -52,7 +52,7 @@ Your Logz.io listener may not be using the correct endpoint.
 Change the endpoint of your listener from `https://<<LISTENER-HOST>>:<<PORT>>` to `http://<<LISTENER-HOST>>:<<PORT>>` or from `http://<<LISTENER-HOST>>:<<PORT>>` to `https://<<LISTENER-HOST>>:<<PORT>>`
 
 
-* {@include: ../log-shipping/listener-var.html}
+* Use the listener URL specific to the region where your Logz.io account is hosted. [Click to look up your listener URL](https://docs.logz.io/user-guide/accounts/account-region.html#available-regions). The required port depends whether HTTP or HTTPS is used: HTTP = 8070, HTTPS = 8071.
 
 
 ##### Possible cause - Kubernetes environment - prometheus.io/scrape is not set

docs/user-guide/Infrastructure-monitoring/introduction-to-prometheus/importing-dashboards.md

@@ -74,7 +74,7 @@ For the dashboard import to work smoothly, you'll need to change the name of the
 Your Metrics account information is located in the <a href ="https://app.logz.io/#/dashboard/settings/manage-accounts" target="_blank">Manage Accounts **(<i class="li li-gear"></i> > Settings > Manage accounts)**</a> page of your Operations workspace. ![Account settings navigation](https://dytvr9ot2sszz.cloudfront.net/logz-docs/grafana/p8s-account-token00.png)
 
 
-For the record, notification endpoints and dashboard annotations are not imported: You'll need to recreate them in Logz.io.  See [Notification endpoints](/user-guide/integrations/endpoints.html) and [Annotations](/user-guide/infrastructure-monitoring/annotations/)for more information.
+For the record, notification endpoints and dashboard annotations are not imported: You'll need to recreate them in Logz.io.  See [Notification endpoints](../integrations/notification-endpoints/endpoints/) and [Annotations](../log-correlations/annotations/)for more information.
 
 ### Importing individual dashboards
 
@@ -93,7 +93,7 @@ In the left navigation pane, click <i class="fas fa-plus"></i> and select **Impo
 
   - To import your existing Prometheus dashboards, first export the relevant dashboards as JSON files, then click **Upload json file** and select the files to upload.
 
-    For related information see [Upload JSON logs]({{site.baseurl}}/shipping/log-sources/json-uploads).
+    For related information see [Upload JSON logs](../../../shipping/code/json).
   - To import dashboards from Grafana.com, enter the relevant dashboard URL or ID in **Import via grafana.com** and **Load** them.
 
 

docs/user-guide/Infrastructure-monitoring/introduction-to-prometheus/prometheus-getting-started.md

@@ -27,13 +27,13 @@ For the trial program, your incoming raw data has a 30-day retention period.
 
 Once your metrics are flowing, import your existing Prometheus and Grafana dashboards to Logz.io Infrastructure Monitoring as JSON files.
 
-For the record, notification endpoints and dashboard annotations are not imported: You'll need to recreate them in Logz.io.  See [Notification endpoints](/user-guide/integrations/endpoints.html) and [Annotations](/user-guide/infrastructure-monitoring/annotations/) for more information.
+For the record, notification endpoints and dashboard annotations are not imported: You'll need to recreate them in Logz.io.  See [Notification endpoints](../../integrations/notification-endpoints/endpoints/) and [Annotations](../log-correlations/annotations/) for more information.
 
-1. [Configure Remote Write](/user-guide/infrastructure-monitoring/prometheus-remote-write#configuring-remote-write-to-logzio).
-1. [Import dashboards](/user-guide/infrastructure-monitoring/prometheus-importing-dashbds).
-1. [Configure notification endpoints](/user-guide/integrations/endpoints.html).
-1. [Recreate your dashboard annotations](/user-guide/infrastructure-monitoring/annotations/).
-1. [Explore your Prometheus metrics](/user-guide/infrastructure-monitoring/metrics-explore-prometheus/).
+1. [Configure Remote Write](./configure-remote-write-prometheus#configuring-remote-write-to-logzio).
+1. [Import dashboards](./importing-dashboards).
+1. [Configure notification endpoints](../../integrations/notification-endpoints/endpoints/).
+1. [Recreate your dashboard annotations](../log-correlations/annotations/).
+1. [Explore your Prometheus metrics](./explore-metrics-prometheus).
 
 
 

docs/user-guide/Infrastructure-monitoring/log-correlations/annotations.md

@@ -41,7 +41,7 @@ Go to the dashboard's settings:
 You'll be using a OpenSearch Dashboards search query to select the logs you want to mark on your dashboard. They will appear as vertical markers on the dashboard's timeline to indicate when they were sent.
 
 Type in an _OpenSearch Dashboards_ query in Lucene syntax.
-It's best if you double-check your query results in [OpenSearch Dashboards](/user-guide/logs/) to make sure it is specific enough.
+It's best if you double-check your query results in [OpenSearch Dashboards](../../log-management/opensearch-dashboards/) to make sure it is specific enough.
 
 You can use Metrics interface variables, on condition that the value of the variable actually appears in the target log. For example, the query `logtype:configuration AND pod.name:$pod` would work assuming the fields `logtype` and `pod.name` exist in the log.
 

docs/user-guide/Infrastructure-monitoring/log-correlations/explore-in-logs-drilldown-links.md

@@ -16,7 +16,7 @@ Drilldown links help you go straight to the related logs whenever you identify a
 
 **Before you begin, you'll need**:
 Edit-permissions to the dashboard. If you don't, duplicate the dashboard first.
-It's also a good idea to have [variables configured](/user-guide/infrastructure-monitoring/configure-metrics-drilldown-links) for your dashboard. Variables aren't required, but they are highly recommended.
+It's also a good idea to have [variables configured](../variables) for your dashboard. Variables aren't required, but they are highly recommended.
 
 
 ### Add a new panel

docs/user-guide/Infrastructure-monitoring/log-correlations/log-correlations.md

@@ -8,6 +8,6 @@ sidebar_position: 1
 
 Your Metrics account offers several ways to correlate data between your Logz.io Infrastructure Monitoring and Log Management accounts:
 
-1. Annotations can mark events on your Metrics dashboards based on data from a logging account. [Learn more about Annotations](/user-guide/infrastructure-monitoring/annotations/).
+1. Annotations can mark events on your Metrics dashboards based on data from a logging account. [Learn more about Annotations](./annotations/).
 
-2. Drill down links offer a quick way to get from an Infrastructure Monitoring metrics visualization to the relevant logs in Log Management. [Learn more about Explore in OpenSearch Dashboards links](/user-guide/infrastructure-monitoring/explore-in-logs-drilldown-links).
+2. Drill down links offer a quick way to get from an Infrastructure Monitoring metrics visualization to the relevant logs in Log Management. [Learn more about Explore in OpenSearch Dashboards links](./explore-in-logs-drilldown-links).

docs/user-guide/Infrastructure-monitoring/metrics-alert-manager.md

@@ -96,7 +96,7 @@ In the second step, you'll need to build the query for this alert. You can use t
 
 ![Metric browser](https://dytvr9ot2sszz.cloudfront.net/logz-docs/grafana/metric-browser-alert.png)
 
-Complete the alert by following the steps to [define your alert condition](/user-guide/infrastructure-monitoring/alerts.html#define-alert-conditions), and [add details to your alert](/user-guide/infrastructure-monitoring/alerts.html#add-details-for-your-alert). 
+Complete the alert by following the steps to [define your alert condition](#define-alert-conditions), and [add details to your alert](#add-details-for-your-alert). 
 
 
 ### 1. Define your notification endpoint

docs/user-guide/Infrastructure-monitoring/metrics-overview/highlights.md

@@ -36,9 +36,9 @@ Logz.io’s Metrics platform is pre-loaded with dozens of dashboards to help you
 
 After configuring how to stream your data to Logz.io, you can select any relevant dashboard from the list and select the data source. Each dashboard is preconfigured to match the particular data type it's named after. These dashboards are production-ready: You don't have to do any customizations, and you don't need to have previous experience to set them up. 
 
-The metrics dashboards are designed by Logz.io specialists so that you can get up-and-running in a matter of minutes. [Learn how to select your first dashboard](/user-guide/infrastructure-monitoring/getting-started).
+The metrics dashboards are designed by Logz.io specialists so that you can get up-and-running in a matter of minutes. 
 
-Once you’re ready to move to the next level, you can duplicate any of the preconfigured dashboards to add your own panels and changes, or create entirely new dashboards of your own. [Learn how to add a new dashboard](/user-guide/infrastructure-monitoring/configure-metrics-drilldown-links).
+Once you’re ready to move to the next level, you can duplicate any of the preconfigured dashboards to add your own panels and changes, or create entirely new dashboards of your own. [Learn how to add a new dashboard](../variables).
 
 ### Maintain data integrity over an extended time
 

docs/user-guide/Infrastructure-monitoring/variables.md

@@ -59,4 +59,4 @@ You're now ready to use the variable in your new dashboard.
 ###### Additional resources
 
 * To learn more about Prometheus and PromQL, check out our [examples and best practices guide](https://docs.logz.io/user-guide/infrastructure-monitoring/prometheus-promql-queries.html). 
-* Looking to configure **Explore in OpenSearch Dashboards** drilldown links? [Read our guide](/user-guide/infrastructure-monitoring/explore-in-logs-drilldown-links.html).
+* Looking to configure **Explore in OpenSearch Dashboards** drilldown links? [Read our guide](./log-correlations/explore-in-logs-drilldown-links/).

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

@@ -18,7 +18,7 @@ The platform utilizes Kubernetes' numerous advantages for R&D and dev teams, all
 
 To activate your Kubernetes 360 dashboard, connect your Kubernetes data quickly and easily through Logz.io's **[Telemetry Collector](https://app.logz.io/#/dashboard/send-your-data/agent/new)**.
 
-If you already have Kubernetes 360 data in your Logz.io account or prefer connecting Kubernetes manually, follow our **[Kubernetes 360 Prerequisite](/user-guide/k360/kubernetes-360-pre.html)** guide.
+If you already have Kubernetes 360 data in your Logz.io account or prefer connecting Kubernetes manually, follow our **[Kubernetes 360 Prerequisite](./kubernetes-360-pre/)** guide.
 
 Once everything is up and running, you can use your Kubernetes 360 application.
 
@@ -32,7 +32,7 @@ Once everything is up and running, you can use your Kubernetes 360 application.
 
 ![deployments card](https://dytvr9ot2sszz.cloudfront.net/logz-docs/k360/focus-on-nodes.png) -->
 
-You can dive deeper into each card by clicking on it and opening the **[Quick view](/user-guide/k360/overview.html#quick-view)** menu.
+You can dive deeper into each card by clicking on it and opening the **[Quick view](#quick-view)** menu.
 
 ## Customize your application
 
@@ -61,7 +61,7 @@ When switching between views, the main cards change to represent the different r
 
 ![deployments card](https://dytvr9ot2sszz.cloudfront.net/logz-docs/k360/node-view-jul-.png)
 
-You can dive deeper into each card by clicking on it and opening the **[Quick view](/user-guide/k360/overview.html#quick-view)** menu.
+You can dive deeper into each card by clicking on it and opening the **[Quick view](#quick-view)** menu.
 
 <h4 id="#search">Search</h4>
 

docs/user-guide/k8s-360/unified-helm-chart.md

@@ -14,7 +14,7 @@ Please be aware that this project is presently in its beta stage, and as such, i
 :::
 
 :::tip
-To get the most out of Kubernetes 360, try out dedicated [dashboard](/user-guide/k360/kubernetes-360-pre.html). Log in to your Logz.io account and navigate to the current instructions page [inside the Logz.io app](https://app.logz.io/#/dashboard/send-your-data/collection?tag=all&collection=prometheus-sources). Install the pre-built dashboard to enhance the observability of your metrics. To view the metrics on the main dashboard, log in to your Logz.io Metrics account, and open the [Logz.io Metrics tab](https://app.logz.io/#/dashboard/metrics).
+To get the most out of Kubernetes 360, try out dedicated [dashboard](./kubernetes-360-pre). Log in to your Logz.io account and navigate to the current instructions page [inside the Logz.io app](https://app.logz.io/#/dashboard/send-your-data/collection?tag=all&collection=prometheus-sources). Install the pre-built dashboard to enhance the observability of your metrics. To view the metrics on the main dashboard, log in to your Logz.io Metrics account, and open the [Logz.io Metrics tab](https://app.logz.io/#/dashboard/metrics).
 :::
 
 
@@ -69,7 +69,7 @@ logzio-monitoring logzio-helm/logzio-monitoring
 | Parameter | Description |
 | --- | --- |
 | `<<LOG-SHIPPING-TOKEN>>` | Replace `<<LOG-SHIPPING-TOKEN>>` with the token of the account you want to ship to. |
-| `<<LISTENER-HOST>>` | Replace `<<LISTENER-HOST>>` with the host [for your region](/user-guide/accounts/account-region.html#available-regions). For example, `listener.logz.io` if your account is hosted on AWS US East, or `listener-nl.logz.io` if hosted on Azure West Europe. The required port depends whether HTTP or HTTPS is used: HTTP = 8070, HTTPS = 8071. |
+| `<<LISTENER-HOST>>` | Replace `<<LISTENER-HOST>>` with the host [for your region](../../admin/hosting-regions/account-region/#available-regions). For example, `listener.logz.io` if your account is hosted on AWS US East, or `listener-nl.logz.io` if hosted on Azure West Europe. The required port depends whether HTTP or HTTPS is used: HTTP = 8070, HTTPS = 8071. |
 | `<<PROMETHEUS-METRICS-SHIPPING-TOKEN>>` | Your [metrics shipping token](https://app.logz.io/#/dashboard/settings/manage-tokens/data-shipping). |
 | `<<P8S-LOGZIO-NAME>>` | The name for the environment's metrics, to easily identify the metrics for each environment. |
 | `<<ENV-ID>>` | The name for your environment's identifier, to easily identify the telemetry data for each environment. |
@@ -148,7 +148,7 @@ For instance, if there is a parameter called `someField` in the `logzio-telemetr
 
 #### Sending telemetry data from eks on fargate
 
-To ship logs from pods running on Fargate, set the `fargateLogRouter.enabled` value to `true`. Doing so will deploy a dedicated `aws-observability` namespace and a `configmap` for the Fargate log router. For more information on EKS Fargate logging, please refer to the [official AWS documentation]((https://docs.aws.amazon.com/eks/latest/userguide/fargate-logging.html).
+To ship logs from pods running on Fargate, set the `fargateLogRouter.enabled` value to `true`. Doing so will deploy a dedicated `aws-observability` namespace and a `configmap` for the Fargate log router. For more information on EKS Fargate logging, please refer to the [official AWS documentation](https://docs.aws.amazon.com/eks/latest/userguide/fargate-logging.html).
 
 ```shell
 helm install -n monitoring \

docs/user-guide/log-management/cold-tier.md

@@ -113,7 +113,7 @@ Re-ingesting logs process failed since you've exceeded your account's limit. Thi
 #### Suggested remedy
 
 
-If your account has a [flexible volume](/user-guide/accounts/flexible-volume.html), you can allocate available GB from one of the existing sub accounts.
+If your account has a [flexible volume](../../admin/logzio-accounts/flexible-volume/), you can allocate available GB from one of the existing sub accounts.
 
 Otherwise, you can update your plan and adjust your daily volume on the [Plan and usage](https://app.logz.io/#/dashboard/settings/plan-and-billing/plan) page.
 

docs/user-guide/log-management/insights/exceptions.md

@@ -72,7 +72,7 @@ Logz.io tracks the recurrence of each exception over time, and retains its **Fir
 
 You can set an alert to get a digest, including your exceptions insights.
 
-To do so, you'll need to [**configure an alert**](/user-guide/alerts/configure-an-alert.html) with the following query:
+To do so, you'll need to [**configure an alert**](../../log-management/log-alerts/configure-alert/) with the following query:
 
 `_exists_: _logzio_logceptions OR _exists_:"_logzio_insights"`
 

docs/user-guide/log-management/log-alerts/configure-alert.md

@@ -25,7 +25,7 @@ Your alert name can contain letters, numbers, spaces, and special characters. It
 
 Next, set the search components. This determines which logs to look for and in which accounts.
 
-If you intend to create a correlated alert with 2 queries, see [this guide](/user-guide/alerts/correlated-alert/).
+If you intend to create a correlated alert with 2 queries, see [this guide](../../log-management/log-alerts/correlated-alert/).
 
 
 ![Alert group by settings](https://dytvr9ot2sszz.cloudfront.net/logz-docs/alerts/alert-filter-component.gif)
@@ -162,9 +162,9 @@ To use an **email** as your endpoint, you need to type the email in the Recipien
 
 
 If you need help adding a new endpoint,
-see [_Notification endpoints_](/user-guide/integrations/endpoints.html).
+see [_Notification endpoints_](../../integrations/notification-endpoints/endpoints/).
 
-Set a time period between notifications to limit how frequently recipients are notified. Logz.io will continue to log triggered alerts without sending notifications, and you can [review these alerts](/user-guide/alerts/event-management.html) directly from the Logz.io platform at any time.
+Set a time period between notifications to limit how frequently recipients are notified. Logz.io will continue to log triggered alerts without sending notifications, and you can [review these alerts](../../log-management/log-alerts/alerts-event-management/) directly from the Logz.io platform at any time.
 
 :::note
 The system combines the **Trigger if** time interval with the **Wait time** interval to calculate how long it should snooze notifications and chooses the more extended time duration available. For example, if your trigger condition is 1 hour and the wait time is 15 Minutes, the system will snooze notifications for 1 hour before triggering them again.

docs/user-guide/log-management/long-term-storage/configure-optimizers.md

@@ -17,7 +17,7 @@ Once a log is pulled to your Logz.io account, it takes up to **2 hours** until i
 :::
 
 
-If you want help updating an existing optimizer, you can [skip the first part of this page](/user-guide/optimizers/configure-optimizers.html#to-configure-an-optimizer).
+If you want help updating an existing optimizer, you can [skip the first part of this page](../../admin/logzio-accounts/manage-the-main-account-and-sub-accounts/#timeless).
 
 ### Create an optimizer:
 

docs/user-guide/log-management/opensearch-dashboards/opensearch-best-practices.md

@@ -161,7 +161,7 @@ For example, if a `metadata` field is assigned as an `Object` in your production
 
 You can also send data from each environment to a dedicated sub account to monitor them individually.
 
-Learn more about [creating and managing sub accounts](/user-guide/accounts/manage-the-main-account-and-sub-accounts.html#add-and-manage-a-log-management-sub-account) and about [field mapping](/user-guide/logs/mapping/) in your account.
+Learn more about [creating and managing sub accounts](../../admin/logzio-accounts/manage-the-main-account-and-sub-accounts/#add-and-manage-a-log-management-sub-account) and about [field mapping](../../data-hub/field-mapping/) in your account.
 
 ## Additional resources