added home page link in each product naviation

pull/1387/head
Scott Anderson 2020-08-10 10:21:19 -06:00
parent bc8c176e4d
commit 0fb2330fa5
6 changed files with 40 additions and 39 deletions

View File

@ -4,8 +4,9 @@ description: >
Learn how to use and leverage InfluxDB in use cases such as monitoring metrics, IoT data, and events.
layout: version-landing
menu:
influxdb:
name: v2.0
influxdb_2_0:
name: InfluxDB 2.0 home
weight: 1
aliases:
- /v2.0/
---

View File

@ -4,7 +4,7 @@ description: Download, install, and setup InfluxDB, creating a default organizat
menu:
influxdb_2_0:
name: Get started
weight: 1
weight: 2
influxdb/v2.0/tags: [get-started, install]
aliases:
- /v2.0/cloud/get-started

View File

@ -2,7 +2,7 @@
title: Introduction to the InfluxData platform
description: The InfluxData platform is the leading modern time-series platform built for metrics and events.
aliases:
- /platform/introduction
- /platform
menu:
platform:
name: Introduction
@ -30,8 +30,8 @@ The **InfluxData 1.x platform** includes the following open source components ([
The **InfluxDB 2.0 platform** consolidates components from the **InfluxData 1.x platform** into a single packaged solution, with added features and flexibility:
- [InfluxDB 2.0 OSS](/influxdb/v2.0/get-started/): open source platform solution in a single binary
- [InfluxDB Cloud 2.0](/influxdb/v2.0/get-started/) (**commercial offering**): hosted cloud solution
- [InfluxDB 2.0 OSS](https://v2.docs.influxdata.com/v2.0/get-started/): open source platform solution in a single binary
- [InfluxDB Cloud 2.0](https://v2.docs.influxdata.com/v2.0/get-started/) (**commercial offering**): hosted cloud solution
InfluxDB Enterprise 2.0 is in development.
@ -40,9 +40,9 @@ InfluxDB Enterprise 2.0 is in development.
### Telegraf
Telegraf is a data collection agent that captures data from a growing list of sources
and translates it into [InfluxDB line protocol format](/{{< latest "influxdb" "v1" >}}/write_protocols/line_protocol_reference/)
and translates it into [InfluxDB line protocol format](/influxdb/latest/write_protocols/line_protocol_reference/)
for storage in InfluxDB. Telegraf's extensible architecture makes it easy to
create [plugins](/{{< latest "telegraf" >}}/plugins/) that both pull data (input plugins) and push data (output plugins)
create [plugins](/telegraf/latest/plugins/) that both pull data (input plugins) and push data (output plugins)
to and from different sources and endpoints.
### InfluxDB
@ -86,13 +86,13 @@ InfluxDB Enterprise provides functionality necessary to run a high-availability
#### Hinted handoff
Data is written across nodes using an eventually consistent write model.
All writes are added to the [Hinted Handoff Queue (HHQ)](/{{< latest "enterprise_influxdb" >}}/concepts/clustering/#hinted-handoff),
All writes are added to the [Hinted Handoff Queue (HHQ)](/enterprise_influxdb/latest/concepts/clustering/#hinted-handoff),
then written to other nodes in the cluster.
#### Anti-Entropy
InfluxDB Enterprise's
[Anti-Entropy (AE)](/{{< latest "enterprise_influxdb" >}}/administration/anti-entropy/)
[Anti-Entropy (AE)](/enterprise_influxdb/latest/administration/anti-entropy/)
process ensures data shards in the cluster are in sync. When "entropy" (out-of-sync
data) is detected, AE will repair the affected shards, syncing the missing data.
@ -136,7 +136,11 @@ Data is passed between InfluxDB and Kapacitor via subscriptions.
Kapacitor Enterprise includes configuration options that let you encrypt
communication between your Kapacitor Enterprise and InfluxDB Enterprise clusters.
<a class="btn" href="https://portal.influxdata.com/" target="\_blank">Try InfluxData Platform Enterprise</a>
<div style="display:inline-block;padding:.25em;margin:1em 0 2em; color:#fff;background:#4ed8a0;background:linear-gradient(to right,#4ed8a0 0,#22adf6 100%);border-radius:3px;">
<a href="https://portal.influxdata.com/" target="\_blank" class="sidebar--support-ad--cta" style="color:#fff;text-align:center;">
Try InfluxData Platform Enterprise
</a>
</div>
## Get started
@ -145,4 +149,4 @@ To get started with the **InfluxData 1.x** platform, see
[Installation and Configuration](/platform/installation)
[Getting Started](/platform/introduction/getting-started)
To get started with the **InfluxDB 2.0** platform, see [**InfluxDB Cloud 2.0**](/influxdb/v2.0/get-started/) or [**InfluxDB 2.0 OSS**](/influxdb/v2.0/get-started/).
To get started with the **InfluxDB 2.0** platform, see [**InfluxDB Cloud 2.0**](https://v2.docs.influxdata.com/v2.0/get-started/) or [**InfluxDB 2.0 OSS**](https://v2.docs.influxdata.com/v2.0/get-started/).

View File

@ -2,11 +2,11 @@
title: Introduction to the InfluxData platform
description: The InfluxData platform is the leading modern time-series platform built for metrics and events.
aliases:
- /platform/
- /platform/introduction
menu:
platform:
name: Introduction
weight: 10
weight: 1
---
**InfluxData platform** is the leading modern [time series](/platform/faq/#what-is-time-series-data) platform, built for metrics and events. Explore both versions of our platform below--[**InfluxData 1.x**](#influxdata-1-x) and [**InfluxDB 2.0**](#influxdb-2-0).
@ -30,8 +30,8 @@ The **InfluxData 1.x platform** includes the following open source components ([
The **InfluxDB 2.0 platform** consolidates components from the **InfluxData 1.x platform** into a single packaged solution, with added features and flexibility:
- [InfluxDB 2.0 OSS](https://v2.docs.influxdata.com/v2.0/get-started/): open source platform solution in a single binary
- [InfluxDB Cloud 2.0](https://v2.docs.influxdata.com/v2.0/get-started/) (**commercial offering**): hosted cloud solution
- [InfluxDB 2.0 OSS](/influxdb/v2.0/get-started/): open source platform solution in a single binary
- [InfluxDB Cloud 2.0](/influxdb/v2.0/get-started/) (**commercial offering**): hosted cloud solution
InfluxDB Enterprise 2.0 is in development.
@ -40,9 +40,9 @@ InfluxDB Enterprise 2.0 is in development.
### Telegraf
Telegraf is a data collection agent that captures data from a growing list of sources
and translates it into [InfluxDB line protocol format](/influxdb/latest/write_protocols/line_protocol_reference/)
and translates it into [InfluxDB line protocol format](/{{< latest "influxdb" "v1" >}}/write_protocols/line_protocol_reference/)
for storage in InfluxDB. Telegraf's extensible architecture makes it easy to
create [plugins](/telegraf/latest/plugins/) that both pull data (input plugins) and push data (output plugins)
create [plugins](/{{< latest "telegraf" >}}/plugins/) that both pull data (input plugins) and push data (output plugins)
to and from different sources and endpoints.
### InfluxDB
@ -86,13 +86,13 @@ InfluxDB Enterprise provides functionality necessary to run a high-availability
#### Hinted handoff
Data is written across nodes using an eventually consistent write model.
All writes are added to the [Hinted Handoff Queue (HHQ)](/enterprise_influxdb/latest/concepts/clustering/#hinted-handoff),
All writes are added to the [Hinted Handoff Queue (HHQ)](/{{< latest "enterprise_influxdb" >}}/concepts/clustering/#hinted-handoff),
then written to other nodes in the cluster.
#### Anti-Entropy
InfluxDB Enterprise's
[Anti-Entropy (AE)](/enterprise_influxdb/latest/administration/anti-entropy/)
[Anti-Entropy (AE)](/{{< latest "enterprise_influxdb" >}}/administration/anti-entropy/)
process ensures data shards in the cluster are in sync. When "entropy" (out-of-sync
data) is detected, AE will repair the affected shards, syncing the missing data.
@ -136,11 +136,7 @@ Data is passed between InfluxDB and Kapacitor via subscriptions.
Kapacitor Enterprise includes configuration options that let you encrypt
communication between your Kapacitor Enterprise and InfluxDB Enterprise clusters.
<div style="display:inline-block;padding:.25em;margin:1em 0 2em; color:#fff;background:#4ed8a0;background:linear-gradient(to right,#4ed8a0 0,#22adf6 100%);border-radius:3px;">
<a href="https://portal.influxdata.com/" target="\_blank" class="sidebar--support-ad--cta" style="color:#fff;text-align:center;">
Try InfluxData Platform Enterprise
</a>
</div>
<a class="btn" href="https://portal.influxdata.com/" target="\_blank">Try InfluxData Platform Enterprise</a>
## Get started
@ -149,4 +145,4 @@ To get started with the **InfluxData 1.x** platform, see
[Installation and Configuration](/platform/installation)
[Getting Started](/platform/introduction/getting-started)
To get started with the **InfluxDB 2.0** platform, see [**InfluxDB Cloud 2.0**](https://v2.docs.influxdata.com/v2.0/get-started/) or [**InfluxDB 2.0 OSS**](https://v2.docs.influxdata.com/v2.0/get-started/).
To get started with the **InfluxDB 2.0** platform, see [**InfluxDB Cloud 2.0**](/influxdb/v2.0/get-started/) or [**InfluxDB 2.0 OSS**](/influxdb/v2.0/get-started/).

View File

@ -1,8 +1,6 @@
---
title: Get started with the InfluxData Platform
description: placeholder
aliases:
- /platform/introduction/getting-started
menu:
platform:
name: Get started
@ -24,14 +22,14 @@ The configuration file for Telegraf specifies where metrics come from and where
* `[[outputs.influxdb]]` - declares how to connect to InfluxDB and the destination database, which is the default telegraf database.
* `[[inputs.cpu]]` - declares how to collect the system cpu metrics to be sent to InfluxDB. Enabled by default.
For details about the configuration file, see [Get started with Telegraf](/{{< latest "telegraf" >}}/introduction/getting-started/).
For details about the configuration file, see [Get started with Telegraf](https://docs.influxdata.com/telegraf/latest/introduction/getting-started/).
## Query data in InfluxDB
As reviewed above, Telegraf is sending system data, including CPU usage, to InfluxDB. There are two ways you can query your InfluxDB data:
* [In Chronograf with the Data Explorer.](/{{< latest "chronograf" >}}/guides/create-a-dashboard/#step-3-create-your-query) Use the builder to select from your existing data and allow Chronograf to format the query for you. Alternatively, manually enter and edit a query. You can move between using the builder and manually editing the query.
* [Using the command line interface.](/{{< latest "influxdb" "v1" >}}/query_language/data_exploration/)
* [In Chronograf with the Data Explorer.](https://docs.influxdata.com/chronograf/latest/guides/create-a-dashboard/#step-3-create-your-query) Use the builder to select from your existing data and allow Chronograf to format the query for you. Alternatively, manually enter and edit a query. You can move between using the builder and manually editing the query.
* [Using the command line interface.](https://docs.influxdata.com/influxdb/latest/query_language/data_exploration/)
**Query example:**
@ -44,10 +42,10 @@ WHERE time > now() - 30m
## Visualize that data in a Chronograf dashboard
Now that you've explored your data with queries, you can build a dashboard in Chronograf to visualize the data. For details, see [Create a dashboard](/{{< latest "chronograf" >}}/guides/create-a-dashboard) and [Using pre-created dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards/).
Now that you've explored your data with queries, you can build a dashboard in Chronograf to visualize the data. For details, see [Create a dashboard](https://docs.influxdata.com/chronograf/latest/guides/create-a-dashboard) and [Using pre-created dashboards](https://docs.influxdata.com/chronograf/latest/guides/using-precreated-dashboards/).
## Create an alert in Kapacitor based on that data
Since InfluxDB is running on `localhost:8086`, Kapacitor finds it during start up and creates several subscriptions on InfluxDB. These subscriptions tell InfluxDB to send all the data it receives from Telegraf to Kapacitor.
For step-by-step instructions on how to set up an alert in Kapacitor based on your data, see [Creating Chronograf alert rules](/{{< latest "chronograf" >}}/guides/create-alert-rules/).
For step-by-step instructions on how to set up an alert in Kapacitor based on your data, see [Creating Chronograf alert rules](https://docs.influxdata.com/chronograf/latest/guides/create-alert-rules/).

View File

@ -1,10 +1,12 @@
---
title: Get started with the InfluxData Platform
description: placeholder
aliases:
- /platform/introduction/getting-started
menu:
platform:
name: Get started
parent: Introduction
weight: 2
---
## Overview
@ -22,14 +24,14 @@ The configuration file for Telegraf specifies where metrics come from and where
* `[[outputs.influxdb]]` - declares how to connect to InfluxDB and the destination database, which is the default telegraf database.
* `[[inputs.cpu]]` - declares how to collect the system cpu metrics to be sent to InfluxDB. Enabled by default.
For details about the configuration file, see [Get started with Telegraf](https://docs.influxdata.com/telegraf/latest/introduction/getting-started/).
For details about the configuration file, see [Get started with Telegraf](/{{< latest "telegraf" >}}/introduction/getting-started/).
## Query data in InfluxDB
As reviewed above, Telegraf is sending system data, including CPU usage, to InfluxDB. There are two ways you can query your InfluxDB data:
* [In Chronograf with the Data Explorer.](https://docs.influxdata.com/chronograf/latest/guides/create-a-dashboard/#step-3-create-your-query) Use the builder to select from your existing data and allow Chronograf to format the query for you. Alternatively, manually enter and edit a query. You can move between using the builder and manually editing the query.
* [Using the command line interface.](https://docs.influxdata.com/influxdb/latest/query_language/data_exploration/)
* [In Chronograf with the Data Explorer.](/{{< latest "chronograf" >}}/guides/create-a-dashboard/#step-3-create-your-query) Use the builder to select from your existing data and allow Chronograf to format the query for you. Alternatively, manually enter and edit a query. You can move between using the builder and manually editing the query.
* [Using the command line interface.](/{{< latest "influxdb" "v1" >}}/query_language/data_exploration/)
**Query example:**
@ -42,10 +44,10 @@ WHERE time > now() - 30m
## Visualize that data in a Chronograf dashboard
Now that you've explored your data with queries, you can build a dashboard in Chronograf to visualize the data. For details, see [Create a dashboard](https://docs.influxdata.com/chronograf/latest/guides/create-a-dashboard) and [Using pre-created dashboards](https://docs.influxdata.com/chronograf/latest/guides/using-precreated-dashboards/).
Now that you've explored your data with queries, you can build a dashboard in Chronograf to visualize the data. For details, see [Create a dashboard](/{{< latest "chronograf" >}}/guides/create-a-dashboard) and [Using pre-created dashboards](/{{< latest "chronograf" >}}/guides/using-precreated-dashboards/).
## Create an alert in Kapacitor based on that data
Since InfluxDB is running on `localhost:8086`, Kapacitor finds it during start up and creates several subscriptions on InfluxDB. These subscriptions tell InfluxDB to send all the data it receives from Telegraf to Kapacitor.
For step-by-step instructions on how to set up an alert in Kapacitor based on your data, see [Creating Chronograf alert rules](https://docs.influxdata.com/chronograf/latest/guides/create-alert-rules/).
For step-by-step instructions on how to set up an alert in Kapacitor based on your data, see [Creating Chronograf alert rules](/{{< latest "chronograf" >}}/guides/create-alert-rules/).