diff --git a/_source/getting-started.md b/_source/getting-started.md index 8a6825bfb..c0d34f645 100644 --- a/_source/getting-started.md +++ b/_source/getting-started.md @@ -44,16 +44,16 @@ Logz.io provides various tools, integrations, and methods to send data and monit The fastest and most seamless way to send your data is through our **Telemetry Collector**. It lets you easily configure your data-sending process by executing a single line of code, providing a complete observability platform to monitor and improve your logs, metrics, and traces. -[**Get started with Telemetry Collector**](https://app.logz.io/#/dashboard/send-your-data/agent/new). +[**Get started with Telemetry Collector**](https://app.logz.io/#/dashboard/integrations/collectors). If you prefer to send your data manually, Logz.io offers numerous methods to do so, and here are some of the more popular ones based on what you’d like to monitor: |**Logs**|**Metrics**|**Traces**|**Cloud SIEM** -|[Filebeat](https://app.logz.io/#/dashboard/send-your-data/log-sources/filebeat)|[.NET](https://app.logz.io/#/dashboard/send-your-data/prometheus-sources/dotnet-custom)|[Jaeger installation](https://app.logz.io/#/dashboard/send-your-data/tracing-sources/jaeger_collector)|[Cloudflare](https://app.logz.io/#/dashboard/send-your-data/security-sources/cloudflare) -|[S3 Bucket](https://app.logz.io/#/dashboard/send-your-data/log-sources/s3-bucket)|[Prometheus](https://app.logz.io/#/dashboard/send-your-data/prometheus-sources/prometheus-remote-write_shipping)|[OpenTelemetry installation](https://app.logz.io/#/dashboard/send-your-data/tracing-sources/opentelemetry)|[NGINX](https://app.logz.io/#/dashboard/send-your-data/security-sources/nginx) -|[cURL](https://app.logz.io/#/dashboard/send-your-data/log-sources/curl)|[Azure Kubernetes Service](https://app.logz.io/#/dashboard/send-your-data/prometheus-sources/otel-metrics-aks-helm)|[Docker](https://app.logz.io/#/dashboard/send-your-data/tracing-sources/docker-otel)|[Active directory](https://app.logz.io/#/dashboard/send-your-data/security-sources/active-directory-winserver) -|[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) +|[Filebeat](https://app.logz.io/#/dashboard/send-your-data/log-sources/filebeat)|[.NET](https://app.logz.io/#/dashboard/send-your-data/prometheus-sources/dotnet-custom)|[Jaeger installation](https://app.logz.io/#/dashboard/integrations/Jaeger-data)|[Cloudflare](https://app.logz.io/#/dashboard/send-your-data/security-sources/cloudflare) +|[S3 Bucket](https://app.logz.io/#/dashboard/send-your-data/log-sources/s3-bucket)|[Prometheus](https://app.logz.io/#/dashboard/send-your-data/prometheus-sources/prometheus-remote-write_shipping)|[OpenTelemetry installation](https://app.logz.io/#/dashboard/integrations/OpenTelemetry-data)|[NGINX](https://app.logz.io/#/dashboard/send-your-data/security-sources/nginx) +|[cURL](https://app.logz.io/#/dashboard/send-your-data/log-sources/curl)|[Azure Kubernetes Service](https://app.logz.io/#/dashboard/send-your-data/prometheus-sources/otel-metrics-aks-helm)|[Docker](https://app.logz.io/#/dashboard/integrations/Docker)|[Active directory](https://app.logz.io/#/dashboard/send-your-data/security-sources/active-directory-winserver) +|[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/integrations/Kubernetes)|[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/integrations/GO)|[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/). diff --git a/_source/logzio_collections/_tracing-sources/span-metrics.md b/_source/logzio_collections/_tracing-sources/span-metrics.md index e93497898..2bfd979b9 100644 --- a/_source/logzio_collections/_tracing-sources/span-metrics.md +++ b/_source/logzio_collections/_tracing-sources/span-metrics.md @@ -36,7 +36,7 @@ order: 330 ### Architecture overview -This integration is based on OpenTelemetry. It works as an add-on to existing OpenTelemetry installations. If you need to set up OpenTelemetry first, refer to our documentation on [OpenTelemetry](https://app.logz.io/#/dashboard/send-your-data/tracing-sources/opentelemetry). +This integration is based on OpenTelemetry. It works as an add-on to existing OpenTelemetry installations. If you need to set up OpenTelemetry first, refer to our documentation on [OpenTelemetry](https://app.logz.io/#/dashboard/integrations/OpenTelemetry-data). The integration includes: diff --git a/_source/user-guide/distributed-tracing/getting-started-tracing.md b/_source/user-guide/distributed-tracing/getting-started-tracing.md index be2f060aa..4f5b9c642 100644 --- a/_source/user-guide/distributed-tracing/getting-started-tracing.md +++ b/_source/user-guide/distributed-tracing/getting-started-tracing.md @@ -75,7 +75,7 @@ Logz.io captures end-to-end distributed transactions from your applications and We recommend that you use the OpenTelemetry collector to gather trace transaction data from your system. With the merging of the OpenTracing and OpenCensus projects, OpenTelemetry is the CNCF standard. -[This link takes you to the OpenTelemetry installation.](https://app.logz.io/#/dashboard/send-your-data/tracing-sources/opentelemetry) +[This link takes you to the OpenTelemetry installation.](https://app.logz.io/#/dashboard/integrations/OpenTelemetry-data) The information is also available in the **Logz.io Docs**, in [**Ship your data > OpenTelemetry installation**](https://docs.logz.io/shipping/tracing-sources/opentelemetry.html). If you’re deploying distributed tracing on Kubernetes, we recommend the [Kubernetes deployment reference](https://docs.logz.io/shipping/tracing-sources/otel-traces-helm.html) topic. diff --git a/_source/user-guide/distributed-tracing/k8s-deployment.md b/_source/user-guide/distributed-tracing/k8s-deployment.md index 616c35ee3..4d30db2a6 100644 --- a/_source/user-guide/distributed-tracing/k8s-deployment.md +++ b/_source/user-guide/distributed-tracing/k8s-deployment.md @@ -37,7 +37,7 @@ Look up your Distributed Tracing `ACCOUNT TOKEN`.
Logz.io uses a Helm chart to send traces from your Kubernetes cluster via the OpenTelemetry collector. -Select **[Send your traces](https://app.logz.io/#/dashboard/send-your-data/collection?tag=all&collection=tracing-sources) [> Kubernetes](https://app.logz.io/#/dashboard/send-your-data/tracing-sources/otel-traces-helm)** and follow the steps to deploy the chart and trace your data. +Select **[Send your data](https://app.logz.io/#/dashboard/integrations/collectors) [> Kubernetes](https://app.logz.io/#/dashboard/integrations/Kubernetes)** and follow the steps to deploy the chart and trace your data. ##### Check the Distributed Tracing tab for your traces. diff --git a/_source/user-guide/distributed-tracing/service-performance-monitoring-setup.md b/_source/user-guide/distributed-tracing/service-performance-monitoring-setup.md index 5590d3a4c..9df096692 100644 --- a/_source/user-guide/distributed-tracing/service-performance-monitoring-setup.md +++ b/_source/user-guide/distributed-tracing/service-performance-monitoring-setup.md @@ -86,9 +86,9 @@ This process is only needed to activate the SPM. Once activated, the admin can r #### Configure and ship your data -You'll need to configure your collector to extract metrics from your data. Log into your Logz.io account and follow these steps to **[modify the OpenTelemetry collector](https://app.logz.io/#/dashboard/send-your-data/tracing-sources/span-metrics)**. +You'll need to configure your collector to extract metrics from your data. Log into your Logz.io account and follow these steps to **[modify the OpenTelemetry collector](https://app.logz.io/#/dashboard/integrations/OpenTelemetry-data)**. -You can configure the collector to ship data from a **[Local host](https://app.logz.io/#/dashboard/send-your-data/tracing-sources/span-metrics?type=local-host)**, **[Docker](https://app.logz.io/#/dashboard/send-your-data/tracing-sources/span-metrics?type=docker)**, or **[Kubernetes](https://app.logz.io/#/dashboard/send-your-data/tracing-sources/span-metrics?type=kubernetes)**. + Before deploying, make sure the collector you're using matches the supported version (should be **0.78.0** and up). diff --git a/_source/user-guide/distributed-tracing/service-performance-monitoring.md b/_source/user-guide/distributed-tracing/service-performance-monitoring.md index 4debcf219..42b7d0436 100644 --- a/_source/user-guide/distributed-tracing/service-performance-monitoring.md +++ b/_source/user-guide/distributed-tracing/service-performance-monitoring.md @@ -22,7 +22,7 @@ Service Performance Monitoring helps cut down the time to identify and resolve a ##### Service Performance Monitoring dashboard -The Service Performance Monitoring dashboard is part of your [Tracing account](https://app.logz.io/#/dashboard/jaeger/monitoring), located under the **Monitor** tab. You can generate a dashboard view for each of your services, and adjust the time span between 1 hour to 2 days ago. +The Service Performance Monitoring dashboard is part of your [Tracing account](https://app.logz.io/#/dashboard/jaeger/monitor), located under the **Monitor** tab. You can generate a dashboard view for each of your services, and adjust the time span between 1 hour to 2 days ago. ![Service Performance Monitoring](https://dytvr9ot2sszz.cloudfront.net/logz-docs/distributed-tracing/jaeger-spm-dashboard.png)