diff --git a/docs/sources/get-started/labels/_index.md b/docs/sources/get-started/labels/_index.md index bc946b418cff4..2d33900814b1e 100644 --- a/docs/sources/get-started/labels/_index.md +++ b/docs/sources/get-started/labels/_index.md @@ -30,7 +30,7 @@ A label is a key-value pair, for example all of the following are labels: A set of log messages which shares all the labels above would be called a log stream. When Loki performs searches, it first looks for all messages in your chosen stream, and then iterates through the logs in the stream to perform your query. Labeling will affect your queries, which in turn will affect your dashboards. -It’s worth spending the time to think about your labeling strategy before you begin ingesting logs to Loki. +It’s worth spending the time to think about your labeling strategy before you begin ingesting logs to Loki. ## Default labels for all users @@ -40,7 +40,7 @@ Loki does not parse or process your log messages on ingestion. However, dependin Loki automatically tries to populate a default `service_name` label while ingesting logs. The service name label is used to find and explore logs in the following Grafana and Grafana Cloud features: -- Explore Logs +- Logs Drilldown - Grafana Cloud Application Observability {{< admonition type="note" >}} diff --git a/docs/sources/get-started/labels/structured-metadata.md b/docs/sources/get-started/labels/structured-metadata.md index d5341a56b7119..8ea8dd17c19c0 100644 --- a/docs/sources/get-started/labels/structured-metadata.md +++ b/docs/sources/get-started/labels/structured-metadata.md @@ -23,7 +23,7 @@ You should only use structured metadata in the following situations: - If you are ingesting data in OpenTelemetry format, using Grafana Alloy or an OpenTelemetry Collector. Structured metadata was designed to support native ingestion of OpenTelemetry data. - If you have high cardinality metadata that should not be used as a label and does not exist in the log line. Some examples might include `process_id` or `thread_id` or Kubernetes pod names. -- If you are using [Explore Logs](https://grafana.com/docs/grafana-cloud/visualizations/simplified-exploration/logs/) to visualize and explore your Loki logs. You must set `discover_log_levels` and `allow_structured_metadata` to `true` in your Loki configuration. +- If you are using [Logs Drilldown](https://grafana.com/docs/grafana-cloud/visualizations/simplified-exploration/logs/) to visualize and explore your Loki logs. You must set `discover_log_levels` and `allow_structured_metadata` to `true` in your Loki configuration. - If you are a large-scale customer, who is ingesting more than 75TB of logs a month and are using [Bloom filters](https://grafana.com/docs/loki//operations/bloom-filters/) (Experimental), starting in [Loki 3.3](https://grafana.com/docs/loki//release-notes/v3-3/) Bloom filters now utilize structured metadata. ## Enable or disable structured metadata diff --git a/docs/sources/send-data/k8s-monitoring-helm/_index.md b/docs/sources/send-data/k8s-monitoring-helm/_index.md index d970030051122..59fc37e995d0a 100644 --- a/docs/sources/send-data/k8s-monitoring-helm/_index.md +++ b/docs/sources/send-data/k8s-monitoring-helm/_index.md @@ -168,12 +168,12 @@ As before, the command also includes a `values` file that specifies the configur ## Deploy the Kubernetes Monitoring Helm chart -The Kubernetes Monitoring Helm chart is used for gathering, scraping, and forwarding Kubernetes telemetry data to a Grafana stack. This includes the ability to collect metrics, logs, traces, and continuous profiling data. The scope of this tutorial is to deploy the Kubernetes Monitoring Helm chart to collect pod logs and Kubernetes events. +The Kubernetes Monitoring Helm chart is used for gathering, scraping, and forwarding Kubernetes telemetry data to a Grafana stack. This includes the ability to collect metrics, logs, traces, and continuous profiling data. The scope of this tutorial is to deploy the Kubernetes Monitoring Helm chart to collect pod logs and Kubernetes events. To deploy the Kubernetes Monitoring Helm chart run the following command: ```bash -helm install --values ./k8s-monitoring-values.yml k8s grafana/k8s-monitoring -n meta +helm install --values ./k8s-monitoring-values.yml k8s grafana/k8s-monitoring -n meta ``` Within the configuration file `k8s-monitoring-values.yml` we have defined the following: @@ -260,14 +260,14 @@ kubectl --namespace meta port-forward $POD_NAME 3000 --address 0.0.0.0 This will make your terminal unusable until you stop the port-forwarding process. To stop the process, press `Ctrl + C`. {{< /admonition >}} -This command will port-forward the Grafana service to your local machine on port `3000`. +This command will port-forward the Grafana service to your local machine on port `3000`. -You can now access Grafana by navigating to [http://localhost:3000](http://localhost:3000) in your browser. The default credentials are `admin` and `adminadminadmin`. +You can now access Grafana by navigating to [http://localhost:3000](http://localhost:3000) in your browser. The default credentials are `admin` and `adminadminadmin`. -One of the first places you should visit is Explore Logs which lets you automatically visualize and explore your logs without having to write queries: +One of the first places you should visit is Logs Drilldown which lets you automatically visualize and explore your logs without having to write queries: [http://localhost:3000/a/grafana-lokiexplore-app](http://localhost:3000/a/grafana-lokiexplore-app) -{{< figure max-width="100%" src="/media/docs/loki/k8s-logs-explore-logs.png" caption="Explore Logs view of K8s logs" alt="Explore Logs view of K8s logs" >}} +{{< figure max-width="100%" src="/media/docs/loki/k8s-logs-explore-logs.png" caption="Logs Drilldown view of K8s logs" alt="Logs Drilldown view of K8s logs" >}} diff --git a/docs/sources/visualize/grafana.md b/docs/sources/visualize/grafana.md index f72ef39075bab..153433972c686 100644 --- a/docs/sources/visualize/grafana.md +++ b/docs/sources/visualize/grafana.md @@ -14,25 +14,25 @@ keywords: # Visualize log data -Grafana Loki does not have its own user interface. Most users [install Grafana](https://grafana.com/docs/grafana/latest/setup-grafana/installation/) in order to visualize their log data. Grafana versions after 6.3 have built-in support for Grafana Loki and [LogQL](https://grafana.com/docs/loki//query/). +Grafana Loki does not have its own user interface. Most users [install Grafana](https://grafana.com/docs/grafana/latest/setup-grafana/installation/) in order to visualize their log data. Grafana versions after 6.3 have built-in support for Grafana Loki and [LogQL](https://grafana.com/docs/loki//query/). There are several different options for how to visualize your log data in Grafana: -- [Explore Logs](https://grafana.com/docs/grafana-cloud/visualizations/simplified-exploration/logs/) lets you explore logs from your Loki data source without writing LogQL queries. +- [Logs Drilldown](https://grafana.com/docs/grafana-cloud/visualizations/simplified-exploration/logs/) lets you explore logs from your Loki data source without writing LogQL queries. - [Grafana Explore](https://grafana.com/docs/grafana/latest/explore/logs-integration/) helps you build and iterate on queries written in LogQL. Once you have a query that finds the data you're looking for, you can consider using your query in a Grafana dashboard. - [Loki Mixins](https://grafana.com/docs/loki/latest/operations/observability/#mixins) include a pre-built set of dashboards, recording rules, and alerts for monitoring Loki. - [Grafana Dashboards](https://grafana.com/docs/grafana/latest/dashboards/) let you query, transform, visualize, and understand your log data. You can create your own custom dashboards, or import and modify public dashboards shared by the community. -## Explore Logs +## Logs Drilldown -Explore Logs lets you automatically visualize and explore logs. Explore Logs makes assumptions about what data you might want to see to help you quickly get started viewing your logs without having to learn LogQL and write queries. +Grafana Logs Drilldown lets you automatically visualize and explore logs. Logs Drilldown makes assumptions about what data you might want to see to help you quickly get started viewing your logs without having to learn LogQL and write queries. -- If you are a Grafana Cloud user, you can access Explore Logs from the Grafana Cloud main navigation menu: select **Explore** > **Logs**. +- If you are a Grafana Cloud user, you can access Logs Drilldown from the Grafana Cloud main navigation menu: select **Explore** > **Logs**. -- If you are an open source or Grafana Enterprise Logs user, you can install the [Explore Logs plugin](https://grafana.com/docs/grafana-cloud/visualizations/simplified-exploration/logs/access/). For more information, refer to the [Explore Logs documentation](https://grafana.com/docs/grafana-cloud/visualizations/simplified-exploration/logs/). +- If you are an open source or Grafana Enterprise Logs user, you can install the [Logs Drilldown plugin](https://grafana.com/docs/grafana-cloud/visualizations/simplified-exploration/logs/access/). For more information, refer to the [Logs Drilldown documentation](https://grafana.com/docs/grafana-cloud/visualizations/simplified-exploration/logs/). {{< admonition type="note" >}} -Starting with Grafana v11.3, the plugin for the Explore Logs app is installed in Grafana by default. +Starting with Grafana v11.3, the plugin for the Logs Drilldown app is installed in Grafana by default. {{< /admonition >}} ## Grafana Explore