From 587da1a905edfe208f3594ac8579fa5799b2dd37 Mon Sep 17 00:00:00 2001 From: Scott Anderson Date: Wed, 24 Apr 2019 11:44:05 -0600 Subject: [PATCH] fixed broken links --- content/v2.0/collect-data/quick-start.md | 6 +++--- content/v2.0/visualize-data/variables/_index.md | 2 +- content/v2.0/visualize-data/variables/create-variable.md | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/content/v2.0/collect-data/quick-start.md b/content/v2.0/collect-data/quick-start.md index b2b30f798..aa395863e 100644 --- a/content/v2.0/collect-data/quick-start.md +++ b/content/v2.0/collect-data/quick-start.md @@ -14,19 +14,19 @@ weight: 101 --- Select **Quick Start** in the last step of the InfluxDB user interface's (UI) -[setup process](/v2.0/get-started/#setup-influxdb) to quickly start collecting data with InfluxDB. +[setup process](/v2.0/get-started/#set-up-influxdb) to quickly start collecting data with InfluxDB. Quick Start creates a data scraper that collects metrics from the InfluxDB `/metrics` endpoint. The scraped data provides a robust dataset of internal InfluxDB metrics that you can query, visualize, and process. ## Use Quick Start to collect InfluxDB metrics -After [initializing InfluxDB v2.0](/v2.0/get-started/#setup-influxdb), +After [setting up InfluxDB v2.0](/v2.0/get-started/#set-up-influxdb), the "Let's start collecting data!" page displays options for collecting data. Click **Quick Start**. InfluxDB creates and configures a new [scraper](/v2.0/collect-data/scrape-data/). The target URL points to the `/metrics` HTTP endpoint of your local InfluxDB instance (e.g. `http://localhost:9999/metrics`), which outputs internal InfluxDB metrics in the [Prometheus data format](https://prometheus.io/docs/instrumenting/exposition_formats/). -It stores the scraped metrics in the bucket created during the [initial setup process](/v2.0/get-started/#setup-influxdb). +It stores the scraped metrics in the bucket created during the [initial setup process](/v2.0/get-started/#set-up-influxdb). The following message briefly appears in the UI: diff --git a/content/v2.0/visualize-data/variables/_index.md b/content/v2.0/visualize-data/variables/_index.md index b64f6604e..58c6529d8 100644 --- a/content/v2.0/visualize-data/variables/_index.md +++ b/content/v2.0/visualize-data/variables/_index.md @@ -17,7 +17,7 @@ making it easy to interact with your dashboard cells and explore your data. Variables are scoped by organization. ## Use dashboard variables -Both [predefined dashboard variables](#predefined-dashboard-variables) and [custom dashboard variables](#manage-custom-variables) +Both [predefined dashboard variables](#predefined-dashboard-variables) and [custom dashboard variables](#custom-dashboard-variables) are stored in a `v` object associated with each dashboard. Reference each variable using dot-notation (e.g. `v.variableName`). diff --git a/content/v2.0/visualize-data/variables/create-variable.md b/content/v2.0/visualize-data/variables/create-variable.md index 96cc30bde..195bdd5f7 100644 --- a/content/v2.0/visualize-data/variables/create-variable.md +++ b/content/v2.0/visualize-data/variables/create-variable.md @@ -20,7 +20,7 @@ _For information about variable types, see [Variable types](/v2.0/visualize-data {{< nav-icon "data-explorer" >}} 2. Click **Script Editor** on the lower right. -3. Build the query for your variable using the [Table visualization type](v2.0/visualize-data/visualization-types/#table) or enable the **View Raw Data** option. +3. Build the query for your variable using the [Table visualization type](/v2.0/visualize-data/visualization-types/#table) or enable the **View Raw Data** option. 4. Click **Save As** in the upper right. 5. In the window that appears, select **Variable**. 6. Enter a name for your variable in the **Name** field.