From 16d1a0b3680f2c30a0eaed32142b91b34410e896 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E2=80=9Cnico-shishkin=E2=80=9D?= <“nicoshishkinatlogz@outlook.com”> Date: Fri, 17 Nov 2023 00:51:36 +0100 Subject: [PATCH] Fixing links --- .../p8s-shipping/dotnet-core-troubleshooting.md | 2 +- ...theus.md => configure-remote-write-prometheus.md} | 0 .../importing-dashboards.md | 4 ++-- .../prometheus-getting-started.md | 12 ++++++------ .../log-correlations/annotations.md | 2 +- .../explore-in-logs-drilldown-links.md | 2 +- .../log-correlations/log-correlations.md | 4 ++-- .../metrics-alert-manager.md | 2 +- .../metrics-overview/highlights.md | 4 ++-- .../Infrastructure-monitoring/variables.md | 2 +- docs/user-guide/k8s-360/overview.md | 6 +++--- docs/user-guide/k8s-360/unified-helm-chart.md | 6 +++--- docs/user-guide/log-management/cold-tier.md | 2 +- .../user-guide/log-management/insights/exceptions.md | 2 +- .../log-management/log-alerts/configure-alert.md | 6 +++--- .../long-term-storage/configure-optimizers.md | 2 +- .../opensearch-best-practices.md | 2 +- .../opensearch-dashboards/opensearch-dashboards.md | 12 ++++++------ .../opensearch-dashboards/opensearch-patterns.md | 2 +- .../troubleshooting/log-shipping-troubleshooting.md | 2 +- docs/user-guide/quick-start.md | 6 +++--- .../telemetry-collector/azure-native-integration.md | 4 ++-- .../telemetry-collector/telemetry-collector.md | 12 ++++++------ static/_redirects | 4 +++- 24 files changed, 52 insertions(+), 50 deletions(-) rename docs/user-guide/Infrastructure-monitoring/introduction-to-prometheus/{configure-remove-write-prometheus.md => configure-remote-write-prometheus.md} (100%) diff --git a/docs/_include/p8s-shipping/dotnet-core-troubleshooting.md b/docs/_include/p8s-shipping/dotnet-core-troubleshooting.md index 34067a70..76c78c9f 100644 --- a/docs/_include/p8s-shipping/dotnet-core-troubleshooting.md +++ b/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://<>:<>` to `http://<>:<>` or from `http://<>:<>` to `https://<>:<>` -* {@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 diff --git a/docs/user-guide/Infrastructure-monitoring/introduction-to-prometheus/configure-remove-write-prometheus.md b/docs/user-guide/Infrastructure-monitoring/introduction-to-prometheus/configure-remote-write-prometheus.md similarity index 100% rename from docs/user-guide/Infrastructure-monitoring/introduction-to-prometheus/configure-remove-write-prometheus.md rename to docs/user-guide/Infrastructure-monitoring/introduction-to-prometheus/configure-remote-write-prometheus.md diff --git a/docs/user-guide/Infrastructure-monitoring/introduction-to-prometheus/importing-dashboards.md b/docs/user-guide/Infrastructure-monitoring/introduction-to-prometheus/importing-dashboards.md index 60e18039..cc13bec3 100644 --- a/docs/user-guide/Infrastructure-monitoring/introduction-to-prometheus/importing-dashboards.md +++ b/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 Manage Accounts **( > Settings > Manage accounts)** 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 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. diff --git a/docs/user-guide/Infrastructure-monitoring/introduction-to-prometheus/prometheus-getting-started.md b/docs/user-guide/Infrastructure-monitoring/introduction-to-prometheus/prometheus-getting-started.md index 1b5f2eb7..e049af28 100644 --- a/docs/user-guide/Infrastructure-monitoring/introduction-to-prometheus/prometheus-getting-started.md +++ b/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). diff --git a/docs/user-guide/Infrastructure-monitoring/log-correlations/annotations.md b/docs/user-guide/Infrastructure-monitoring/log-correlations/annotations.md index cc2ea344..6f82a3fb 100644 --- a/docs/user-guide/Infrastructure-monitoring/log-correlations/annotations.md +++ b/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. diff --git a/docs/user-guide/Infrastructure-monitoring/log-correlations/explore-in-logs-drilldown-links.md b/docs/user-guide/Infrastructure-monitoring/log-correlations/explore-in-logs-drilldown-links.md index ae88ddcb..601144d2 100644 --- a/docs/user-guide/Infrastructure-monitoring/log-correlations/explore-in-logs-drilldown-links.md +++ b/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 diff --git a/docs/user-guide/Infrastructure-monitoring/log-correlations/log-correlations.md b/docs/user-guide/Infrastructure-monitoring/log-correlations/log-correlations.md index 9b6a09f7..cb22703d 100644 --- a/docs/user-guide/Infrastructure-monitoring/log-correlations/log-correlations.md +++ b/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). diff --git a/docs/user-guide/Infrastructure-monitoring/metrics-alert-manager.md b/docs/user-guide/Infrastructure-monitoring/metrics-alert-manager.md index 7f5b38e9..d02aa621 100644 --- a/docs/user-guide/Infrastructure-monitoring/metrics-alert-manager.md +++ b/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 diff --git a/docs/user-guide/Infrastructure-monitoring/metrics-overview/highlights.md b/docs/user-guide/Infrastructure-monitoring/metrics-overview/highlights.md index 7b8a3638..e08e8030 100644 --- a/docs/user-guide/Infrastructure-monitoring/metrics-overview/highlights.md +++ b/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 diff --git a/docs/user-guide/Infrastructure-monitoring/variables.md b/docs/user-guide/Infrastructure-monitoring/variables.md index 50d6af1a..95908736 100644 --- a/docs/user-guide/Infrastructure-monitoring/variables.md +++ b/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/). diff --git a/docs/user-guide/k8s-360/overview.md b/docs/user-guide/k8s-360/overview.md index 52aac0a6..cf941953 100644 --- a/docs/user-guide/k8s-360/overview.md +++ b/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.

Search

diff --git a/docs/user-guide/k8s-360/unified-helm-chart.md b/docs/user-guide/k8s-360/unified-helm-chart.md index 4185a686..8cd7d525 100644 --- a/docs/user-guide/k8s-360/unified-helm-chart.md +++ b/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 | | --- | --- | | `<>` | Replace `<>` with the token of the account you want to ship to. | -| `<>` | Replace `<>` 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. | +| `<>` | Replace `<>` 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. | | `<>` | Your [metrics shipping token](https://app.logz.io/#/dashboard/settings/manage-tokens/data-shipping). | | `<>` | The name for the environment's metrics, to easily identify the metrics for each environment. | | `<>` | 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 \ diff --git a/docs/user-guide/log-management/cold-tier.md b/docs/user-guide/log-management/cold-tier.md index ae2cdb7a..26285fb7 100644 --- a/docs/user-guide/log-management/cold-tier.md +++ b/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. diff --git a/docs/user-guide/log-management/insights/exceptions.md b/docs/user-guide/log-management/insights/exceptions.md index 653fdfad..248e7ba8 100644 --- a/docs/user-guide/log-management/insights/exceptions.md +++ b/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"` diff --git a/docs/user-guide/log-management/log-alerts/configure-alert.md b/docs/user-guide/log-management/log-alerts/configure-alert.md index 13a8e95a..ff192f54 100644 --- a/docs/user-guide/log-management/log-alerts/configure-alert.md +++ b/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. diff --git a/docs/user-guide/log-management/long-term-storage/configure-optimizers.md b/docs/user-guide/log-management/long-term-storage/configure-optimizers.md index 2aa4c450..5a40ee66 100644 --- a/docs/user-guide/log-management/long-term-storage/configure-optimizers.md +++ b/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: diff --git a/docs/user-guide/log-management/opensearch-dashboards/opensearch-best-practices.md b/docs/user-guide/log-management/opensearch-dashboards/opensearch-best-practices.md index 7d07b578..9e02eb7b 100644 --- a/docs/user-guide/log-management/opensearch-dashboards/opensearch-best-practices.md +++ b/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 diff --git a/docs/user-guide/log-management/opensearch-dashboards/opensearch-dashboards.md b/docs/user-guide/log-management/opensearch-dashboards/opensearch-dashboards.md index acccb2cf..3faaf871 100644 --- a/docs/user-guide/log-management/opensearch-dashboards/opensearch-dashboards.md +++ b/docs/user-guide/log-management/opensearch-dashboards/opensearch-dashboards.md @@ -19,13 +19,13 @@ OpenSearch Dashboards is designed to help you investigate massive volumes of dat #### 1. Select Account -First, decide which accounts you want to search. Managing your accounts is the first step to successful logging. You can create sub accounts to separate data by environment, microservice, team, and more. [Learn more about account management and sub accounts](/user-guide/accounts/manage-the-main-account-and-sub-accounts.html). +First, decide which accounts you want to search. Managing your accounts is the first step to successful logging. You can create sub accounts to separate data by environment, microservice, team, and more. [Learn more about account management and sub accounts](../../admin/logzio-accounts/manage-the-main-account-and-sub-accounts/). #### 2. Apply Filters OpenSearch Dashboards filters offer the most convenient, powerful, and flexible method for querying logs. -Filters can be used on any mapped fields and can take any number of forms: filter for field exists or does not exist, filter for a field with an exact value match or a field that contains a value among the results, and more. [Learn more about OSD mapping](/user-guide/logs/mapping/). +Filters can be used on any mapped fields and can take any number of forms: filter for field exists or does not exist, filter for a field with an exact value match or a field that contains a value among the results, and more. [Learn more about OSD mapping](../../data-hub/field-mapping/). One advantage of OpenSearch filters is that they provide guidance that is specific to your dataset. When OpenSearch maps your data to fields, it also determines which filtering options are relevant. When you add filters, only relevant options appear in the dropdown menus. @@ -56,9 +56,9 @@ The logs returned by your search are your results - aka "hits". Depending on the To expand a log, click it and review the complete log mapped into field:value pairs. You can also switch to the raw JSON. -* **Patterns** - Logz.io groups your logs using advanced clustering techniques to help you identify similar logs by groups, reducing the amount of logs to review. Patterns also help to surface issues and errors that might otherwise go unnoticed. [Learn more](/user-guide/logs/log-patterns.html). +* **Patterns** - Logz.io groups your logs using advanced clustering techniques to help you identify similar logs by groups, reducing the amount of logs to review. Patterns also help to surface issues and errors that might otherwise go unnoticed. [Learn more](../../log-management/opensearch-dashboards/opensearch-patterns/). -* **Exceptions** - Logz.io Insights Engine scans your logs for application errors and warnings to help you identify issues that require your attention. [Learn more](/user-guide/insights/exceptions/). +* **Exceptions** - Logz.io Insights Engine scans your logs for application errors and warnings to help you identify issues that require your attention. [Learn more](../../log-management/insights/exceptions/). #### 6. Take action following your results @@ -68,7 +68,7 @@ If you click the **Inspect** function, you can view the query as sent to OpenSea Once you've refined a query to the point that it returns exactly what you are looking for, you can be proactive in any number of ways: -* Create an **alert** to trigger automatically and send out notifications to your preferred endpoints. [Learn how to configure an alert](/user-guide/alerts/configure-an-alert.html). +* Create an **alert** to trigger automatically and send out notifications to your preferred endpoints. [Learn how to configure an alert](../../log-management/log-alerts/configure-alert/). * **Save** the search to display it in visualizations and dashboards or to load it in the future. * **Share** results with colleagues or external stakeholders. * **Export** results to a spreadsheet. @@ -76,5 +76,5 @@ Once you've refined a query to the point that it returns exactly what you are lo ###### Additional resources -* [OpenSearch Dashboards best practices](/user-guide/logs/best-practices.html) +* [OpenSearch Dashboards best practices](../../log-management/opensearch-dashboards/opensearch-best-practices/) * [Create and run advanced searches in OpenSearch Dashboards](https://logz.io/blog/kibana-advanced/) \ No newline at end of file diff --git a/docs/user-guide/log-management/opensearch-dashboards/opensearch-patterns.md b/docs/user-guide/log-management/opensearch-dashboards/opensearch-patterns.md index dea08e13..a4c635df 100644 --- a/docs/user-guide/log-management/opensearch-dashboards/opensearch-patterns.md +++ b/docs/user-guide/log-management/opensearch-dashboards/opensearch-patterns.md @@ -74,7 +74,7 @@ Variables come in 2 forms: ### Log pattern limitations -**A. **Unidentified size: Estimated size calculations depend on a enabling the log size field in the [Manage accounts page](https://app.logz.io/#/dashboard/settings/manage-accounts). [Learn more](/user-guide/accounts/manage-account-usage.html#enabling-account-utilization-metrics-and-log-size) +**A. **Unidentified size: Estimated size calculations depend on a enabling the log size field in the [Manage accounts page](https://app.logz.io/#/dashboard/settings/manage-accounts). [Learn more](../../admin/account-volume-optimization/manage-account-usage/#enabling-account-utilization-metrics-and-log-size) **B.** Unidentified patterns: Logs that don't fall under any pattern are grouped under the unidentified pattern category. diff --git a/docs/user-guide/log-management/troubleshooting/log-shipping-troubleshooting.md b/docs/user-guide/log-management/troubleshooting/log-shipping-troubleshooting.md index f5c1efcc..f906f9dd 100644 --- a/docs/user-guide/log-management/troubleshooting/log-shipping-troubleshooting.md +++ b/docs/user-guide/log-management/troubleshooting/log-shipping-troubleshooting.md @@ -97,7 +97,7 @@ your machine is having trouble connecting to the Logz.io listener. Confirm that your firewall and network settings allow communication with the right outbound port -and the Logz.io [listener IP addresses](/user-guide/log-shipping/listener-ip-addresses.html) +and the Logz.io [listener IP addresses](../../admin/hosting-regions/listener-ip-addresses/) for your region. ## Check that log shipping configuration is set to the right account token diff --git a/docs/user-guide/quick-start.md b/docs/user-guide/quick-start.md index dd7e3b27..7094f19c 100644 --- a/docs/user-guide/quick-start.md +++ b/docs/user-guide/quick-start.md @@ -15,7 +15,7 @@ Logz.io is an end-to-end cloud monitoring service built for scale. It’s the be One unified SaaS platform to collect and analyze logs, metrics, and traces, combined with human-powered AI/ML features to improve troubleshooting, reduce response time and help you manage costs. -Whether you are a new user or looking for a refresher on Logz.io, you are invited to join one of our engineers for a **[training session on the Logz.io platform](https://docs.logz.io/training/)**! +Whether you are a new user or looking for a refresher on Logz.io, you are invited to join one of our engineers for a **[training session on the Logz.io platform](https://logz.io/training/)**! ## Send your data to Logz.io @@ -38,7 +38,7 @@ If you prefer to send your data manually, Logz.io offers numerous methods to do |[JSON uploads](https://app.logz.io/#/dashboard/send-your-data/log-sources/json-uploads)|[Google Kubernetes Engine over OpenTelemetry](https://app.logz.io/#/dashboard/send-your-data/prometheus-sources/otel-metrics-gke-helm)|[Kubernetes](https://app.logz.io/#/dashboard/send-your-data/tracing-sources/otel-traces-helm)|[CloudTrail](https://app.logz.io/#/dashboard/send-your-data/security-sources/cloudtrail) |[Docker container](https://app.logz.io/#/dashboard/send-your-data/log-sources/docker)|[Amazon EC2](https://app.logz.io/#/dashboard/send-your-data/prometheus-sources/aws-ec2-prometheus)|[Go instrumentation](https://app.logz.io/#/dashboard/send-your-data/tracing-sources/go-otel)|[auditd](https://app.logz.io/#/dashboard/send-your-data/security-sources/auditd) | -Browse the complete list of available shipping methods [here](https://docs.logz.io/shipping/). +Browse the complete list of available shipping methods [here](https://docs.logz.io/docs/category/send-your-data). To learn more about shipping your data, check out **Shipping Log Data to Logz.io**: @@ -131,7 +131,7 @@ Logz.io **[Cloud SIEM](https://app.logz.io/#/dashboard/security/summary)** (Secu Here are some popular Cloud SIEM resources to help you get started: -* **[Cloud SIEM quick start guide](https://docs.logz.io/user-guide/cloud-siem/quick-guide.html)** +* **[Cloud SIEM quick start guide](https://docs.logz.io/docs/category/cloud-siem-quick-start-guide)** * **[Investigate security events](https://docs.logz.io/user-guide/cloud-siem/security-events.html)** * **[Threat Intelligence feeds](https://docs.logz.io/user-guide/cloud-siem/threat-intelligence.html)** * **[Configure a security rule](https://docs.logz.io/user-guide/cloud-siem/manage-security-rules.html)** diff --git a/docs/user-guide/telemetry-collector/azure-native-integration.md b/docs/user-guide/telemetry-collector/azure-native-integration.md index ee61ee72..26619aea 100644 --- a/docs/user-guide/telemetry-collector/azure-native-integration.md +++ b/docs/user-guide/telemetry-collector/azure-native-integration.md @@ -84,7 +84,7 @@ Once you connect your Azure Native Integration with Logz.io, it'll have access t To connect your Azure Native Integration with Logz.io you'll need to send the following information: -* **Client secret value** - that you created and copied in the [Create a certificate](/user-guide/cloud-fetcher.html#create-a-certificate) section. +* **Client secret value** - that you created and copied in the [Create a certificate](./azure-native-integration/#create-a-certificate) section. Navigate to App registration and click on the app you created. There, you'll be able to find the following information: @@ -119,7 +119,7 @@ Take the credentials you've copied from your Azure app and enter the required va * **Tenant ID** - Your Azure app's directory ID * **Client ID** - Your Azure app's application ID -* **Client Secret** - The value you've copied in the [Create a certificate](/user-guide/cloud-fetcher.html#create-a-certificate) section +* **Client Secret** - The value you've copied in the [Create a certificate](./azure-native-integration/#create-a-certificate) section * **Subscription** - Your Azure app's subscription ID * *Optional* - **Resource group name** - The name of the group that's associated with the Azure app you created * _Optional_ - **Tags** - You can add tags associated with the sent data for easier analysis and identification diff --git a/docs/user-guide/telemetry-collector/telemetry-collector.md b/docs/user-guide/telemetry-collector/telemetry-collector.md index e2adea62..daa4dc57 100644 --- a/docs/user-guide/telemetry-collector/telemetry-collector.md +++ b/docs/user-guide/telemetry-collector/telemetry-collector.md @@ -30,12 +30,12 @@ If you're interested in sending your data through a different source, you can us ## Getting started with the Telemetry Collector: -* [Send **AWS** data with Telemetry Collector](/user-guide/log-shipping/telemetry-collector-aws.html) - * [Manage an AWS Telemetry Collector](/user-guide/log-shipping/telemetry-collector-aws.html#how-to-remove-a-telemetry-collector) -* [Send **Kubernetes** data with Telemetry Collector](/user-guide/log-shipping/telemetry-collector-k8s.html) - * [Manage a Kubernetes Telemetry Collector](/user-guide/log-shipping/telemetry-collector-k8s.html#how-to-remove-a-telemetry-collector) -* [Send **Localhost** data with Telemetry Collector](/user-guide/log-shipping/telemetry-collector-localhost.html) - * [Manage a Localhost Telemetry Collector](/user-guide/log-shipping/telemetry-collector-localhost.html#manage-and-remove-a-telemetry-collector) +* [Send **AWS** data with Telemetry Collector](./telemetry-collector-aws/) + * [Manage an AWS Telemetry Collector](./telemetry-collector-aws.html#how-to-remove-a-telemetry-collector) +* [Send **Kubernetes** data with Telemetry Collector](./telemetry-collector-k8s.html) + * [Manage a Kubernetes Telemetry Collector](./telemetry-collector-k8s.html#how-to-remove-a-telemetry-collector) +* [Send **Localhost** data with Telemetry Collector](./telemetry-collector-localhost.html) + * [Manage a Localhost Telemetry Collector](./telemetry-collector-localhost.html#manage-and-remove-a-telemetry-collector) ###### Additional resources diff --git a/static/_redirects b/static/_redirects index 1a56d1f3..6b9967df 100644 --- a/static/_redirects +++ b/static/_redirects @@ -554,4 +554,6 @@ /shipping/log-sources/vpc.html /docs/shipping/Network/VPC-network /shipping/log-sources/windows.html /docs/shipping/Operating-Systems/Windows /api https://logz-docs-api.netlify.app/api -/shipping/prometheus-sources/aws-cloudformation.html /docs/shipping/AWS/aws-cloudformation \ No newline at end of file +/shipping/prometheus-sources/aws-cloudformation.html /docs/shipping/AWS/aws-cloudformation +/shipping/ /docs/category/send-your-data +/docs/category/cloud-siem-quick-start-guide /docs/category/cloud-siem-quick-start-guide \ No newline at end of file