+
+
The log viewer provides a detailed histogram showing the time-based distribution of log entries color-coded by log severity.
It also includes a live stream of logs that can be searched, filtered, and paused to analyze specific time ranges.
Logs are pulled from the `syslog` measurement.
_Other log inputs and alternate log measurement options will be available in future updates._
-
+
### Searching and filtering logs
Logs are searched using keywords or regular expressions.
They can also be filtered by clicking values in the log table such as `severity` or `facility`.
Any tag values included with the log entry can be used as a filter.
-
+
> **Note:** The log search field is case-sensitive.
@@ -45,13 +45,13 @@ Timeframe selection allows you to go to to a specific event and see logs both pr
When viewing logs from a previous time window, first select the target time, then select the offset.
The offset is used to define the upper and lower thresholds of the window from which logs are pulled.
-
+
## Configuring the log viewer
The log viewer can be customized to fit your specific needs.
Open the log viewer configuration options by clicking the gear button in the top right corner of the log viewer.
-
+
### Severity colors
Every log severity is assigned a color which is used in the display of log entries.
@@ -68,15 +68,15 @@ Below are the options and how they appear in the log table:
| Severity Format | Display |
| --------------- |:------- |
-| Dot | 
|
-| Dot + Text | 
|
-| Text | 
|
+| Dot | 
|
+| Dot + Text | 
|
+| Text | 
|
## Logs in dashboards
An incredibly powerful way to analyze log data is by creating dashboards that include log data.
This is possible by using the [Table visualization type](/chronograf/v1.6/guides/visualization-types/#table) to display log data in your dashboard.
-
+
This type of visualization allows you to quickly identify anomalies in other metrics and see logs associated with those anomalies.
diff --git a/content/chronograf/v1.6/guides/annotations.md b/content/chronograf/v1.6/guides/annotations.md
index 864e6e694..057e55021 100644
--- a/content/chronograf/v1.6/guides/annotations.md
+++ b/content/chronograf/v1.6/guides/annotations.md
@@ -20,7 +20,7 @@ The following screenshot of five graph views displays annotations for a single p
The text and timestamp for the single point in time can be seem above the annotation line in the graph view on the lower right.
The annotation displays "`Deploy v3.8.1-2`" and the time "`2018/28/02 15:59:30:00`".
-
+
**To add and edit an annotation:**
diff --git a/content/chronograf/v1.6/guides/cloning-in-ui.md b/content/chronograf/v1.6/guides/cloning-in-ui.md
index 4c98255ab..7f42ad691 100644
--- a/content/chronograf/v1.6/guides/cloning-in-ui.md
+++ b/content/chronograf/v1.6/guides/cloning-in-ui.md
@@ -18,11 +18,11 @@ Dashboards in Chronograf can be cloned (or copied) to be used to create a dashbo
1. On the **Dashboards** page, hover your cursor over the listing of the dashboard that you want to clone and click the **Clone** button that appears.
-
+
The cloned dashboard opens and displays the name of the original dashboard with `(clone)` after it.
-
+
You can now change the dashboard name and customize the dashboard.
@@ -34,10 +34,10 @@ Cells in Chronograf dashboards can be cloned, or copied, to quickly create a cel
1. On the dashboard cell that you want to make a copy of, click the **Clone** icon and then confirm by clicking **Clone Cell**.
-
+
2. The cloned cell appears in the dashboard displaying the nameof the original cell with `(clone)` after it.
-
+
You can now change the cell name and customize the cell.
diff --git a/content/chronograf/v1.6/guides/configuring-alert-endpoints.md b/content/chronograf/v1.6/guides/configuring-alert-endpoints.md
index c3893c5d5..f32599ba5 100644
--- a/content/chronograf/v1.6/guides/configuring-alert-endpoints.md
+++ b/content/chronograf/v1.6/guides/configuring-alert-endpoints.md
@@ -58,7 +58,7 @@ For example, Chronograf's Slack integration allows users to specify a default ch
Configure Chronograf to send alert messages to a HipChat room.
The sections below describe each configuration option.
-
+
#### Subdomain
@@ -88,7 +88,7 @@ The following steps describe how to create the API access token:
Your token appears in the table just above the **Create new token** section:
-
+
### Kafka
@@ -226,7 +226,7 @@ Click **Add Another Config** to add additional Slack alert endpoints. Each addit
Configure Chronograf to send alert messages to an existing Telegram bot.
The sections below describe each configuration option.
-
+
#### Telegram bot
diff --git a/content/chronograf/v1.6/guides/create-a-dashboard.md b/content/chronograf/v1.6/guides/create-a-dashboard.md
index 51c37e9db..348200137 100644
--- a/content/chronograf/v1.6/guides/create-a-dashboard.md
+++ b/content/chronograf/v1.6/guides/create-a-dashboard.md
@@ -14,7 +14,7 @@ This guide shows you how to create custom Chronograf dashboards.
By the end of this guide, you'll be aware of the tools available to you for creating dashboards similar to this example:
-
+
## Requirements
@@ -36,7 +36,7 @@ Click **Name This Dashboard** and type a new name. In this guide, "ChronoDash" i
In the first cell, titled "Untitled Cell", click **Edit**
to open the cell editor mode.
-
+
### Step 3: Create your query
@@ -51,13 +51,13 @@ Those defaults are configurable using the query builder or by manually editing t
In addition, the time range (`:dashboardTime:`) is [configurable on the dashboard](#step-6-configure-your-dashboard).
-
+
### Step 4: Choose your visualization type
Chronograf supports many different [visualization types](/chronograf/latest/guides/visualization-types/). To choose a visualization type, click **Visualization** and select **Step-Plot Graph**.
-
+
### Step 5: Save your cell
Click **Save** (the green checkmark icon) to save your cell.
diff --git a/content/chronograf/v1.6/guides/create-alert-rules.md b/content/chronograf/v1.6/guides/create-alert-rules.md
index e7dbf8cf5..16107b21b 100644
--- a/content/chronograf/v1.6/guides/create-alert-rules.md
+++ b/content/chronograf/v1.6/guides/create-alert-rules.md
@@ -38,12 +38,12 @@ See the [Configuring Kapacitor Event Handlers](/chronograf/latest/guides/configu
Navigate to the **Manage Tasks** page under **Alerting** in the left navigation, then click **+ Build Alert Rule** in the top right corner.
-
+
The **Manage Tasks** page is used to create and edit your Chronograf alert rules.
The steps below guide you through the process of creating a Chronograf alert rule.
-
+
### Step 1: Name the alert rule
@@ -72,7 +72,7 @@ Navigate through databases, measurements, fields, and tags to select the relevan
In this example, select the `telegraf` [database](/influxdb/latest/concepts/glossary/#database), the `autogen` [retention policy](/influxdb/latest/concepts/glossary/#retention-policy-rp), the `cpu` [measurement](/influxdb/latest/concepts/glossary/#measurement), and the `usage_idle` [field](/influxdb/latest/concepts/glossary/#field).
-
+
### Step 4: Define the rule condition
@@ -80,7 +80,7 @@ Define the threshold condition.
Condition options are determined by the [alert type](#step-2-select-the-alert-type).
For this example, the alert conditions are if `usage_idle` is less than `80`.
-
+
The graph shows a preview of the relevant data and the threshold number.
By default, the graph shows data from the past 15 minutes.
@@ -98,7 +98,7 @@ Each handler has unique configurable options.
For this example, choose the **slack** alert handler and enter the desired options.
-
+
> Multiple alert handlers can be added to send alerts to multiple endpoints.
@@ -111,7 +111,7 @@ As you type your alert message, clicking the data templates will insert them at
In this example, use the alert message, `Your idle CPU usage is {{.Level}} at {{ index .Fields "value" }}.`.
-
+
*View the Kapacitor documentation for more information about [message template data](/kapacitor/latest/nodes/alert_node/#message).*
@@ -120,7 +120,7 @@ In this example, use the alert message, `Your idle CPU usage is {{.Level}} at {{
Click **Save Rule** in the top right corner and navigate to the **Manage Tasks** page to see your rule.
Notice that you can easily enable and disable the rule by toggling the checkbox in the **Enabled** column.
-
+
Next, move on to the section below to experience your alert rule in action.
@@ -149,10 +149,10 @@ Assuming the first step was successful, `#ohnos` should reveal at least two aler
* The first alert message indicates that your idle CPU usage was `CRITICAL`, meaning it dipped below `80%`.
* The second alert message indicates that your idle CPU usage returned to an `OK` level of `80%` or above.
-
+
You can also see alerts on the **Alert History** page available under **Alerting** in the left navigation.
-
+
That's it! You've successfully used Chronograf to configure an alert rule to monitor your idle CPU usage and send notifications to Slack.
diff --git a/content/chronograf/v1.6/guides/dashboard-template-variables.md b/content/chronograf/v1.6/guides/dashboard-template-variables.md
index f636f8361..8305d2d9b 100644
--- a/content/chronograf/v1.6/guides/dashboard-template-variables.md
+++ b/content/chronograf/v1.6/guides/dashboard-template-variables.md
@@ -25,7 +25,7 @@ You can use either [predefined template variables](#predefined-template-variable
or [custom template variables](#create-custom-template-variables).
Variable values are then selected in your dashboard user-interface (UI).
-
+
## Predefined template variables
Chronograf includes predefined template variables controlled by elements in the Chrongraf UI.
@@ -38,7 +38,7 @@ These template variables can be used in any of your cells' queries.
### dashboardTime
The `:dashboardTime:` template variable is controlled by the "time" dropdown in your Chronograf dashboard.
-
+
If using relative times, it represents the time offset specified in the dropdown (-5m, -15m, -30m, etc.) and assumes time is relative to "now".
If using absolute times defined by the date picker, `:dashboardTime:` is populated with lower threshold.
@@ -56,7 +56,7 @@ WHERE time > :dashboardTime:
### upperDashboardTime
The `:upperDashboardTime:` template variable is defined by the upper time limit specified using the date picker.
-
+
It will inherit `now()` when using relative time frames or the upper time limit when using absolute timeframes.
@@ -69,7 +69,7 @@ WHERE time > :dashboardTime: AND time < :upperDashboardTime:
### interval
The `:interval:` template variable is defined by the interval dropdown in the Chronograf dashboard.
-
+
In cell queries, it should be used in the `GROUP BY time()` clause that accompanies aggregate functions:
@@ -95,7 +95,7 @@ To create a template variable:
If using the CSV or Map types, upload or input the CSV with the desired values in the appropriate format then select a default value.
5. Click **Create**.
-
+
Once created, the template variable can be used in any of your cell's queries or titles
and a dropdown for the variable will be included at the top of your dashboard.
@@ -251,7 +251,7 @@ key3,value3
key4,value4
```
-
+
> If values are meant to be used as string field values, wrap them in single quote ([required by InfluxQL](/influxdb/latest/troubleshooting/frequently-asked-questions/#when-should-i-single-quote-and-when-should-i-double-quote-in-queries)). This only pertains to values. String keys do not matter.
@@ -285,7 +285,7 @@ The customer names would populate your template variable dropdown rather than th
Vary part of a query with a customized meta query that pulls a specific array of values from InfluxDB.
These variables allow you to pull a highly customized array of potential values and offer advanced functionality such as [filtering values based on other template variables](#filtering-template-variables-with-other-template-variables).
-
+
_**Example custom meta query variable in a cell query**_
```sql
@@ -330,7 +330,7 @@ For example, let's say you want to list all the field keys associated with a mea
1. Create a template variable named `:measurementVar:` _(the name "measurement" is [reserved]( #reserved-variable-names))_ that uses the [Measurements](#measurements) variable type to pull in all measurements from the `telegraf` database.
- 
+ 
2. Create a template variable named `:fieldKey:` that uses the [custom meta query](#custom-meta-query) variable type.
The following meta query pulls a list of field keys based on the existing `:measurementVar:` template variable.
@@ -339,7 +339,7 @@ The following meta query pulls a list of field keys based on the existing `:meas
SHOW FIELD KEYS ON telegraf FROM :measurementVar:
```
- 
+ 
3. Create a new dashboard cell that uses the `:fieldKey:` and `:measurementVar` template variables in its query.
@@ -349,7 +349,7 @@ The following meta query pulls a list of field keys based on the existing `:meas
The resulting dashboard will work like this:
-
+
### Defining template variables in the URL
Chronograf uses URL query parameters (also known as query string parameters) to set both display options and template variables in the URL.
diff --git a/content/chronograf/v1.6/guides/monitoring-influxenterprise-clusters.md b/content/chronograf/v1.6/guides/monitoring-influxenterprise-clusters.md
index d33454c91..3688da390 100644
--- a/content/chronograf/v1.6/guides/monitoring-influxenterprise-clusters.md
+++ b/content/chronograf/v1.6/guides/monitoring-influxenterprise-clusters.md
@@ -32,7 +32,7 @@ Chronograf and the other components of the TICK stack are supported on several o
Before we begin, here's an overview of the final monitoring setup:
-
+
The diagram above shows an InfluxDB Enterprise cluster that consists of three meta nodes (M) and three data nodes (D).
Each data node has its own [Telegraf](/telegraf/latest/) instance (T).
@@ -233,7 +233,7 @@ Chronograf can be downloaded from the [InfluxData downloads page](https://portal
To access Chronograf, go to http://localhost:8888.
The welcome page includes instructions for connecting Chronograf to that instance.
-
+
For the `Connection String`, enter the hostname or IP of your InfluxDB OSS instance, and be sure to include the default port: `8086`.
Next, name your data source; this can be anything you want.
@@ -245,17 +245,17 @@ Chronograf works with the Telegraf data in your InfluxDB OSS instance.
The `Host List` page shows your data node's hostnames, their statuses, CPU usage, load, and their configured applications.
In this case, you've only enabled the system stats input plugin so `system` is the single application that appears in the `Apps` column.
-
+
Click `system` to see the Chronograf canned dashboard for that application.
Keep an eye on your data nodes by viewing that dashboard for each hostname:
-
+
Next, check out the Data Explorer to create a customized graph with the monitoring data.
In the image below, the Chronograf query editor is used to visualize the idle CPU usage data for each data node:
-
+
Create more customized graphs and save them to a dashboard on the Dashboard page in Chronograf.
See the [Creating Chronograf dashboards](/chronograf/latest/guides/create-a-dashboard/) guide for more information.
diff --git a/content/chronograf/v1.6/guides/presentation-mode.md b/content/chronograf/v1.6/guides/presentation-mode.md
index dd30157fd..bedea108c 100644
--- a/content/chronograf/v1.6/guides/presentation-mode.md
+++ b/content/chronograf/v1.6/guides/presentation-mode.md
@@ -13,7 +13,7 @@ Presentation mode allows you to view Chronograf in full screen, hiding the left
## Entering presentation mode manually
To enter presentation mode manually, click the icon in the upper right:
-
+
To exit presentation mode, press `ESC`.
diff --git a/content/chronograf/v1.6/guides/visualization-types.md b/content/chronograf/v1.6/guides/visualization-types.md
index 38fcf49e6..d86f614b0 100644
--- a/content/chronograf/v1.6/guides/visualization-types.md
+++ b/content/chronograf/v1.6/guides/visualization-types.md
@@ -10,7 +10,7 @@ menu:
Chronograf's dashboard views support the following visualization types, which can be selected in the **Visualization Type** selection view.
-[Visualization Type selector](/img/chronograf/chrono-viz-types-selector.png)
+[Visualization Type selector](/img/chronograf/1-6-viz-types-selector.png)
Each of the available visualization types and available user controls are described below.
@@ -30,11 +30,11 @@ For information on adding and displaying annotations in graph views, see [Adding
The **Line Graph** view displays a time series in a line graph.
-
+
#### Line Graph Controls
-
+
Use the **Line Graph Controls** to specify the following:
@@ -53,18 +53,18 @@ Use the **Line Graph Controls** to specify the following:
#### Line Graph example
-
+
### Stacked Graph
The **Stacked Graph** view displays multiple time series bars as segments stacked on top of each other.
-
+
#### Stacked Graph Controls
-
+
Use the **Stacked Graph Controls** to specify the following:
@@ -83,18 +83,18 @@ Use the **Stacked Graph Controls** to specify the following:
#### Stacked Graph example
-
+
### Step-Plot Graph
The **Step-Plot Graph** view displays a time series in a staircase graph.
-
+
#### Step-Plot Graph Controls
-
+
Use the **Step-Plot Graph Controls** to specify the following:
@@ -111,7 +111,7 @@ Use the **Step-Plot Graph Controls** to specify the following:
#### Step-Plot Graph example
-
+
### Bar Graph
@@ -120,11 +120,11 @@ The **Bar Graph** view displays the specified time series using a bar chart.
To select this view, click the Bar Graph selector icon.
-
+
#### Bar Graph Controls
-
+
Use the **Bar Graph Controls** to specify the following:
@@ -141,7 +141,7 @@ Use the **Bar Graph Controls** to specify the following:
#### Bar Graph example
-
+
### Line Graph + Single Stat
@@ -150,11 +150,11 @@ The **Line Graph + Single Stat** view displays the specified time series in a li
To select this view, click the **Line Graph + Single Stat** view option.
-
+
#### Line Graph + Single Stat Controls
-
+
Use the **Line Graph + Single Stat Controls** to specify the following:
@@ -171,13 +171,13 @@ Use the **Line Graph + Single Stat Controls** to specify the following:
#### Line Graph + Single Stat example
-
+
### Single Stat
The **Single Stat** view displays the most recent value of the specified time series as a numerical value.
-
+
If a cell's query includes a [`GROUP BY` tag](/influxdb/latest/query_language/data_exploration/#group-by-tags) clause, Chronograf sorts the different [series](/influxdb/latest/concepts/glossary/#series) lexicographically and shows the most recent [field value](/influxdb/latest/concepts/glossary/#field-value) associated with the first series.
For example, if a query groups by the `name` [tag key](/influxdb/latest/concepts/glossary/#tag-key) and `name` has two [tag values](/influxdb/latest/concepts/glossary/#tag-value) (`chronelda` and `chronz`), Chronograf shows the most recent field value associated with the `chronelda` series.
@@ -203,11 +203,11 @@ The **Gauge** view displays the single value most recent value for a time series
To select this view, click the Gauge selector icon.
-
+
#### Gauge Controls
-
+
Use the **Gauge Controls** to specify the following:
@@ -221,17 +221,17 @@ Use the **Gauge Controls** to specify the following:
#### Gauge example
-
+
### Table
The **Table** panel displays the results of queries in a tabular view, which is sometimes easier to analyze than graph views of data.
-
+
#### Table Controls
-
+
Use the **Table Controls** to specify the following:
@@ -255,4 +255,4 @@ Use the **Table Controls** to specify the following:
#### Table view example
-
+
diff --git a/content/chronograf/v1.6/troubleshooting/frequently-asked-questions.md b/content/chronograf/v1.6/troubleshooting/frequently-asked-questions.md
index bf8a06faa..7303d7814 100644
--- a/content/chronograf/v1.6/troubleshooting/frequently-asked-questions.md
+++ b/content/chronograf/v1.6/troubleshooting/frequently-asked-questions.md
@@ -15,7 +15,7 @@ When you enter the InfluxDB HTTP bind address in the `Connection String` input,
If it is a data node, Chronograf automatically adds the `Meta Service Connection URL` input to the connection details form.
Enter the HTTP bind address of one of your cluster's meta nodes into that input and Chronograf takes care of the rest.
-
+
Note that the example above assumes that you do not have authentication enabled.
If you have authentication enabled, the form requires username and password information.
diff --git a/content/chronograf/v1.7/_index.md b/content/chronograf/v1.7/_index.md
index c53ca055e..1e472fefd 100644
--- a/content/chronograf/v1.7/_index.md
+++ b/content/chronograf/v1.7/_index.md
@@ -10,7 +10,7 @@ menu:
Chronograf is InfluxData's open source web application.
Use Chronograf with the other components of the [TICK stack](https://www.influxdata.com/products/) to visualize your monitoring data and easily create alerting and automation rules.
-
+
## Key features
diff --git a/content/chronograf/v1.7/administration/chrono-on-clusters.md b/content/chronograf/v1.7/administration/chrono-on-clusters.md
index 347682a40..24808dd2c 100644
--- a/content/chronograf/v1.7/administration/chrono-on-clusters.md
+++ b/content/chronograf/v1.7/administration/chrono-on-clusters.md
@@ -14,7 +14,7 @@ When you enter the InfluxDB HTTP bind address in the `Connection String` input,
If it is a data node, Chronograf automatically adds the `Meta Service Connection URL` input to the connection details form.
Enter the HTTP bind address of one of your cluster's meta nodes into that input and Chronograf takes care of the rest.
-
+
Note that the example above assumes that you do not have authentication enabled.
If you have authentication enabled, the form requires username and password information.
diff --git a/content/chronograf/v1.7/administration/creating-connections.md b/content/chronograf/v1.7/administration/creating-connections.md
index d2f5a0523..bc01964a2 100644
--- a/content/chronograf/v1.7/administration/creating-connections.md
+++ b/content/chronograf/v1.7/administration/creating-connections.md
@@ -23,10 +23,10 @@ To create an InfluxDB connection in the Chronograf UI:
1. Open Chronograf and click **Configuration** (wrench icon) in the navigation menu.
2. Click **Add Connection**.
- 
+ 
3. Enter values for the following fields:
- 
+ 
* **Connection URL**: Enter the hostname or IP address of the InfluxDB instance and the port. The field is prefilled with `http://localhost:8086`.
* **Connection Name**: Enter the name for this connection.
@@ -167,11 +167,11 @@ To create a Kapacitor connection using the Chronograf UI:
1. Open Chronograf and click **Configuration** (wrench icon) in the navigation menu.
2. Next to an existing [InfluxDB connection](#managing-influxdb-connections-using-the-chronograf-ui), click **Add Kapacitor Connection** if there are no existing Kapacitor connections or select **Add Kapacitor Connection** in the **Kapacitor Connection** dropdown list.
- 
+ 
3. In the **Connection Details** section, enter values for the following fields:
- 
+ 
* **Kapacitor URL**: Enter the hostname or IP address of the Kapacitor instance and the port. The field is prefilled with `http://localhost:9092`.
* **Name**: Enter the name for this connection.
diff --git a/content/chronograf/v1.7/administration/import-export-dashboards.md b/content/chronograf/v1.7/administration/import-export-dashboards.md
index be794cfff..5ce94796a 100644
--- a/content/chronograf/v1.7/administration/import-export-dashboards.md
+++ b/content/chronograf/v1.7/administration/import-export-dashboards.md
@@ -20,7 +20,7 @@ This allows you to recreate robust dashboards without having to manually configu
2. Hover over the dashboard you would like to export and click the "Export"
button that appears to the right.
-
+
This downloads a JSON file containing dashboard information including template variables,
cells and cell information such as the query, cell-sizing, color scheme, visualization type, etc.
@@ -35,13 +35,13 @@ cells and cell information such as the query, cell-sizing, color scheme, visuali
The newly imported dashboard will be included in your list of dashboards.
-
+
### Reconciling unmatched sources
If the data sources defined in the imported dashboard JSON file do not match any of your local sources,
you will have to reconcile each of the unmatched sources during the import process.
-
+
## Required user roles
Depending on the role of your user, there are some restrictions on importing and exporting dashboards:
diff --git a/content/chronograf/v1.7/administration/managing-influxdb-users.md b/content/chronograf/v1.7/administration/managing-influxdb-users.md
index 7c660cae6..fecfafba0 100644
--- a/content/chronograf/v1.7/administration/managing-influxdb-users.md
+++ b/content/chronograf/v1.7/administration/managing-influxdb-users.md
@@ -88,7 +88,7 @@ On the **Chronograf Admin** page:
* Change user passwords
* Assign admin and remove admin permissions to or from a user
-
+
InfluxDB users are either admin users or non-admin users.
See InfluxDB's [authentication and authorization](/influxdb/latest/administration/authentication_and_authorization/#user-types-and-privileges) documentation for more information about those user types.
@@ -129,7 +129,7 @@ On the `Admin` page:
* Create, edit, and delete roles
* Assign and remove roles to or from a user
-
+
### User types
@@ -306,4 +306,4 @@ For example, the image below contains three roles: `CREATOR`, `DESTROYER`, and `
`CREATOR` includes two permissions (`CreateDatbase` and `CreateUserAndRole`) and is assigned to one user (`chrononut`).
`DESTROYER` also includes two permissions (`DropDatabase` and `DropData`) and is assigned to two users (`chrononut` and `chronelda`).
-
+
diff --git a/content/chronograf/v1.7/administration/transition-web-admin-interface.md b/content/chronograf/v1.7/administration/transition-web-admin-interface.md
index 60dfc9e4a..3d851f44d 100644
--- a/content/chronograf/v1.7/administration/transition-web-admin-interface.md
+++ b/content/chronograf/v1.7/administration/transition-web-admin-interface.md
@@ -25,7 +25,7 @@ The following sections describe the Chronograf features that relate to the web a
In the web admin interface, users chose the target database in the top right corner and selected from a set of query templates in the `Query Templates` dropdown.
The templates included queries with no user-provided values (example: [`SHOW MEASUREMENTS`](/influxdb/latest/query_language/schema_exploration/#show-measurements)) and queries with user-provided values (example: [`SHOW TAG KEYS FROM "
+
The log viewer provides a detailed histogram showing the time-based distribution of log entries color-coded by log severity.
It also includes a live stream of logs that can be searched, filtered, and paused to analyze specific time ranges.
Logs are pulled from the `syslog` measurement.
_Other log inputs and alternate log measurement options will be available in future updates._
-
+
### Searching and filtering logs
Search for logs using keywords or regular expressions.
@@ -34,7 +34,7 @@ Any tag values included with the log entry can be used as a filter.
You can also use search operators to filter your results. For example, if you want to find results with a severity of critical that don't mention RSS, you can enter: `severity == crit` and `-RSS`.
-
+
> **Note:** The log search field is case-sensitive.
@@ -45,13 +45,13 @@ In the log viewer, you can select time ranges from which to view logs.
By default, logs are streamed and displayed relative to "now," but it is possible to view logs from a past window of time.
timeframe selection allows you to go to to a specific event and see logs for a time window both preceding and following that event. The default window is one minute, meaning the graph shows logs from thirty seconds before and the target time. Click the dropdown menu change the window.
-
+
## Configuring the log viewer
The log viewer can be customized to fit your specific needs.
Open the log viewer configuration options by clicking the gear button in the top right corner of the log viewer. Once done, click **Save** to apply the changes.
-
+
### Severity colors
Every log severity is assigned a color which is used in the display of log entries.
@@ -67,9 +67,9 @@ Below are the options and how they appear in the log table:
| Severity Format | Display |
| --------------- |:------- |
-| Dot | 
|
-| Dot + Text | 
|
-| Text | 
|
+| Dot | |
+| Dot + Text | |
+| Text | |
### Truncate or wrap log messages
By default, text in Log Viewer columns is truncated if it exceeds the column width. You can choose to wrap the text instead to display the full content of each cell.
@@ -82,6 +82,6 @@ To copy the complete, untruncated log message, select the message cell and click
An incredibly powerful way to analyze log data is by creating dashboards that include log data.
This is possible by using the [Table visualization type](/chronograf/v1.7/guides/visualization-types/#table) to display log data in your dashboard.
-
+
This type of visualization allows you to quickly identify anomalies in other metrics and see logs associated with those anomalies.
diff --git a/content/chronograf/v1.7/guides/annotations.md b/content/chronograf/v1.7/guides/annotations.md
index bf66fecb9..9158894c1 100644
--- a/content/chronograf/v1.7/guides/annotations.md
+++ b/content/chronograf/v1.7/guides/annotations.md
@@ -20,7 +20,7 @@ The following screenshot of five graph views displays annotations for a single p
The text and timestamp for the single point in time can be seem above the annotation line in the graph view on the lower right.
The annotation displays "`Deploy v3.8.1-2`" and the time "`2018/28/02 15:59:30:00`".
-
+
**To add an annotation using the Chronograf user interface:**
diff --git a/content/chronograf/v1.7/guides/cloning-in-ui.md b/content/chronograf/v1.7/guides/cloning-in-ui.md
index 35568951d..64f9a7342 100644
--- a/content/chronograf/v1.7/guides/cloning-in-ui.md
+++ b/content/chronograf/v1.7/guides/cloning-in-ui.md
@@ -18,11 +18,11 @@ Dashboards in Chronograf can be cloned (or copied) to be used to create a dashbo
1. On the **Dashboards** page, hover your cursor over the listing of the dashboard that you want to clone and click the **Clone** button that appears.
-
+
The cloned dashboard opens and displays the name of the original dashboard with `(clone)` after it.
-
+
You can now change the dashboard name and customize the dashboard.
@@ -34,10 +34,10 @@ Cells in Chronograf dashboards can be cloned, or copied, to quickly create a cel
1. On the dashboard cell that you want to make a copy of, click the **Clone** icon and then confirm by clicking **Clone Cell**.
-
+
2. The cloned cell appears in the dashboard displaying the nameof the original cell with `(clone)` after it.
-
+
You can now change the cell name and customize the cell.
diff --git a/content/chronograf/v1.7/guides/configuring-alert-endpoints.md b/content/chronograf/v1.7/guides/configuring-alert-endpoints.md
index f29c8838b..df7169a41 100644
--- a/content/chronograf/v1.7/guides/configuring-alert-endpoints.md
+++ b/content/chronograf/v1.7/guides/configuring-alert-endpoints.md
@@ -253,7 +253,7 @@ Click **Add Another Config** to add additional Slack alert endpoints. Each addit
Configure Chronograf to send alert messages to an existing Telegram bot.
The sections below describe each configuration option.
-
+
#### Telegram bot
diff --git a/content/chronograf/v1.7/guides/create-a-dashboard.md b/content/chronograf/v1.7/guides/create-a-dashboard.md
index fcd2a8f20..915541ec7 100644
--- a/content/chronograf/v1.7/guides/create-a-dashboard.md
+++ b/content/chronograf/v1.7/guides/create-a-dashboard.md
@@ -17,7 +17,7 @@ Chronograf offers a complete dashboard solution for visualizing your data and mo
By the end of this guide, you'll be aware of the tools available to you for creating dashboards similar to this example:
-
+
## Requirements
@@ -39,7 +39,7 @@ Click **Name This Dashboard** and type a new name. In this guide, "ChronoDash" i
In the first cell, titled "Untitled Cell", click **Edit**
to open the cell editor mode.
-
+
### Step 3: Create your query
@@ -54,13 +54,13 @@ Those defaults are configurable using the query builder or by manually editing t
In addition, the time range (`:dashboardTime:`) is [configurable on the dashboard](#step-6-configure-your-dashboard).
-
+
### Step 4: Choose your visualization type
Chronograf supports many different [visualization types](/chronograf/latest/guides/visualization-types/). To choose a visualization type, click **Visualization** and select **Step-Plot Graph**.
-
+
### Step 5: Save your cell
Click **Save** (the green checkmark icon) to save your cell.
@@ -95,10 +95,10 @@ Now, you're ready to experiment and complete your dashboard by creating, editing
Select from a variety of dashboard templates to import and customize based on which Telegraf plugins you have enabled, such as the following examples:
-
-
-
-
+
+
+
+
**To import dashboard templates:**
@@ -106,7 +106,7 @@ Select from a variety of dashboard templates to import and customize based on wh
2. In the **InfluxDB Connection** window, enter or verify your connection details and click **Add** or **Update Connection**.
3. In the **Dashboards** window, select from the available dashboard templates to import based on which Telegraf plugins you have enabled.
- 
+ 
4. Click **Create (x) Dashboards**.
5. Edit, clone, or configure the dashboards as needed.
diff --git a/content/chronograf/v1.7/guides/create-alert-rules.md b/content/chronograf/v1.7/guides/create-alert-rules.md
index f072b1f0c..bf517385a 100644
--- a/content/chronograf/v1.7/guides/create-alert-rules.md
+++ b/content/chronograf/v1.7/guides/create-alert-rules.md
@@ -38,12 +38,12 @@ See the [Configuring Kapacitor Event Handlers](/chronograf/latest/guides/configu
Navigate to the **Manage Tasks** page under **Alerting** in the left navigation, then click **+ Build Alert Rule** in the top right corner.
-
+
The **Manage Tasks** page is used to create and edit your Chronograf alert rules.
The steps below guide you through the process of creating a Chronograf alert rule.
-
+
### Step 1: Name the alert rule
@@ -72,7 +72,7 @@ Navigate through databases, measurements, fields, and tags to select the relevan
In this example, select the `telegraf` [database](/influxdb/latest/concepts/glossary/#database), the `autogen` [retention policy](/influxdb/latest/concepts/glossary/#retention-policy-rp), the `cpu` [measurement](/influxdb/latest/concepts/glossary/#measurement), and the `usage_idle` [field](/influxdb/latest/concepts/glossary/#field).
-
+
### Step 4: Define the rule condition
@@ -80,7 +80,7 @@ Define the threshold condition.
Condition options are determined by the [alert type](#step-2-select-the-alert-type).
For this example, the alert conditions are if `usage_idle` is less than `80`.
-
+
The graph shows a preview of the relevant data and the threshold number.
By default, the graph shows data from the past 15 minutes.
@@ -98,7 +98,7 @@ Each handler has unique configurable options.
For this example, choose the **slack** alert handler and enter the desired options.
-
+
> Multiple alert handlers can be added to send alerts to multiple endpoints.
@@ -111,7 +111,7 @@ As you type your alert message, clicking the data templates will insert them at
In this example, use the alert message, `Your idle CPU usage is {{.Level}} at {{ index .Fields "value" }}.`.
-
+
*View the Kapacitor documentation for more information about [message template data](/kapacitor/latest/nodes/alert_node/#message).*
@@ -120,7 +120,7 @@ In this example, use the alert message, `Your idle CPU usage is {{.Level}} at {{
Click **Save Rule** in the top right corner and navigate to the **Manage Tasks** page to see your rule.
Notice that you can easily enable and disable the rule by toggling the checkbox in the **Enabled** column.
-
+
Next, move on to the section below to experience your alert rule in action.
@@ -149,10 +149,10 @@ Assuming the first step was successful, `#ohnos` should reveal at least two aler
* The first alert message indicates that your idle CPU usage was `CRITICAL`, meaning it dipped below `80%`.
* The second alert message indicates that your idle CPU usage returned to an `OK` level of `80%` or above.
-
+
You can also see alerts on the **Alert History** page available under **Alerting** in the left navigation.
-
+
That's it! You've successfully used Chronograf to configure an alert rule to monitor your idle CPU usage and send notifications to Slack.
diff --git a/content/chronograf/v1.7/guides/dashboard-template-variables.md b/content/chronograf/v1.7/guides/dashboard-template-variables.md
index f3bcd558a..283efe99d 100644
--- a/content/chronograf/v1.7/guides/dashboard-template-variables.md
+++ b/content/chronograf/v1.7/guides/dashboard-template-variables.md
@@ -25,7 +25,7 @@ You can use either [predefined template variables](#predefined-template-variable
or [custom template variables](#create-custom-template-variables).
Variable values are then selected in your dashboard user-interface (UI).
-
+
## Predefined template variables
Chronograf includes predefined template variables controlled by elements in the Chrongraf UI.
@@ -38,7 +38,7 @@ These template variables can be used in any of your cells' queries.
### dashboardTime
The `:dashboardTime:` template variable is controlled by the "time" dropdown in your Chronograf dashboard.
-
+
If using relative times, it represents the time offset specified in the dropdown (-5m, -15m, -30m, etc.) and assumes time is relative to "now".
If using absolute times defined by the date picker, `:dashboardTime:` is populated with lower threshold.
@@ -56,7 +56,7 @@ WHERE time > :dashboardTime:
### upperDashboardTime
The `:upperDashboardTime:` template variable is defined by the upper time limit specified using the date picker.
-
+
It will inherit `now()` when using relative time frames or the upper time limit when using absolute timeframes.
@@ -69,7 +69,7 @@ WHERE time > :dashboardTime: AND time < :upperDashboardTime:
### interval
The `:interval:` template variable is defined by the interval dropdown in the Chronograf dashboard.
-
+
In cell queries, it should be used in the `GROUP BY time()` clause that accompanies aggregate functions:
@@ -95,7 +95,7 @@ To create a template variable:
If using the CSV or Map types, upload or input the CSV with the desired values in the appropriate format then select a default value.
5. Click **Create**.
-
+
Once created, the template variable can be used in any of your cell's queries or titles
and a dropdown for the variable will be included at the top of your dashboard.
@@ -251,7 +251,7 @@ key3,value3
key4,value4
```
-
+
> If values are meant to be used as string field values, wrap them in single quote ([required by InfluxQL](/influxdb/latest/troubleshooting/frequently-asked-questions/#when-should-i-single-quote-and-when-should-i-double-quote-in-queries)). This only pertains to values. String keys do not matter.
@@ -285,7 +285,7 @@ The customer names would populate your template variable dropdown rather than th
Vary part of a query with a customized meta query that pulls a specific array of values from InfluxDB.
These variables allow you to pull a highly customized array of potential values and offer advanced functionality such as [filtering values based on other template variables](#filtering-template-variables-with-other-template-variables).
-
+
_**Example custom meta query variable in a cell query**_
```sql
@@ -330,7 +330,7 @@ For example, let's say you want to list all the field keys associated with a mea
1. Create a template variable named `:measurementVar:` _(the name "measurement" is [reserved]( #reserved-variable-names))_ that uses the [Measurements](#measurements) variable type to pull in all measurements from the `telegraf` database.
- 
+
2. Create a template variable named `:fieldKey:` that uses the [custom meta query](#custom-meta-query) variable type.
The following meta query pulls a list of field keys based on the existing `:measurementVar:` template variable.
@@ -339,7 +339,7 @@ The following meta query pulls a list of field keys based on the existing `:meas
SHOW FIELD KEYS ON telegraf FROM :measurementVar:
```
- 
+
3. Create a new dashboard cell that uses the `:fieldKey:` and `:measurementVar` template variables in its query.
@@ -349,7 +349,7 @@ The following meta query pulls a list of field keys based on the existing `:meas
The resulting dashboard will work like this:
-
+
### Defining template variables in the URL
Chronograf uses URL query parameters (also known as query string parameters) to set both display options and template variables in the URL.
diff --git a/content/chronograf/v1.7/guides/monitoring-influxenterprise-clusters.md b/content/chronograf/v1.7/guides/monitoring-influxenterprise-clusters.md
index e2f81f207..991eff573 100644
--- a/content/chronograf/v1.7/guides/monitoring-influxenterprise-clusters.md
+++ b/content/chronograf/v1.7/guides/monitoring-influxenterprise-clusters.md
@@ -32,7 +32,7 @@ Chronograf and the other components of the TICK stack are supported on several o
Before we begin, here's an overview of the final monitoring setup:
-
+
The diagram above shows an InfluxEnterprise cluster that consists of three meta nodes (M) and three data nodes (D).
Each data node has its own [Telegraf](/telegraf/latest/) instance (T).
@@ -233,7 +233,7 @@ Chronograf can be downloaded from the [InfluxData downloads page](https://portal
To access Chronograf, go to http://localhost:8888.
The welcome page includes instructions for connecting Chronograf to that instance.
-
+
For the `Connection String`, enter the hostname or IP of your InfluxDB OSS instance, and be sure to include the default port: `8086`.
Next, name your data source; this can be anything you want.
@@ -245,17 +245,17 @@ Chronograf works with the Telegraf data in your InfluxDB OSS instance.
The `Host List` page shows your data node's hostnames, their statuses, CPU usage, load, and their configured applications.
In this case, you've only enabled the system stats input plugin so `system` is the single application that appears in the `Apps` column.
-
+
Click `system` to see the Chronograf canned dashboard for that application.
Keep an eye on your data nodes by viewing that dashboard for each hostname:
-
+
Next, check out the Data Explorer to create a customized graph with the monitoring data.
In the image below, the Chronograf query editor is used to visualize the idle CPU usage data for each data node:
-
+
Create more customized graphs and save them to a dashboard on the Dashboard page in Chronograf.
See the [Creating Chronograf dashboards](/chronograf/latest/guides/create-a-dashboard/) guide for more information.
diff --git a/content/chronograf/v1.7/guides/presentation-mode.md b/content/chronograf/v1.7/guides/presentation-mode.md
index 8b31befb5..491b46bc8 100644
--- a/content/chronograf/v1.7/guides/presentation-mode.md
+++ b/content/chronograf/v1.7/guides/presentation-mode.md
@@ -13,7 +13,7 @@ Presentation mode allows you to view Chronograf in full screen, hiding the left
## Entering presentation mode manually
To enter presentation mode manually, click the icon in the upper right:
-
+
To exit presentation mode, press `ESC`.
diff --git a/content/chronograf/v1.7/guides/querying-data.md b/content/chronograf/v1.7/guides/querying-data.md
index 73d7b1fda..c4e73200f 100644
--- a/content/chronograf/v1.7/guides/querying-data.md
+++ b/content/chronograf/v1.7/guides/querying-data.md
@@ -11,7 +11,7 @@ Explore and visualize your data in the **Data Explorer**. For both InfluxQL and
To open the **Data Explorer**, click the **Explore** icon in the navigation bar:
-
+
## Select local time or UTC (Coordinated Universal Time)
@@ -47,7 +47,7 @@ Flux is InfluxData's new functional data scripting language designed for queryin
* To get started with your query, click the **Script Wizard**. In the wizard, you can select a bucket, measurement, fields and an aggregate.
- 
+ 
For example, if you make the above selections, the wizard inserts the following script:
@@ -75,9 +75,9 @@ To add your query and graph to a dashboard:
1. Click **Send to Dashboard** in the upper right.
2. In the **Target Dashboard(s)** dropdown, select at least one existing dashboard to send the cell to, or select **Send to a New Dashboard**.
- 
+ 
3. Enter a name for the new cell and, if you created a new dashboard, the new dashboard.
4. Click **Send to Dashboard(s)**.
- 
+ 
diff --git a/content/chronograf/v1.7/guides/visualization-types.md b/content/chronograf/v1.7/guides/visualization-types.md
index 38589bce8..006062f34 100644
--- a/content/chronograf/v1.7/guides/visualization-types.md
+++ b/content/chronograf/v1.7/guides/visualization-types.md
@@ -10,7 +10,7 @@ menu:
Chronograf's dashboard views support the following visualization types, which can be selected in the **Visualization Type** selection view of the [Data Explorer](/chronograf/latest/querying-data) .
-[Visualization Type selector](/img/chronograf/chrono-viz-types-selector.png)
+[Visualization Type selector](/img/chronograf/1-6-viz-types-selector.png)
Each of the available visualization types and available user controls are described below.
@@ -31,11 +31,11 @@ For information on adding and displaying annotations in graph views, see [Adding
The **Line Graph** view displays a time series in a line graph.
-
+
#### Line Graph Controls
-
+
Use the **Line Graph Controls** to specify the following:
@@ -54,18 +54,18 @@ Use the **Line Graph Controls** to specify the following:
#### Line Graph example
-
+
### Stacked Graph
The **Stacked Graph** view displays multiple time series bars as segments stacked on top of each other.
-
+
#### Stacked Graph Controls
-
+
Use the **Stacked Graph Controls** to specify the following:
@@ -84,18 +84,18 @@ Use the **Stacked Graph Controls** to specify the following:
#### Stacked Graph example
-
+
### Step-Plot Graph
The **Step-Plot Graph** view displays a time series in a staircase graph.
-
+
#### Step-Plot Graph Controls
-
+
Use the **Step-Plot Graph Controls** to specify the following:
@@ -112,7 +112,7 @@ Use the **Step-Plot Graph Controls** to specify the following:
#### Step-Plot Graph example
-
+
### Bar Graph
@@ -121,11 +121,11 @@ The **Bar Graph** view displays the specified time series using a bar chart.
To select this view, click the Bar Graph selector icon.
-
+
#### Bar Graph Controls
-
+
Use the **Bar Graph Controls** to specify the following:
@@ -142,7 +142,7 @@ Use the **Bar Graph Controls** to specify the following:
#### Bar Graph example
-
+
### Line Graph + Single Stat
@@ -151,11 +151,11 @@ The **Line Graph + Single Stat** view displays the specified time series in a li
To select this view, click the **Line Graph + Single Stat** view option.
-
+
#### Line Graph + Single Stat Controls
-
+
Use the **Line Graph + Single Stat Controls** to specify the following:
@@ -172,13 +172,13 @@ Use the **Line Graph + Single Stat Controls** to specify the following:
#### Line Graph + Single Stat example
-
+
### Single Stat
The **Single Stat** view displays the most recent value of the specified time series as a numerical value.
-
+
If a cell's query includes a [`GROUP BY` tag](/influxdb/latest/query_language/data_exploration/#group-by-tags) clause, Chronograf sorts the different [series](/influxdb/latest/concepts/glossary/#series) lexicographically and shows the most recent [field value](/influxdb/latest/concepts/glossary/#field-value) associated with the first series.
For example, if a query groups by the `name` [tag key](/influxdb/latest/concepts/glossary/#tag-key) and `name` has two [tag values](/influxdb/latest/concepts/glossary/#tag-value) (`chronelda` and `chronz`), Chronograf shows the most recent field value associated with the `chronelda` series.
@@ -204,11 +204,11 @@ The **Gauge** view displays the single value most recent value for a time series
To select this view, click the Gauge selector icon.
-
+
#### Gauge Controls
-
+
Use the **Gauge Controls** to specify the following:
@@ -222,17 +222,17 @@ Use the **Gauge Controls** to specify the following:
#### Gauge example
-
+
### Table
The **Table** panel displays the results of queries in a tabular view, which is sometimes easier to analyze than graph views of data.
-
+
#### Table Controls
-
+
Use the **Table Controls** to specify the following:
@@ -256,17 +256,17 @@ Use the **Table Controls** to specify the following:
#### Table view example
-
+
### Note
The **Note** panel displays Markdown-formatted text with your graph.
-
+
#### Note Controls
-
+
Enter your text in the **Add a Note** panel, using Markdown to format the text.
@@ -274,4 +274,4 @@ Enable the **Display note in cell when query returns no results** option to disp
#### Note view example
-
+
diff --git a/content/chronograf/v1.7/troubleshooting/frequently-asked-questions.md b/content/chronograf/v1.7/troubleshooting/frequently-asked-questions.md
index 434ae5439..ea166032c 100644
--- a/content/chronograf/v1.7/troubleshooting/frequently-asked-questions.md
+++ b/content/chronograf/v1.7/troubleshooting/frequently-asked-questions.md
@@ -15,7 +15,7 @@ When you enter the InfluxDB HTTP bind address in the `Connection String` input,
If it is a data node, Chronograf automatically adds the `Meta Service Connection URL` input to the connection details form.
Enter the HTTP bind address of one of your cluster's meta nodes into that input and Chronograf takes care of the rest.
-
+
Note that the example above assumes that you do not have authentication enabled.
If you have authentication enabled, the form requires username and password information.
diff --git a/content/chronograf/v1.8/_index.md b/content/chronograf/v1.8/_index.md
index c4acfcc73..41c31dfbb 100644
--- a/content/chronograf/v1.8/_index.md
+++ b/content/chronograf/v1.8/_index.md
@@ -10,7 +10,7 @@ menu:
Chronograf is InfluxData's open source web application.
Use Chronograf with the other components of the [TICK stack](https://www.influxdata.com/products/) to visualize your monitoring data and easily create alerting and automation rules.
-
+
## Key features
diff --git a/content/chronograf/v1.8/administration/chrono-on-clusters.md b/content/chronograf/v1.8/administration/chrono-on-clusters.md
index e8b765795..15ce62cf6 100644
--- a/content/chronograf/v1.8/administration/chrono-on-clusters.md
+++ b/content/chronograf/v1.8/administration/chrono-on-clusters.md
@@ -14,7 +14,7 @@ When you enter the InfluxDB HTTP bind address in the `Connection String` input,
If it is a data node, Chronograf automatically adds the `Meta Service Connection URL` input to the connection details form.
Enter the HTTP bind address of one of your cluster's meta nodes into that input and Chronograf takes care of the rest.
-
+
Note that the example above assumes that you do not have authentication enabled.
If you have authentication enabled, the form requires username and password information.
diff --git a/content/chronograf/v1.8/administration/create-high-availability.md b/content/chronograf/v1.8/administration/create-high-availability.md
index ea0c0d36d..95f14f50f 100644
--- a/content/chronograf/v1.8/administration/create-high-availability.md
+++ b/content/chronograf/v1.8/administration/create-high-availability.md
@@ -17,7 +17,7 @@ Have an existing Chronograf configuration store that you want to use with a Chro
## Architecture
-
+{{< svg "/static/img/chronograf/1-8-ha-architecture.svg" >}}
## Install and start etcd
diff --git a/content/chronograf/v1.8/administration/creating-connections.md b/content/chronograf/v1.8/administration/creating-connections.md
index 59aaaf067..add18e874 100644
--- a/content/chronograf/v1.8/administration/creating-connections.md
+++ b/content/chronograf/v1.8/administration/creating-connections.md
@@ -23,10 +23,10 @@ To create an InfluxDB connection in the Chronograf UI:
1. Open Chronograf and click **Configuration** (wrench icon) in the navigation menu.
2. Click **Add Connection**.
- 
+ 
3. Enter values for the following fields:
- 
+
* **Connection URL**: Enter the hostname or IP address of the InfluxDB instance and the port. The field is prefilled with `http://localhost:8086`.
* **Connection Name**: Enter the name for this connection.
@@ -167,11 +167,11 @@ To create a Kapacitor connection using the Chronograf UI:
1. Open Chronograf and click **Configuration** (wrench icon) in the navigation menu.
2. Next to an existing [InfluxDB connection](#managing-influxdb-connections-using-the-chronograf-ui), click **Add Kapacitor Connection** if there are no existing Kapacitor connections or select **Add Kapacitor Connection** in the **Kapacitor Connection** dropdown list.
- 
+ 
3. In the **Connection Details** section, enter values for the following fields:
- 
+
* **Kapacitor URL**: Enter the hostname or IP address of the Kapacitor instance and the port. The field is prefilled with `http://localhost:9092`.
* **Name**: Enter the name for this connection.
diff --git a/content/chronograf/v1.8/administration/import-export-dashboards.md b/content/chronograf/v1.8/administration/import-export-dashboards.md
index ca5ab10ab..ed59bf415 100644
--- a/content/chronograf/v1.8/administration/import-export-dashboards.md
+++ b/content/chronograf/v1.8/administration/import-export-dashboards.md
@@ -20,7 +20,7 @@ This allows you to recreate robust dashboards without having to manually configu
2. Hover over the dashboard you would like to export and click the "Export"
button that appears to the right.
-
+
This downloads a JSON file containing dashboard information including template variables,
cells and cell information such as the query, cell-sizing, color scheme, visualization type, etc.
@@ -35,13 +35,13 @@ cells and cell information such as the query, cell-sizing, color scheme, visuali
The newly imported dashboard will be included in your list of dashboards.
-
+
### Reconciling unmatched sources
If the data sources defined in the imported dashboard JSON file do not match any of your local sources,
you will have to reconcile each of the unmatched sources during the import process.
-
+
## Required user roles
Depending on the role of your user, there are some restrictions on importing and exporting dashboards:
diff --git a/content/chronograf/v1.8/administration/managing-influxdb-users.md b/content/chronograf/v1.8/administration/managing-influxdb-users.md
index c32965bf1..6ca3b4b74 100644
--- a/content/chronograf/v1.8/administration/managing-influxdb-users.md
+++ b/content/chronograf/v1.8/administration/managing-influxdb-users.md
@@ -88,7 +88,7 @@ On the **Chronograf Admin** page:
* Change user passwords
* Assign admin and remove admin permissions to or from a user
-
+
InfluxDB users are either admin users or non-admin users.
See InfluxDB's [authentication and authorization](/influxdb/latest/administration/authentication_and_authorization/#user-types-and-privileges) documentation for more information about those user types.
@@ -129,7 +129,7 @@ On the `Admin` page:
* Create, edit, and delete roles
* Assign and remove roles to or from a user
-
+
### User types
@@ -306,4 +306,4 @@ For example, the image below contains three roles: `CREATOR`, `DESTROYER`, and `
`CREATOR` includes two permissions (`CreateDatbase` and `CreateUserAndRole`) and is assigned to one user (`chrononut`).
`DESTROYER` also includes two permissions (`DropDatabase` and `DropData`) and is assigned to two users (`chrononut` and `chronelda`).
-
+
diff --git a/content/chronograf/v1.8/administration/upgrading.md b/content/chronograf/v1.8/administration/upgrading.md
index 334c74e71..2b13a9210 100644
--- a/content/chronograf/v1.8/administration/upgrading.md
+++ b/content/chronograf/v1.8/administration/upgrading.md
@@ -16,4 +16,4 @@ If you're upgrading from Chronograf 1.4 or later, [download and install](https:/
> ***Note:*** Installing a new version of Chronograf automatically clears the localStorage settings.
-After upgrading, see [Getting Started](/chronograf/latest/introduction/getting-started/) to get up and running.
\ No newline at end of file
+After upgrading, see [Getting Started](/chronograf/latest/introduction/getting-started/) to get up and running.
diff --git a/content/chronograf/v1.8/guides/advanced-kapacitor.md b/content/chronograf/v1.8/guides/advanced-kapacitor.md
index c9fe23458..38c982745 100644
--- a/content/chronograf/v1.8/guides/advanced-kapacitor.md
+++ b/content/chronograf/v1.8/guides/advanced-kapacitor.md
@@ -31,7 +31,7 @@ In the Databases tab:
#### Step 1: Locate the `chronograf` database and click on the infinity symbol (∞)
-
+
#### Step 2: Enter a different duration
@@ -50,7 +50,7 @@ Those alerts no longer appear in your InfluxDB instance or on Chronograf's Alert
Looking at the image below and assuming that the current time is 19:00 on April 27, 2017, only the first three alerts would appear in your alert history; they occurred within the previous hour (18:00 through 19:00).
The fourth alert, which occurred on the same day at 16:58:50, is outside the previous hour and would no longer appear in the InfluxDB `chronograf` database or on the Chronograf Alert History page.
-
+
## TICKscript management
@@ -69,4 +69,4 @@ You cannot edit pre-existing tasks on the Chronograf Alert Rules page.
The `mytick` task in the image below is a pre-existing task; its name appears on the Alert Rules page but you cannot click on it or edit its TICKscript in the interface.
Currently, you must manually edit your existing tasks and TICKscripts on your machine.
-
+
diff --git a/content/chronograf/v1.8/guides/analyzing-logs.md b/content/chronograf/v1.8/guides/analyzing-logs.md
index 338e63b93..f56d87bc0 100644
--- a/content/chronograf/v1.8/guides/analyzing-logs.md
+++ b/content/chronograf/v1.8/guides/analyzing-logs.md
@@ -18,14 +18,14 @@ Logs data is a first class citizen in InfluxDB and is populated using available
## Viewing logs in Chronograf
Chronograf has a dedicated log viewer accessed by clicking the **Log Viewer** button in the left navigation.
-
+
The log viewer provides a detailed histogram showing the time-based distribution of log entries color-coded by log severity.
It also includes a live stream of logs that can be searched, filtered, and paused to analyze specific time ranges.
Logs are pulled from the `syslog` measurement.
_Other log inputs and alternate log measurement options will be available in future updates._
-
+
### Searching and filtering logs
Search for logs using keywords or regular expressions.
@@ -34,7 +34,7 @@ Any tag values included with the log entry can be used as a filter.
You can also use search operators to filter your results. For example, if you want to find results with a severity of critical that don't mention RSS, you can enter: `severity == crit` and `-RSS`.
-
+
> **Note:** The log search field is case-sensitive.
@@ -45,13 +45,13 @@ In the log viewer, you can select time ranges from which to view logs.
By default, logs are streamed and displayed relative to "now," but it is possible to view logs from a past window of time.
timeframe selection allows you to go to to a specific event and see logs for a time window both preceding and following that event. The default window is one minute, meaning the graph shows logs from thirty seconds before and the target time. Click the dropdown menu change the window.
-
+
## Configuring the log viewer
The log viewer can be customized to fit your specific needs.
Open the log viewer configuration options by clicking the gear button in the top right corner of the log viewer. Once done, click **Save** to apply the changes.
-
+
### Severity colors
Every log severity is assigned a color which is used in the display of log entries.
@@ -67,9 +67,9 @@ Below are the options and how they appear in the log table:
| Severity Format | Display |
| --------------- |:------- |
-| Dot | 
|
-| Dot + Text | 
|
-| Text | 
|
+| Dot | |
+| Dot + Text | |
+| Text | |
### Truncate or wrap log messages
By default, text in Log Viewer columns is truncated if it exceeds the column width. You can choose to wrap the text instead to display the full content of each cell.
@@ -82,6 +82,6 @@ To copy the complete, untruncated log message, select the message cell and click
An incredibly powerful way to analyze log data is by creating dashboards that include log data.
This is possible by using the [Table visualization type](/chronograf/v1.8/guides/visualization-types/#table) to display log data in your dashboard.
-
+
This type of visualization allows you to quickly identify anomalies in other metrics and see logs associated with those anomalies.
diff --git a/content/chronograf/v1.8/guides/annotations.md b/content/chronograf/v1.8/guides/annotations.md
index 9710ef233..d0d300fc6 100644
--- a/content/chronograf/v1.8/guides/annotations.md
+++ b/content/chronograf/v1.8/guides/annotations.md
@@ -20,7 +20,7 @@ The following screenshot of five graph views displays annotations for a single p
The text and timestamp for the single point in time can be seem above the annotation line in the graph view on the lower right.
The annotation displays "`Deploy v3.8.1-2`" and the time "`2018/28/02 15:59:30:00`".
-
+
**To add an annotation using the Chronograf user interface:**
diff --git a/content/chronograf/v1.8/guides/cloning-in-ui.md b/content/chronograf/v1.8/guides/cloning-in-ui.md
index f193278af..ea94831f5 100644
--- a/content/chronograf/v1.8/guides/cloning-in-ui.md
+++ b/content/chronograf/v1.8/guides/cloning-in-ui.md
@@ -18,11 +18,11 @@ Dashboards in Chronograf can be cloned (or copied) to be used to create a dashbo
1. On the **Dashboards** page, hover your cursor over the listing of the dashboard that you want to clone and click the **Clone** button that appears.
-
+
The cloned dashboard opens and displays the name of the original dashboard with `(clone)` after it.
-
+
You can now change the dashboard name and customize the dashboard.
@@ -34,10 +34,10 @@ Cells in Chronograf dashboards can be cloned, or copied, to quickly create a cel
1. On the dashboard cell that you want to make a copy of, click the **Clone** icon and then confirm by clicking **Clone Cell**.
-
+
2. The cloned cell appears in the dashboard displaying the nameof the original cell with `(clone)` after it.
-
+
You can now change the cell name and customize the cell.
diff --git a/content/chronograf/v1.8/guides/configuring-alert-endpoints.md b/content/chronograf/v1.8/guides/configuring-alert-endpoints.md
index 20ad96738..a9f77d360 100644
--- a/content/chronograf/v1.8/guides/configuring-alert-endpoints.md
+++ b/content/chronograf/v1.8/guides/configuring-alert-endpoints.md
@@ -253,7 +253,7 @@ Click **Add Another Config** to add additional Slack alert endpoints. Each addit
Configure Chronograf to send alert messages to an existing Telegram bot.
The sections below describe each configuration option.
-
+
#### Telegram bot
diff --git a/content/chronograf/v1.8/guides/create-a-dashboard.md b/content/chronograf/v1.8/guides/create-a-dashboard.md
index 88f523c7e..98570ee80 100644
--- a/content/chronograf/v1.8/guides/create-a-dashboard.md
+++ b/content/chronograf/v1.8/guides/create-a-dashboard.md
@@ -16,7 +16,7 @@ Chronograf offers a complete dashboard solution for visualizing your data and mo
By the end of this guide, you'll be aware of the tools available to you for creating dashboards similar to this example:
-
+
## Requirements
@@ -38,7 +38,7 @@ Click **Name This Dashboard** and type a new name. In this guide, "ChronoDash" i
In the first cell, titled "Untitled Cell", click **Edit**
to open the cell editor mode.
-
+
### Step 3: Create your query
@@ -53,13 +53,13 @@ Those defaults are configurable using the query builder or by manually editing t
In addition, the time range (`:dashboardTime:` and `:upperDashboardTime:`) are [configurable on the dashboard](#step-6-configure-your-dashboard).
-
+
### Step 4: Choose your visualization type
Chronograf supports many different [visualization types](/chronograf/latest/guides/visualization-types/). To choose a visualization type, click **Visualization** and select **Step-Plot Graph**.
-
+
### Step 5: Save your cell
@@ -102,10 +102,10 @@ Now, you're ready to experiment and complete your dashboard by creating, editing
Select from a variety of dashboard templates to import and customize based on which Telegraf plugins you have enabled, such as the following examples:
-
-
-
-
+
+
+
+
**To import dashboard templates:**
@@ -113,7 +113,7 @@ Select from a variety of dashboard templates to import and customize based on wh
2. In the **InfluxDB Connection** window, enter or verify your connection details and click **Add** or **Update Connection**.
3. In the **Dashboards** window, select from the available dashboard templates to import based on which Telegraf plugins you have enabled.
- 
+
4. Click **Create (x) Dashboards**.
5. Edit, clone, or configure the dashboards as needed.
diff --git a/content/chronograf/v1.8/guides/create-alert-rules.md b/content/chronograf/v1.8/guides/create-alert-rules.md
index d6c9eeec0..396da67bf 100644
--- a/content/chronograf/v1.8/guides/create-alert-rules.md
+++ b/content/chronograf/v1.8/guides/create-alert-rules.md
@@ -38,12 +38,12 @@ See the [Configuring Kapacitor Event Handlers](/chronograf/latest/guides/configu
Navigate to the **Manage Tasks** page under **Alerting** in the left navigation, then click **+ Build Alert Rule** in the top right corner.
-
+
The **Manage Tasks** page is used to create and edit your Chronograf alert rules.
The steps below guide you through the process of creating a Chronograf alert rule.
-
+
### Step 1: Name the alert rule
@@ -72,7 +72,7 @@ Navigate through databases, measurements, fields, and tags to select the relevan
In this example, select the `telegraf` [database](/influxdb/latest/concepts/glossary/#database), the `autogen` [retention policy](/influxdb/latest/concepts/glossary/#retention-policy-rp), the `cpu` [measurement](/influxdb/latest/concepts/glossary/#measurement), and the `usage_idle` [field](/influxdb/latest/concepts/glossary/#field).
-
+
### Step 4: Define the rule condition
@@ -80,7 +80,7 @@ Define the threshold condition.
Condition options are determined by the [alert type](#step-2-select-the-alert-type).
For this example, the alert conditions are if `usage_idle` is less than `80`.
-
+
The graph shows a preview of the relevant data and the threshold number.
By default, the graph shows data from the past 15 minutes.
@@ -98,7 +98,7 @@ Each handler has unique configurable options.
For this example, choose the **slack** alert handler and enter the desired options.
-
+
> Multiple alert handlers can be added to send alerts to multiple endpoints.
@@ -111,7 +111,7 @@ As you type your alert message, clicking the data templates will insert them at
In this example, use the alert message, `Your idle CPU usage is {{.Level}} at {{ index .Fields "value" }}.`.
-
+
*View the Kapacitor documentation for more information about [message template data](/kapacitor/latest/nodes/alert_node/#message).*
@@ -120,7 +120,7 @@ In this example, use the alert message, `Your idle CPU usage is {{.Level}} at {{
Click **Save Rule** in the top right corner and navigate to the **Manage Tasks** page to see your rule.
Notice that you can easily enable and disable the rule by toggling the checkbox in the **Enabled** column.
-
+
Next, move on to the section below to experience your alert rule in action.
@@ -149,10 +149,10 @@ Assuming the first step was successful, `#ohnos` should reveal at least two aler
* The first alert message indicates that your idle CPU usage was `CRITICAL`, meaning it dipped below `80%`.
* The second alert message indicates that your idle CPU usage returned to an `OK` level of `80%` or above.
-
+
You can also see alerts on the **Alert History** page available under **Alerting** in the left navigation.
-
+
That's it! You've successfully used Chronograf to configure an alert rule to monitor your idle CPU usage and send notifications to Slack.
diff --git a/content/chronograf/v1.8/guides/dashboard-template-variables.md b/content/chronograf/v1.8/guides/dashboard-template-variables.md
index 5279313dc..0365bf458 100644
--- a/content/chronograf/v1.8/guides/dashboard-template-variables.md
+++ b/content/chronograf/v1.8/guides/dashboard-template-variables.md
@@ -25,7 +25,7 @@ You can use either [predefined template variables](#predefined-template-variable
or [custom template variables](#create-custom-template-variables).
Variable values are then selected in your dashboard user-interface (UI).
-
+
## Predefined template variables
Chronograf includes predefined template variables controlled by elements in the Chrongraf UI.
@@ -38,7 +38,7 @@ These template variables can be used in any of your cells' queries.
### dashboardTime
The `:dashboardTime:` template variable is controlled by the "time" dropdown in your Chronograf dashboard.
-
+
If using relative times, it represents the time offset specified in the dropdown (-5m, -15m, -30m, etc.) and assumes time is relative to "now".
If using absolute times defined by the date picker, `:dashboardTime:` is populated with lower threshold.
@@ -56,7 +56,7 @@ WHERE time > :dashboardTime:
### upperDashboardTime
The `:upperDashboardTime:` template variable is defined by the upper time limit specified using the date picker.
-
+
It will inherit `now()` when using relative time frames or the upper time limit when using absolute timeframes.
@@ -70,7 +70,7 @@ WHERE time > :dashboardTime: AND time < :upperDashboardTime:
The `:interval:` template variable is defined by the interval dropdown in the Chronograf dashboard.
-
+
In cell queries, it should be used in the `GROUP BY time()` clause that accompanies aggregate functions:
@@ -251,7 +251,7 @@ key3,value3
key4,value4
```
-
+
> If values are meant to be used as string field values, wrap them in single quote ([required by InfluxQL](/influxdb/latest/troubleshooting/frequently-asked-questions/#when-should-i-single-quote-and-when-should-i-double-quote-in-queries)). This only pertains to values. String keys do not matter.
@@ -285,7 +285,7 @@ The customer names would populate your template variable dropdown rather than th
Vary part of a query with a customized meta query that pulls a specific array of values from InfluxDB.
These variables allow you to pull a highly customized array of potential values and offer advanced functionality such as [filtering values based on other template variables](#filtering-template-variables-with-other-template-variables).
-
+
_**Example custom meta query variable in a cell query**_
```sql
@@ -331,7 +331,7 @@ For example, let's say you want to list all the field keys associated with a mea
1. Create a template variable named `:measurementVar:` _(the name "measurement" is [reserved]( #reserved-variable-names))_ that uses the [Measurements](#measurements) variable type to pull in all measurements from the `telegraf` database.
- 
+
2. Create a template variable named `:fieldKey:` that uses the [custom meta query](#custom-meta-query) variable type.
The following meta query pulls a list of field keys based on the existing `:measurementVar:` template variable.
@@ -340,7 +340,7 @@ The following meta query pulls a list of field keys based on the existing `:meas
SHOW FIELD KEYS ON telegraf FROM :measurementVar:
```
- 
+
3. Create a new dashboard cell that uses the `:fieldKey:` and `:measurementVar` template variables in its query.
@@ -350,7 +350,7 @@ The following meta query pulls a list of field keys based on the existing `:meas
The resulting dashboard will work like this:
-
+
### Defining template variables in the URL
Chronograf uses URL query parameters (also known as query string parameters) to set both display options and template variables in the URL.
diff --git a/content/chronograf/v1.8/guides/monitoring-influxenterprise-clusters.md b/content/chronograf/v1.8/guides/monitoring-influxenterprise-clusters.md
index 7921c8f55..4a314626b 100644
--- a/content/chronograf/v1.8/guides/monitoring-influxenterprise-clusters.md
+++ b/content/chronograf/v1.8/guides/monitoring-influxenterprise-clusters.md
@@ -32,7 +32,7 @@ Chronograf and the other components of the TICK stack are supported on several o
Before we begin, here's an overview of the final monitoring setup:
-
+
The diagram above shows an InfluxEnterprise cluster that consists of three meta nodes (M) and three data nodes (D).
Each data node has its own [Telegraf](/telegraf/latest/) instance (T).
@@ -259,7 +259,7 @@ Chronograf can be downloaded from the [InfluxData downloads page](https://portal
To access Chronograf, go to http://localhost:8888.
The welcome page includes instructions for connecting Chronograf to that instance.
-
+
For the `Connection String`, enter the hostname or IP of your InfluxDB OSS instance, and be sure to include the default port: `8086`.
Next, name your data source; this can be anything you want.
@@ -271,17 +271,17 @@ Chronograf works with the Telegraf data in your InfluxDB OSS instance.
The `Host List` page shows your data node's hostnames, their statuses, CPU usage, load, and their configured applications.
In this case, you've only enabled the system stats input plugin so `system` is the single application that appears in the `Apps` column.
-
+
Click `system` to see the Chronograf canned dashboard for that application.
Keep an eye on your data nodes by viewing that dashboard for each hostname:
-
+
Next, check out the Data Explorer to create a customized graph with the monitoring data.
In the image below, the Chronograf query editor is used to visualize the idle CPU usage data for each data node:
-
+
Create more customized graphs and save them to a dashboard on the Dashboard page in Chronograf.
See the [Creating Chronograf dashboards](/chronograf/latest/guides/create-a-dashboard/) guide for more information.
diff --git a/content/chronograf/v1.8/guides/presentation-mode.md b/content/chronograf/v1.8/guides/presentation-mode.md
index 9a420b702..adda52076 100644
--- a/content/chronograf/v1.8/guides/presentation-mode.md
+++ b/content/chronograf/v1.8/guides/presentation-mode.md
@@ -13,7 +13,7 @@ Presentation mode allows you to view Chronograf in full screen, hiding the left
## Entering presentation mode manually
To enter presentation mode manually, click the icon in the upper right:
-
+
To exit presentation mode, press `ESC`.
diff --git a/content/chronograf/v1.8/guides/querying-data.md b/content/chronograf/v1.8/guides/querying-data.md
index b63fec054..e72730c00 100644
--- a/content/chronograf/v1.8/guides/querying-data.md
+++ b/content/chronograf/v1.8/guides/querying-data.md
@@ -11,7 +11,7 @@ Explore and visualize your data in the **Data Explorer**. For both InfluxQL and
To open the **Data Explorer**, click the **Explore** icon in the navigation bar:
-
+
## Select local time or UTC (Coordinated Universal Time)
@@ -47,7 +47,7 @@ Flux is InfluxData's new functional data scripting language designed for queryin
* To get started with your query, click the **Script Wizard**. In the wizard, you can select a bucket, measurement, fields and an aggregate.
- 
+
For example, if you make the above selections, the wizard inserts the following script:
@@ -75,9 +75,9 @@ To add your query and graph to a dashboard:
1. Click **Send to Dashboard** in the upper right.
2. In the **Target Dashboard(s)** dropdown, select at least one existing dashboard to send the cell to, or select **Send to a New Dashboard**.
-
+
3. Enter a name for the new cell and, if you created a new dashboard, the new dashboard.
4. Click **Send to Dashboard(s)**.
- 
+
diff --git a/content/chronograf/v1.8/guides/visualization-types.md b/content/chronograf/v1.8/guides/visualization-types.md
index e9bdc2123..1ad125bd8 100644
--- a/content/chronograf/v1.8/guides/visualization-types.md
+++ b/content/chronograf/v1.8/guides/visualization-types.md
@@ -10,7 +10,7 @@ menu:
Chronograf's dashboard views support the following visualization types, which can be selected in the **Visualization Type** selection view of the [Data Explorer](/chronograf/latest/querying-data) .
-[Visualization Type selector](/img/chronograf/chrono-viz-types-selector.png)
+[Visualization Type selector](/img/chronograf/1-6-viz-types-selector.png)
Each of the available visualization types and available user controls are described below.
@@ -31,11 +31,11 @@ For information on adding and displaying annotations in graph views, see [Adding
The **Line Graph** view displays a time series in a line graph.
-
+
#### Line Graph Controls
-
+
Use the **Line Graph Controls** to specify the following:
@@ -54,18 +54,18 @@ Use the **Line Graph Controls** to specify the following:
#### Line Graph example
-
+
### Stacked Graph
The **Stacked Graph** view displays multiple time series bars as segments stacked on top of each other.
-
+
#### Stacked Graph Controls
-
+
Use the **Stacked Graph Controls** to specify the following:
@@ -84,18 +84,18 @@ Use the **Stacked Graph Controls** to specify the following:
#### Stacked Graph example
-
+
### Step-Plot Graph
The **Step-Plot Graph** view displays a time series in a staircase graph.
-
+
#### Step-Plot Graph Controls
-
+
Use the **Step-Plot Graph Controls** to specify the following:
@@ -112,7 +112,7 @@ Use the **Step-Plot Graph Controls** to specify the following:
#### Step-Plot Graph example
-
+
### Bar Graph
@@ -121,11 +121,11 @@ The **Bar Graph** view displays the specified time series using a bar chart.
To select this view, click the Bar Graph selector icon.
-
+
#### Bar Graph Controls
-
+
Use the **Bar Graph Controls** to specify the following:
@@ -142,7 +142,7 @@ Use the **Bar Graph Controls** to specify the following:
#### Bar Graph example
-
+
### Line Graph + Single Stat
@@ -151,11 +151,11 @@ The **Line Graph + Single Stat** view displays the specified time series in a li
To select this view, click the **Line Graph + Single Stat** view option.
-
+
#### Line Graph + Single Stat Controls
-
+
Use the **Line Graph + Single Stat Controls** to specify the following:
@@ -172,13 +172,13 @@ Use the **Line Graph + Single Stat Controls** to specify the following:
#### Line Graph + Single Stat example
-
+
### Single Stat
The **Single Stat** view displays the most recent value of the specified time series as a numerical value.
-
+
If a cell's query includes a [`GROUP BY` tag](/influxdb/latest/query_language/data_exploration/#group-by-tags) clause, Chronograf sorts the different [series](/influxdb/latest/concepts/glossary/#series) lexicographically and shows the most recent [field value](/influxdb/latest/concepts/glossary/#field-value) associated with the first series.
For example, if a query groups by the `name` [tag key](/influxdb/latest/concepts/glossary/#tag-key) and `name` has two [tag values](/influxdb/latest/concepts/glossary/#tag-value) (`chronelda` and `chronz`), Chronograf shows the most recent field value associated with the `chronelda` series.
@@ -204,11 +204,11 @@ The **Gauge** view displays the single value most recent value for a time series
To select this view, click the Gauge selector icon.
-
+
#### Gauge Controls
-
+
Use the **Gauge Controls** to specify the following:
@@ -222,17 +222,17 @@ Use the **Gauge Controls** to specify the following:
#### Gauge example
-
+
### Table
The **Table** panel displays the results of queries in a tabular view, which is sometimes easier to analyze than graph views of data.
-
+
#### Table Controls
-
+
Use the **Table Controls** to specify the following:
@@ -256,17 +256,17 @@ Use the **Table Controls** to specify the following:
#### Table view example
-
+
### Note
The **Note** panel displays Markdown-formatted text with your graph.
-
+
#### Note Controls
-
+
Enter your text in the **Add a Note** panel, using Markdown to format the text.
@@ -274,4 +274,4 @@ Enable the **Display note in cell when query returns no results** option to disp
#### Note view example
-
+
diff --git a/content/chronograf/v1.8/tools/chronoctl/migrate.md b/content/chronograf/v1.8/tools/chronoctl/migrate.md
index f67d35db2..9bbd02478 100644
--- a/content/chronograf/v1.8/tools/chronoctl/migrate.md
+++ b/content/chronograf/v1.8/tools/chronoctl/migrate.md
@@ -22,4 +22,4 @@ chronoctl migrate [flags]
| Flag | Description | Input type |
|:---- |:----------- |:----------: |
| `-f`, `--from` | Full path to BoltDB file or etcd (e.g. 'bolt:///path/to/chronograf-v1.db' or 'etcd://user:pass@localhost:2379 (default: chronograf-v1.db) | string |
-| `-t`, `--to` | Full path to BoltDB file or etcd (e.g. 'bolt:///path/to/chronograf-v1.db' or 'etcd://user:pass@localhost:2379 (default: etcd://localhost:2379) | string |
\ No newline at end of file
+| `-t`, `--to` | Full path to BoltDB file or etcd (e.g. 'bolt:///path/to/chronograf-v1.db' or 'etcd://user:pass@localhost:2379 (default: etcd://localhost:2379) | string |
diff --git a/content/chronograf/v1.8/troubleshooting/frequently-asked-questions.md b/content/chronograf/v1.8/troubleshooting/frequently-asked-questions.md
index 5d6cbdd87..8bb924799 100644
--- a/content/chronograf/v1.8/troubleshooting/frequently-asked-questions.md
+++ b/content/chronograf/v1.8/troubleshooting/frequently-asked-questions.md
@@ -15,7 +15,7 @@ When you enter the InfluxDB HTTP bind address in the `Connection String` input,
If it is a data node, Chronograf automatically adds the `Meta Service Connection URL` input to the connection details form.
Enter the HTTP bind address of one of your cluster's meta nodes into that input and Chronograf takes care of the rest.
-
+
Note that the example above assumes that you do not have authentication enabled.
If you have authentication enabled, the form requires username and password information.
diff --git a/content/enterprise_influxdb/v1.5/_index.md b/content/enterprise_influxdb/v1.5/_index.md
index 30a8de87c..c114edc05 100644
--- a/content/enterprise_influxdb/v1.5/_index.md
+++ b/content/enterprise_influxdb/v1.5/_index.md
@@ -17,19 +17,19 @@ Use InfluxDB Enterprise to:
* Monitor your cluster
- 
+ 
* Manage queries
- 
+ 
* Manage users
- 
+ 
* Explore and visualize your data
- 
+ 
If you're interested in working with InfluxDB Enterprise, visit
[InfluxPortal](https://portal.influxdata.com/) to sign up, get a license key,
diff --git a/content/enterprise_influxdb/v1.6/_index.md b/content/enterprise_influxdb/v1.6/_index.md
index d9b0b1d1c..dc647fb57 100644
--- a/content/enterprise_influxdb/v1.6/_index.md
+++ b/content/enterprise_influxdb/v1.6/_index.md
@@ -17,19 +17,19 @@ Use InfluxDB Enterprise to:
* Monitor your cluster
- 
+ 
* Manage queries
- 
+ 
* Manage users
- 
+ 
* Explore and visualize your data
- 
+ 
If you're interested in working with InfluxDB Enterprise, visit
[InfluxPortal](https://portal.influxdata.com/) to sign up, get a license key,
diff --git a/content/enterprise_influxdb/v1.6/install-and-deploy/deploying/google-cloud-platform.md b/content/enterprise_influxdb/v1.6/install-and-deploy/deploying/google-cloud-platform.md
index c6b1598c8..f2eb6e7b4 100644
--- a/content/enterprise_influxdb/v1.6/install-and-deploy/deploying/google-cloud-platform.md
+++ b/content/enterprise_influxdb/v1.6/install-and-deploy/deploying/google-cloud-platform.md
@@ -27,11 +27,11 @@ To deploy InfluxDB Enterprise on platforms other than GCP, please see [InfluxDB
To deploy an InfluxDB Enterprise cluster, log in to your Google Cloud Platform account and navigate to [InfluxData's InfluxDB Enterprise (BYOL)](https://console.cloud.google.com/partner/editor/influxdata-public/influxdb-enterprise-byol) solution in the GCP Marketplace.
-
+
Click __Launch on compute engine__ to open up the configuration page.
-
+
Copy the InfluxDB Enterprise license key to the __InfluxDB Enterprise license key__ field or [sign up for a free InfluxDB Enterprise trial for GCP](https://portal.influxdata.com/users/gcp) to obtain a license key.
@@ -39,11 +39,11 @@ Adjust any other fields as desired. The cluster will only be accessible within t
Click __Deploy__ to launch the InfluxDB Enterprise cluster.
-
+
The cluster will take up to five minutes to fully deploy. If the deployment does not complete or reports an error, read through the list of [common deployment errors](https://cloud.google.com/marketplace/docs/troubleshooting).
-
+
Your cluster is now deployed!
diff --git a/content/enterprise_influxdb/v1.6/install-and-deploy/production_installation/_index.md b/content/enterprise_influxdb/v1.6/install-and-deploy/production_installation/_index.md
index 6ba80a3e8..ec4b35aac 100644
--- a/content/enterprise_influxdb/v1.6/install-and-deploy/production_installation/_index.md
+++ b/content/enterprise_influxdb/v1.6/install-and-deploy/production_installation/_index.md
@@ -21,4 +21,4 @@ Learn how to deploy a cluster on the cloud provider of your choice:
- [GCP](/enterprise_influxdb/v1.7/install-and-deploy/google-cloud-platform/)
- [AWS](/enterprise_influxdb/v1.7/install-and-deploy/aws/)
- - [Azure](/enterprise_influxdb/v1.7/install-and-deploy/deploying/azure/)
\ No newline at end of file
+ - [Azure](/enterprise_influxdb/v1.7/install-and-deploy/deploying/azure/)
diff --git a/content/enterprise_influxdb/v1.7/_index.md b/content/enterprise_influxdb/v1.7/_index.md
index fdc16070b..61b4613d0 100644
--- a/content/enterprise_influxdb/v1.7/_index.md
+++ b/content/enterprise_influxdb/v1.7/_index.md
@@ -17,19 +17,19 @@ Use InfluxDB Enterprise to:
* Monitor your cluster
- 
+ 
* Manage queries
- 
+ 
* Manage users
- 
+ 
* Explore and visualize your data
- 
+ 
If you're interested in working with InfluxDB Enterprise, visit
[InfluxPortal](https://portal.influxdata.com/) to sign up, get a license key,
diff --git a/content/enterprise_influxdb/v1.7/administration/backup-and-restore.md b/content/enterprise_influxdb/v1.7/administration/backup-and-restore.md
index 6b45decc4..5ed854ec0 100644
--- a/content/enterprise_influxdb/v1.7/administration/backup-and-restore.md
+++ b/content/enterprise_influxdb/v1.7/administration/backup-and-restore.md
@@ -454,4 +454,4 @@ First, run two clusters in separate AWS regions, and then transfer your data usi
9. Use a separate data node for monitoring metrics.
- > **Limitations:** This solution cannot handle much backfill. To capture backfill, you must create an ad hoc solution. Also, if your disaster recovery site goes down, data on the active site is still getting backed up into S3, but isn’t imported until your disaster recovery cluster is back up and your import script runs.
\ No newline at end of file
+ > **Limitations:** This solution cannot handle much backfill. To capture backfill, you must create an ad hoc solution. Also, if your disaster recovery site goes down, data on the active site is still getting backed up into S3, but isn’t imported until your disaster recovery cluster is back up and your import script runs.
diff --git a/content/enterprise_influxdb/v1.7/troubleshooting/frequently_asked_questions.md b/content/enterprise_influxdb/v1.7/troubleshooting/frequently_asked_questions.md
index 8c74df7e3..eb00398bc 100644
--- a/content/enterprise_influxdb/v1.7/troubleshooting/frequently_asked_questions.md
+++ b/content/enterprise_influxdb/v1.7/troubleshooting/frequently_asked_questions.md
@@ -97,4 +97,4 @@ If you are getting an error message while attempting to `influxd-ctl join` a new
## Why do I see entropy when rebalancing shards?
-Before rebalancing shards, we recommend enabling anti-entropy (AE) to ensure all shard data is successfully copied. To learn more about AE, see [Use Anti-Entropy service in InfluxDB Enterprise](/enterprise_influxdb/v1.7/administration/anti-entropy).
\ No newline at end of file
+Before rebalancing shards, we recommend enabling anti-entropy (AE) to ensure all shard data is successfully copied. To learn more about AE, see [Use Anti-Entropy service in InfluxDB Enterprise](/enterprise_influxdb/v1.7/administration/anti-entropy).
diff --git a/content/enterprise_influxdb/v1.8/_index.md b/content/enterprise_influxdb/v1.8/_index.md
index 1828ae97b..251e3dcf2 100644
--- a/content/enterprise_influxdb/v1.8/_index.md
+++ b/content/enterprise_influxdb/v1.8/_index.md
@@ -16,19 +16,19 @@ Use InfluxDB Enterprise to:
* Monitor your cluster
- 
+ 
* Manage queries
- 
+ 
* Manage users
- 
+ 
* Explore and visualize your data
- 
+ 
If you're interested in working with InfluxDB Enterprise, visit
[InfluxPortal](https://portal.influxdata.com/) to sign up, get a license key,
diff --git a/content/influxdb/v1.3/guides/hardware_sizing.md b/content/influxdb/v1.3/guides/hardware_sizing.md
index ba846ae53..696940731 100644
--- a/content/influxdb/v1.3/guides/hardware_sizing.md
+++ b/content/influxdb/v1.3/guides/hardware_sizing.md
@@ -157,7 +157,7 @@ A series cardinality around or above 10 million can cause OOM failures even with
The increase in RAM needs relative to series cardinality is exponential where the exponent is between one and two:
-
+
# What kind of storage do I need?
InfluxDB is designed to run on SSDs. InfluxData does not test on HDDs or networked storage devices, and we do not recommend them for production. Performance is an order of magnitude lower on spinning disk drives and the system may break down under even moderate load. For best results InfluxDB servers must have at least 1000 IOPS on the storage system.
diff --git a/content/influxdb/v1.3/query_language/functions.md b/content/influxdb/v1.3/query_language/functions.md
index bd4de4a57..4fc8c8180 100644
--- a/content/influxdb/v1.3/query_language/functions.md
+++ b/content/influxdb/v1.3/query_language/functions.md
@@ -3040,7 +3040,7 @@ The example focuses the following subsample of the [`NOAA_water_database` data](
SELECT "water_level" FROM "NOAA_water_database"."autogen"."h2o_feet" WHERE "location"='santa_monica' AND time >= '2015-08-22 22:12:00' AND time <= '2015-08-28 03:00:00'
```
-
+
##### Step 1: Match the Trends of the Raw Data
@@ -3060,7 +3060,7 @@ match the time range of the raw data. The blue line shows the results of the query: - + ##### Step 2: Determine the Seasonal Pattern
@@ -3070,7 +3070,7 @@ query in step 1. Focusing on the blue line in the graph below, the pattern in the `water_level` data repeats about every 25 hours and 15 minutes. There are four data points per season, so `4` is the seasonal pattern argument. - + ##### Step 3: Apply the HOLT_WINTERS() function
@@ -3087,7 +3087,7 @@ The second argument in the `HOLT_WINTERS_WITH_FIT()` function (`4`) is the seaso The blue line shows the results of the query: - + ### Common Issues with `HOLT_WINTERS()` diff --git a/content/influxdb/v1.3/tools/_index.md b/content/influxdb/v1.3/tools/_index.md index 6419d2a0b..0429af648 100644 --- a/content/influxdb/v1.3/tools/_index.md +++ b/content/influxdb/v1.3/tools/_index.md @@ -18,7 +18,7 @@ HTTP API that comes with every InfluxDB package. Use `influx` to write data (manually or from a file), query data interactively, and view query output in different formats: - + Go straight to the documentation on: diff --git a/content/influxdb/v1.4/guides/hardware_sizing.md b/content/influxdb/v1.4/guides/hardware_sizing.md index d2942b073..9f6969b03 100644 --- a/content/influxdb/v1.4/guides/hardware_sizing.md +++ b/content/influxdb/v1.4/guides/hardware_sizing.md @@ -157,7 +157,7 @@ A series cardinality around or above 10 million can cause OOM failures even with The increase in RAM needs relative to series cardinality is exponential where the exponent is between one and two: - + # What kind of storage do I need? InfluxDB is designed to run on SSDs. InfluxData does not test on HDDs or networked storage devices, and we do not recommend them for production. Performance is an order of magnitude lower on spinning disk drives and the system may break down under even moderate load. For best results InfluxDB servers must have at least 1000 IOPS on the storage system. diff --git a/content/influxdb/v1.4/query_language/functions.md b/content/influxdb/v1.4/query_language/functions.md index 0002184bf..55886cf91 100644 --- a/content/influxdb/v1.4/query_language/functions.md +++ b/content/influxdb/v1.4/query_language/functions.md @@ -3040,7 +3040,7 @@ The example focuses the following subsample of the [`NOAA_water_database` data]( SELECT "water_level" FROM "NOAA_water_database"."autogen"."h2o_feet" WHERE "location"='santa_monica' AND time >= '2015-08-22 22:12:00' AND time <= '2015-08-28 03:00:00' ``` - + ##### Step 1: Match the Trends of the Raw Data
@@ -3060,7 +3060,7 @@ match the time range of the raw data. The blue line shows the results of the query: - + ##### Step 2: Determine the Seasonal Pattern
@@ -3070,7 +3070,7 @@ query in step 1. Focusing on the blue line in the graph below, the pattern in the `water_level` data repeats about every 25 hours and 15 minutes. There are four data points per season, so `4` is the seasonal pattern argument. - + ##### Step 3: Apply the HOLT_WINTERS() function
@@ -3087,7 +3087,7 @@ The second argument in the `HOLT_WINTERS_WITH_FIT()` function (`4`) is the seaso The blue line shows the results of the query: - + ### Common Issues with `HOLT_WINTERS()` diff --git a/content/influxdb/v1.4/tools/_index.md b/content/influxdb/v1.4/tools/_index.md index bf00d9f6d..336f17ada 100644 --- a/content/influxdb/v1.4/tools/_index.md +++ b/content/influxdb/v1.4/tools/_index.md @@ -18,7 +18,7 @@ HTTP API that comes with every InfluxDB package. Use `influx` to write data (manually or from a file), query data interactively, and view query output in different formats: - + Go straight to the documentation on: diff --git a/content/influxdb/v1.5/guides/calculating_percentages.md b/content/influxdb/v1.5/guides/calculating_percentages.md index 1c7762b44..411b92dd4 100644 --- a/content/influxdb/v1.5/guides/calculating_percentages.md +++ b/content/influxdb/v1.5/guides/calculating_percentages.md @@ -83,7 +83,7 @@ FROM "apple_stand"."autogen"."variety"'> If visualized as a [stacked graph](/chronograf/v1.5/guides/visualization-types/#stacked-graph) in Chronograf, it would look like: - + ### Calculating aggregate percentage per variety The following query calculates the average percentage of the total weight each variety @@ -112,4 +112,4 @@ _**Note the following about this query:**_ If visualized as a [stacked graph](/chronograf/v1.5/guides/visualization-types/#stacked-graph) in Chronograf, it would look like: - + diff --git a/content/influxdb/v1.5/query_language/functions.md b/content/influxdb/v1.5/query_language/functions.md index 8f3007dc3..8797fb55c 100644 --- a/content/influxdb/v1.5/query_language/functions.md +++ b/content/influxdb/v1.5/query_language/functions.md @@ -3041,7 +3041,7 @@ The example focuses the following subsample of the [`NOAA_water_database` data]( SELECT "water_level" FROM "NOAA_water_database"."autogen"."h2o_feet" WHERE "location"='santa_monica' AND time >= '2015-08-22 22:12:00' AND time <= '2015-08-28 03:00:00' ``` - + ##### Step 1: Match the Trends of the Raw Data
@@ -3061,7 +3061,7 @@ match the time range of the raw data. The blue line shows the results of the query: - + ##### Step 2: Determine the Seasonal Pattern
@@ -3071,7 +3071,7 @@ query in step 1. Focusing on the blue line in the graph below, the pattern in the `water_level` data repeats about every 25 hours and 15 minutes. There are four data points per season, so `4` is the seasonal pattern argument. - + ##### Step 3: Apply the HOLT_WINTERS() function
@@ -3088,7 +3088,7 @@ The second argument in the `HOLT_WINTERS_WITH_FIT()` function (`4`) is the seaso The blue line shows the results of the query: - + ### Common Issues with `HOLT_WINTERS()` diff --git a/content/influxdb/v1.5/tools/_index.md b/content/influxdb/v1.5/tools/_index.md index c97152daa..2debcb346 100644 --- a/content/influxdb/v1.5/tools/_index.md +++ b/content/influxdb/v1.5/tools/_index.md @@ -19,7 +19,7 @@ HTTP API that comes with every InfluxDB package. Use `influx` to write data (manually or from a file), query data interactively, and view query output in different formats: - + Go straight to the documentation on: diff --git a/content/influxdb/v1.6/guides/calculating_percentages.md b/content/influxdb/v1.6/guides/calculating_percentages.md index 86251ffb3..42c4c93ac 100644 --- a/content/influxdb/v1.6/guides/calculating_percentages.md +++ b/content/influxdb/v1.6/guides/calculating_percentages.md @@ -83,7 +83,7 @@ FROM "apple_stand"."autogen"."variety"'> If visualized as a [stacked graph](/chronograf/v1.6/guides/visualization-types/#stacked-graph) in Chronograf, it would look like: - + ### Calculating aggregate percentage per variety The following query calculates the average percentage of the total weight each variety @@ -112,4 +112,4 @@ _**Note the following about this query:**_ If visualized as a [stacked graph](/chronograf/v1.6/guides/visualization-types/#stacked-graph) in Chronograf, it would look like: - + diff --git a/content/influxdb/v1.6/query_language/functions.md b/content/influxdb/v1.6/query_language/functions.md index a3b6b8925..a842d46ff 100644 --- a/content/influxdb/v1.6/query_language/functions.md +++ b/content/influxdb/v1.6/query_language/functions.md @@ -6010,7 +6010,7 @@ The example focuses the following subsample of the [`NOAA_water_database` data]( SELECT "water_level" FROM "NOAA_water_database"."autogen"."h2o_feet" WHERE "location"='santa_monica' AND time >= '2015-08-22 22:12:00' AND time <= '2015-08-28 03:00:00' ``` - + ##### Step 1: Match the Trends of the Raw Data
@@ -6030,7 +6030,7 @@ match the time range of the raw data. The blue line shows the results of the query: - + ##### Step 2: Determine the Seasonal Pattern
@@ -6040,7 +6040,7 @@ query in step 1. Focusing on the blue line in the graph below, the pattern in the `water_level` data repeats about every 25 hours and 15 minutes. There are four data points per season, so `4` is the seasonal pattern argument. - + ##### Step 3: Apply the HOLT_WINTERS() function
@@ -6057,7 +6057,7 @@ The second argument in the `HOLT_WINTERS_WITH_FIT()` function (`4`) is the seaso The blue line shows the results of the query: - + ### Common Issues with `HOLT_WINTERS()` diff --git a/content/influxdb/v1.6/tools/_index.md b/content/influxdb/v1.6/tools/_index.md index 9adca19b0..03bc17a2d 100644 --- a/content/influxdb/v1.6/tools/_index.md +++ b/content/influxdb/v1.6/tools/_index.md @@ -19,7 +19,7 @@ HTTP API that comes with every InfluxDB package. Use `influx` to write data (manually or from a file), query data interactively, and view query output in different formats: - + Go straight to the documentation on: diff --git a/content/influxdb/v1.7/guides/calculating_percentages.md b/content/influxdb/v1.7/guides/calculating_percentages.md index 51a7178d9..129a136e1 100644 --- a/content/influxdb/v1.7/guides/calculating_percentages.md +++ b/content/influxdb/v1.7/guides/calculating_percentages.md @@ -83,7 +83,7 @@ FROM "apple_stand"."autogen"."variety"'> If visualized as a [stacked graph](/chronograf/v1.7/guides/visualization-types/#stacked-graph) in Chronograf, it would look like: - + ### Calculating aggregate percentage per variety The following query calculates the average percentage of the total weight each variety @@ -112,4 +112,4 @@ _**Note the following about this query:**_ If visualized as a [stacked graph](/chronograf/v1.7/guides/visualization-types/#stacked-graph) in Chronograf, it would look like: - + diff --git a/content/influxdb/v1.7/query_language/functions.md b/content/influxdb/v1.7/query_language/functions.md index abd0476f6..f3761d909 100644 --- a/content/influxdb/v1.7/query_language/functions.md +++ b/content/influxdb/v1.7/query_language/functions.md @@ -6236,7 +6236,7 @@ The example focuses on the following subsample of the [`NOAA_water_database` dat SELECT "water_level" FROM "NOAA_water_database"."autogen"."h2o_feet" WHERE "location"='santa_monica' AND time >= '2015-08-22 22:12:00' AND time <= '2015-08-28 03:00:00' ``` - + ###### Step 1: Match the Trends of the Raw Data @@ -6256,7 +6256,7 @@ match the time range of the raw data. The blue line shows the results of the query: - + ###### Step 2: Determine the Seasonal Pattern @@ -6266,7 +6266,7 @@ query in step 1. Focusing on the blue line in the graph below, the pattern in the `water_level` data repeats about every 25 hours and 15 minutes. There are four data points per season, so `4` is the seasonal pattern argument. - + ###### Step 3: Apply the HOLT_WINTERS() function @@ -6283,7 +6283,7 @@ The second argument in the `HOLT_WINTERS_WITH_FIT()` function (`4`) is the seaso The blue line shows the results of the query: - + #### Common Issues with `HOLT_WINTERS()` diff --git a/content/influxdb/v1.8/guides/calculate_percentages.md b/content/influxdb/v1.8/guides/calculate_percentages.md index 172f4ed70..c38dcef1d 100644 --- a/content/influxdb/v1.8/guides/calculate_percentages.md +++ b/content/influxdb/v1.8/guides/calculate_percentages.md @@ -228,7 +228,7 @@ FROM "apple_stand"."autogen"."variety"'> If visualized as a [stacked graph](/chronograf/v1.8/guides/visualization-types/#stacked-graph) in Chronograf, it would look like: - + ### Calculating aggregate percentage per variety @@ -258,7 +258,7 @@ _**Note the following about this query:**_ If visualized as a [stacked graph](/chronograf/v1.8/guides/visualization-types/#stacked-graph) in Chronograf, it would look like: - + {{% /tab-content %}} {{< /tabs-wrapper >}} diff --git a/content/influxdb/v1.8/guides/hardware_sizing.md b/content/influxdb/v1.8/guides/hardware_sizing.md index d1448fe60..0723bd30a 100644 --- a/content/influxdb/v1.8/guides/hardware_sizing.md +++ b/content/influxdb/v1.8/guides/hardware_sizing.md @@ -115,7 +115,7 @@ In general, more RAM helps queries return faster. Your RAM requirements are prim The increase in RAM needs relative to series cardinality is exponential where the exponent is between one and two: - + ## Guidelines per cluster diff --git a/content/influxdb/v1.8/query_language/functions.md b/content/influxdb/v1.8/query_language/functions.md index f00e88222..2e561e0c5 100644 --- a/content/influxdb/v1.8/query_language/functions.md +++ b/content/influxdb/v1.8/query_language/functions.md @@ -6236,7 +6236,7 @@ The example focuses on the following subsample of the [`NOAA_water_database` dat SELECT "water_level" FROM "NOAA_water_database"."autogen"."h2o_feet" WHERE "location"='santa_monica' AND time >= '2015-08-22 22:12:00' AND time <= '2015-08-28 03:00:00' ``` - + ###### Step 1: Match the Trends of the Raw Data @@ -6256,7 +6256,7 @@ match the time range of the raw data. The blue line shows the results of the query: - + ###### Step 2: Determine the Seasonal Pattern @@ -6266,7 +6266,7 @@ query in step 1. Focusing on the blue line in the graph below, the pattern in the `water_level` data repeats about every 25 hours and 15 minutes. There are four data points per season, so `4` is the seasonal pattern argument. - + ###### Step 3: Apply the HOLT_WINTERS() function @@ -6283,7 +6283,7 @@ The second argument in the `HOLT_WINTERS_WITH_FIT()` function (`4`) is the seaso The blue line shows the results of the query: - + #### Common Issues with `HOLT_WINTERS()` diff --git a/content/influxdb/v2.0/account-management/data-usage.md b/content/influxdb/v2.0/account-management/data-usage.md index 87dd38ebf..399b36942 100644 --- a/content/influxdb/v2.0/account-management/data-usage.md +++ b/content/influxdb/v2.0/account-management/data-usage.md @@ -29,7 +29,7 @@ Find data usage information for the time frame specified in the drop-down at the - **Rate Limits over the specified time period:** A list of rate limit events over the specified time period. -{{< img-hd src="/img/2-0-cloud-usage.png" />}} +{{< img-hd src="/img/influxdb/2-0-cloud-usage.png" />}} ## Exceeded rate limits diff --git a/content/influxdb/v2.0/example.md b/content/influxdb/v2.0/example.md index 6e83f1909..2d2a02f4e 100644 --- a/content/influxdb/v2.0/example.md +++ b/content/influxdb/v2.0/example.md @@ -61,7 +61,7 @@ WHERE time > now() - 15m ### h3 This is a header3 This is a paragraph. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc rutrum, metus id scelerisque euismod, erat ante suscipit nibh, ac congue enim risus id est. Etiam tristique nisi et tristique auctor. Morbi eu bibendum erat. Sed ullamcorper, dui id lobortis efficitur, mauris odio pharetra neque, vel tempor odio dolor blandit justo. - + {{< img-hd src="/img/test-image-2.png" alt="Test Image" />}} diff --git a/content/influxdb/v2.0/query-data/execute-queries.md b/content/influxdb/v2.0/query-data/execute-queries.md index 7bc163189..99ed461dc 100644 --- a/content/influxdb/v2.0/query-data/execute-queries.md +++ b/content/influxdb/v2.0/query-data/execute-queries.md @@ -23,7 +23,7 @@ This guide covers the different options: ## Data Explorer Queries can be built, executed, and visualized in InfluxDB UI's Data Explorer. - + ## Influx REPL The [`influx repl` command](/v2.0/reference/cli/influx/repl) starts an interactive diff --git a/content/influxdb/v2.0/query-data/flux/group-data.md b/content/influxdb/v2.0/query-data/flux/group-data.md index 5904475e4..c154ea09c 100644 --- a/content/influxdb/v2.0/query-data/flux/group-data.md +++ b/content/influxdb/v2.0/query-data/flux/group-data.md @@ -164,7 +164,7 @@ Table: keys: [_start, _stop, _field, _measurement, cpu] **Note that the group key is output with each table: `Table: keys: