From 0691611cfdc68ad10fdc078269d99bf50634aa94 Mon Sep 17 00:00:00 2001 From: Scott Anderson Date: Wed, 11 Sep 2019 16:09:56 -0600 Subject: [PATCH] fixed various broken links --- .../cloud/account-management/offboarding.md | 2 +- .../notification-endpoints/update.md | 2 +- .../process-data/manage-tasks/create-task.md | 2 - content/v2.0/query-data/guides/histograms.md | 5 +- content/v2.0/query-data/guides/sql.md | 4 +- content/v2.0/reference/annotated-csv.md | 4 +- content/v2.0/reference/glossary.md | 81 +++++++++---------- .../visualization-types/graph.md | 2 +- 8 files changed, 50 insertions(+), 52 deletions(-) diff --git a/content/v2.0/cloud/account-management/offboarding.md b/content/v2.0/cloud/account-management/offboarding.md index f2b9d6fb2..ea60507b8 100644 --- a/content/v2.0/cloud/account-management/offboarding.md +++ b/content/v2.0/cloud/account-management/offboarding.md @@ -30,7 +30,7 @@ For details, see [Export a task](/v2.0/process-data/manage-tasks/export-task/). #### Export dashboards -For details, see [Export a dashboard](v2.0/visualize-data/dashboards/export-dashboard/). +For details, see [Export a dashboard](/v2.0/visualize-data/dashboards/export-dashboard/). #### Telegraf configurations diff --git a/content/v2.0/monitor-alert/notification-endpoints/update.md b/content/v2.0/monitor-alert/notification-endpoints/update.md index 585a13932..a35ff0011 100644 --- a/content/v2.0/monitor-alert/notification-endpoints/update.md +++ b/content/v2.0/monitor-alert/notification-endpoints/update.md @@ -13,7 +13,7 @@ related: cloud_all: true --- -To update the notification endpoint details, complete the procedures below as needed. To update the notification endpoint selected for a notification rule, see [update notification rules](/v2.0/cloud/monitor-alert/update-notification-rules/). +To update the notification endpoint details, complete the procedures below as needed. To update the notification endpoint selected for a notification rule, see [update notification rules](/v2.0/monitor-alert/notification-rules/update/). ## Add a label to notification endpoint diff --git a/content/v2.0/process-data/manage-tasks/create-task.md b/content/v2.0/process-data/manage-tasks/create-task.md index 1b578a9f8..270a0d1c2 100644 --- a/content/v2.0/process-data/manage-tasks/create-task.md +++ b/content/v2.0/process-data/manage-tasks/create-task.md @@ -55,8 +55,6 @@ The InfluxDB UI provides multiple ways to create a task: 6. In the right panel, enter your task script. 7. Click **Save** in the upper right. -{{< img-hd src="/img/2-0-tasks-create-edit.png" title="Create a task" />}} - ### Import a task 1. Click on the **Tasks** icon in the left navigation menu. diff --git a/content/v2.0/query-data/guides/histograms.md b/content/v2.0/query-data/guides/histograms.md index a0be7ac6d..4253e8183 100644 --- a/content/v2.0/query-data/guides/histograms.md +++ b/content/v2.0/query-data/guides/histograms.md @@ -74,7 +74,7 @@ Because the Histogram visualization uses visualization controls to creates bins {{% note %}} Output of the [`histogram()` function](#histogram-function) is **not** compatible with the Histogram visualization type. -View the example [below](#visualize-error-counts-by-severity-over-time). +View the example [below](#visualize-errors-by-severity). {{% /note %}} ## Examples @@ -160,7 +160,8 @@ Table: keys: [_start, _stop, _field, _measurement, host] ``` ### Visualize errors by severity -Use the [Telegraf Syslog plugin](Telegraf Syslog plugin) to collect error information from your system. +Use the [Telegraf Syslog plugin](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/syslog) +to collect error information from your system. Query the `severity_code` field in the `syslog` measurement: ```js diff --git a/content/v2.0/query-data/guides/sql.md b/content/v2.0/query-data/guides/sql.md index 2a3d6dc46..aabcfc312 100644 --- a/content/v2.0/query-data/guides/sql.md +++ b/content/v2.0/query-data/guides/sql.md @@ -94,7 +94,7 @@ join(tables: {metric: sensorMetrics, info: sensorInfo}, on: ["sensor_id"]) ## Use SQL results to populate dashboard variables Use `sql.from()` to [create dashboard variables](/v2.0/visualize-data/variables/create-variable/) from SQL query results. -The following example uses the [air sensor sample data](#sample-data) below to +The following example uses the [air sensor sample data](#sample-sensor-data) below to create a variable that lets you select the location of a sensor. ```js @@ -167,7 +167,7 @@ To use `air-sensor-data.rb`: _**Note:** Use the `--help` flag to view other configuration options._ -5. [Query your target bucket](v2.0/query-data/execute-queries/) to ensure the +5. [Query your target bucket](/v2.0/query-data/execute-queries/) to ensure the generated data is writing successfully. The generator doesn't catch errors from write requests, so it will continue running even if data is not writing to InfluxDB successfully. diff --git a/content/v2.0/reference/annotated-csv.md b/content/v2.0/reference/annotated-csv.md index 001154163..46ec4d69e 100644 --- a/content/v2.0/reference/annotated-csv.md +++ b/content/v2.0/reference/annotated-csv.md @@ -134,9 +134,9 @@ Annotation rows are optional, describe column properties, and start with `#` (or |Annotation name | Values| Description | | :-------- | :--------- | :-------| -| **datatype** | a [valid data type](#Valid-data-types) | Describes the type of data. | +| **datatype** | a [valid data type](#valid-data-types) | Describes the type of data. | | **group** | boolean flag `true` or `false` | Indicates the column is part of the group key.| -| **default** | a [valid data type](#Valid-data-types) |Value to use for rows with an empty string value.| +| **default** | a [valid data type](#valid-data-types) |Value to use for rows with an empty string value.| ##### Example Encoding of datatype and group annotations for two tables. diff --git a/content/v2.0/reference/glossary.md b/content/v2.0/reference/glossary.md index 9f3fd3243..54b9ac46a 100644 --- a/content/v2.0/reference/glossary.md +++ b/content/v2.0/reference/glossary.md @@ -106,15 +106,16 @@ monitor.check( ) ``` -This check gives rows with a `_value` greater than 90.0 a crit _level; rows greater than 80.0 get a warn _level, and so on. +This check gives rows with a `_value` greater than 90.0 a crit `_level`; rows greater than 80.0 get a warn `_level`, and so on. -Learn how to [create a check](/v2.0/cloud/monitor-alert/manage-checks/create-checks). +Learn how to [create a check](/v2.0/monitor-alert/checks/create/). Related entries: [check status](#check-status), [notification rule](#notification-rule), [notification endpoint](#notification-endpoint) ### check status -A [check](#check) gets one of the following statuses (`_level`): CRIT, INFO, WARN, or OK. Check statuses are written to a status measurement in the _monitoring bucket. +A [check](#check) gets one of the following statuses (`_level`): `crit`, `info`, `warn`, or `ok`. +Check statuses are written to a status measurement in the `_monitoring` bucket. Related entries: [check](#check), [notification rule](#notification-rule), [notification endpoint](#notification-endpoint) @@ -124,10 +125,10 @@ Comma-separated values (CSV) delimits text between commas to separate values. A InfluxData uses annotated CSV (comma-separated values) format to encode HTTP responses and results returned to the Flux csv.from() function. For more detail, see [Annotated CSV](/v2.0/reference/annotated-csv/). - [user](#user) ### date-time @@ -246,7 +245,7 @@ Aggregating high resolution data into lower resolution data to preserve disk spa A data type that represents a duration of time (1s, 1m, 1h, 1d). Retention policies are set using durations. Data older than the duration is automatically dropped from the database. -Related entries: [retention policy](#retention-policy-rp) + ## E @@ -259,8 +258,8 @@ Metrics gathered at irregular time intervals. In Flux, a an explicit block is a possibly empty sequence of statements within matching braces (`{ }`) that is defined in the source code, for example: ``` -Block = "{" StatementList "} -StatementList = { Statement } +Block = "{" StatementList "} +StatementList = { Statement } ``` Related entries: [implicit block](#implicit-block), [block](#block) @@ -338,7 +337,7 @@ A lightweight scripting language for querying databases (like InfluxDB) and work Flux functions aggregate, select, and transform time series data. For a complete list of Flux functions, see [Flux functions](/v2.0/reference/flux/stdlib/all-functions/). -Related entries: [aggregation](#aggregation), [selector](#selector), [transformation](#transformation) +Related entries: [aggregate](#aggregate), [selector](#selector), [transformation](#transformation) ### function block @@ -384,7 +383,7 @@ Related entries: [bucket](#bucket) [field key](#field-key), [measurement](#measurement), -[retention policy](#retention-policy-rp), + [tag key](#tag-key), [user](#user) @@ -424,7 +423,7 @@ The SQL-like query language used to query data in InfluxDB 1.x. Telegraf input plugins actively gather metrics and deliver them to the core agent, where aggregator, processor, and output plugins can operate on the metrics. In order to activate an input plugin, it needs to be enabled and configured in Telegraf's configuration file. -Related entries: [aggregator plugin](/telegraf/v1.10/concepts/glossary/#aggregator-plugin), [collection interval](/telegraf/v1.10/concepts/glossary/#collection-interval), [output plugin](/telegraf/v1.10/concepts/glossary/#output-plugin), [processor plugin](/telegraf/v1.10/concepts/glossary/#processor-plugin) +Related entries: [aggregator plugin](#aggregator-plugin), [collection interval](#collection-interval), [output plugin](#output-plugin), [processor plugin](#processor-plugin) ### instance @@ -466,7 +465,7 @@ A literal is value in an expression, a number, character, string, function, obje See examples of [Flux literals](/v2.0/reference/flux/language/expressions/#examples-of-function-literals). - @@ -849,7 +848,7 @@ The key-value pair in InfluxDB's data structure that records metadata. Tags are an optional part of InfluxDB's data structure but they are useful for storing commonly-queried metadata; tags are indexed so queries on tags are performant. *Query tip:* Compare tags to fields; fields are not indexed. -Related entries: [field](/influxdb/latest/concepts/glossary/#field), [tag key](/influxdb/latest/concepts/glossary/#tag-key), [tag set](/influxdb/latest/concepts/glossary/#tag-set), [tag value](/influxdb/latest/concepts/glossary/#tag-value) +Related entries: [field](#field), [tag key](#tag-key), [tag set](#tag-set), [tag value](#tag-value) ### tag key @@ -858,7 +857,7 @@ Tag keys are indexed so queries on tag keys are processed quickly. *Query tip:* Compare tag keys to field keys. Field keys are not indexed. -Related entries: [field key](/#field-key), [tag](#tag), [tag set](#tag-set), [tag value](#tag-value) +Related entries: [field key](#field-key), [tag](#tag), [tag set](#tag-set), [tag value](#tag-value) ### tag set @@ -917,9 +916,9 @@ By default, tracing is disabled in InfluxDB. To enable tracing or set other Infl ### transformation An InfluxQL function that returns a value or a set of values calculated from specified points, but does not return an aggregated value across those points. -See [InfluxQL functions](/influxdb/latest/query_language/functions/#transformations) for a complete list of the available and upcoming aggregations. +See [InfluxQL functions](http://docs.influxdata.com/influxdb/latest/query_language/functions/#transformations) for a complete list of the available and upcoming aggregations. -Related entries: [aggregation](/influxdb/latest/concepts/glossary/#aggregation), [function](/influxdb/latest/concepts/glossary/#function), [selector](/influxdb/latest/concepts/glossary/#selector) +Related entries: [aggregate](#aggregate), [function](#function), [selector](#selector) ## TSI (Time Series Index) @@ -933,7 +932,7 @@ The Time Series Logs (TSL) extension (.tsl) identifies Time Series Index (TSI) l A data storage format that allows greater compaction and higher write and read throughput than B+ or LSM tree implementations. For more information, see [Storage engine](http://docs.influxdata.com/influxdb/latest/concepts/storage_engine/). -Related entries: [TSI](#TSI) +Related entries: [TSI](#tsi-time-series-index) ## U @@ -957,7 +956,7 @@ The preferred measurement of the rate at which data are persisted to InfluxDB. W To calculate the values per second rate, multiply the number of points written per second by the number of values stored per point. For example, if the points have four fields each, and a batch of 5000 points is written 10 times per second, the values per second rate is `4 field values per point * 5000 points per batch * 10 batches per second = 200,000 values per second`. -Related entries: [batch](#batch), [field](#field), [point](#point), [points per second](#points-per-second) +Related entries: [batch](#batch), [field](#field), [point](#point) ### variable diff --git a/content/v2.0/visualize-data/visualization-types/graph.md b/content/v2.0/visualize-data/visualization-types/graph.md index d5af696a9..b32cc360c 100644 --- a/content/v2.0/visualize-data/visualization-types/graph.md +++ b/content/v2.0/visualize-data/visualization-types/graph.md @@ -12,7 +12,7 @@ menu: --- The Graph visualization provides several types of graphs, each configured through -the [Graph options](#graph-options). +the [Graph controls](#graph-controls). {{< img-hd src="/img/2-0-visualizations-line-graph-example.png" alt="Line Graph example" />}}