Influxdata
/
docs-v2
mirror of https://github.com/influxdata/docs-v2.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Remove all cloud native subscription content (#4663) 

* remove all cloud native subscription content

* removed videos related to native subscriptions
pull/4697/head^2
Scott Anderson 2023-01-11 10:11:00 -07:00 committed by GitHub
parent f311c76a84
commit e475e19df8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
10 changed files with 2 additions and 543 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

100
content/influxdb/cloud/reference/json-parsing.md
View File

@ -1,100 +0,0 @@
---
title: JSON parsing examples
description: >
Review example JSON parsing rules for native subscriptions.
menu:
influxdb_cloud_ref:
name: JSON parsing examples
weight: 8
influxdb/v2.0/tags: [mqtt]
related:
---
Use the following examples to help you set up JSON parsing rules using [JSON Path](https://jsonpath.com/)
for [native subscriptions](/influxdb/cloud/write-data/no-code/native-subscriptions). All JSON paths start with a `$`.
## Example MQTT message in "flat" JSON format
```json
{
"device_type":"temperature_sensor",
"device_id":2036,
"model_id":"KN24683",
"temperature":25.0,
"time":1653998899010000000,
"error_state":"in_error"
}
```
With "flat" JSON, all values are at the root level (`$`) and are referenced with dot notation.
| InfluxDB Element | JSON Path | Data Type | Parsed Result |
| :--------------- | :-------------- | :---------- | :------------------- |
| Measurement | `$.device_type` | String | "temperature_sensor" |
| Timestamp | `$.time` | Nanoseconds | 1653998899010000000 |
| Tag | `$.device_id` | Integer | 2036 |
| Field 1 | `$.temperature` | Float | 25.0 |
| Field 2 | `$.error_state` | String | "in_error" |
## Example MQTT message with nested JSON objects
```json
{
"device_information": {
"device_type":"temperature_sensor",
"device_id":2036,
"model_id":"KN24683"
},
"temperature":25.0,
"time":1667247643,
"error_state":"in_error"
}
```
| InfluxDB Element | JSON Path | Data Type | Parsed Result |
| :--------------- | :--------------------------------- | :-------- | :------------------- |
| Measurement | `$.device_information.device_type` | String | "temperature_sensor" |
| Timestamp | `$.time` | Seconds | 1653998899010000000 |
| Tag | `$.device_information.device_id` | Integer | 2036 |
| Field 1 | `$.temperature` | Float | 25.0 |
| Field 2 | `$.error_state` | String | "in_error" |
## Example MQTT message with JSON arrays
Currently, there is limited support for working with key/value pairs that are held within
a JSON array. Entire arrays cannot be loaded into a single field value, but if your messages
have a fixed number of values in the array being passed, you can specify an array index number
in your JSON path.
```json
{
"device_information":{
"device_type":"temperature_sensor",
"device_id":2309,
"model_id":"KN24683"
},
"time":1653998899010000000,
"temperature":25.0,
"error_state":"in_error",
"errors_encountered":[
{
"time_encountered":"2022:05:30:23:11",
"error_number":403
},
{
"time_encountered":"2022:06:01:12:15",
"error_number":404
}
]
}
```
| InfluxDB Element | JSON Path | Data Type | Parsed Result |
| :--------------- | :-------------------------------------- | :---------- | :------------------- |
| Measurement | `$.device_information.device_type` | String | "temperature_sensor" |
| Timestamp | `$.time` | Nanoseconds | 1653998899010000000 |
| Tag | `$.device_information.device_id` | Integer | 2036 |
| Field 1 | `$.temperature` | Float | 25.0 |
| Field 2 | `$.error_state` | String | "in_error" |
| Field 3 | `$.errors_encountered.[0].error_number` | Integer | 403 |
| Field 4 | `$.errors_encountered.[1].error_number` | Integer | 404 |

213
content/influxdb/cloud/write-data/no-code/native-subscriptions.md
View File

@ -1,213 +0,0 @@
---
title: Set up native MQTT subscriptions
weight: 102
aliases:
- /influxdb/cloud/write-data/no-code/load-data/
description: >
Use native subscriptions to ingest data.
menu:
influxdb_cloud:
name: Native MQTT subscriptions
parent: Write data
influxdb/v2.0/tags: [mqtt, native subscription]
---
{{% note %}}
This feature is available with usage-based plans only. For more information, see [InfluxDB Cloud Plans](/influxdb/cloud/account-management/pricing-plans/).
{{% /note %}}
To ingest MQTT (Message Queuing Telemetry Transport) data into InfluxDB, do the following to set up a native subscription:
1. [Subscribe to an MQTT topic](#subscribe-to-an-mqtt-topic) in InfluxDB Cloud by configuring an MQTT broker, and specifying the topic(s) to subscribe to.
2. [Define parsing rules](#define-parsing-rules) for JSON or regex data (line protocol requires no configuration).
{{% note %}}
For troubleshooting help, see [Troubleshoot MQTT ingest errors](/influxdb/cloud/write-data/troubleshoot/#troubleshoot-mqtt-ingest-errors/).
{{% /note %}}
#### Subscribe to an MQTT topic
1. In the navigation menu on the left, click **Load Data** > **Native Subscriptions**.
{{< nav-icon "data" >}}
2. Click **+ Create Subscription**.
3. On the **Setting Up - MQTT Subscriber** page, under **Connect to Broker**, enter the following:
- Subscription Name
- Description (optional)
- Protocol
- Hostname or IP address (hostname or URL of the MQTT broker)
- Port (TCP/IP port number the MQTT broker uses)
- Security details. Choose one of the following:
- **None**
- **Basic** (username/password)
- **Certificate**
4. Under **Subscribe to a topic**, in the **Topic** field, enter the MQTT topic name to subscribe to. Note, MQTT brokers typically support wildcard subscriptions with the wildcard characters `+` and `#`.
- To subscribe to all topics in a directory, use `+`. For example, if an `iotdevices` directory includes two directories called `asia` and `europe`, to subscribe to a `sensor` topic in either directory, use `iotdevices/+/sensors` to subscribe to `iotdevices/asia/sensors`, and `iotdevices/europe/sensors`.
- To subscribe to all topics in a directory, use `#`. For example, `iotdevices/#` subscribes to all topics in the `iotdevices` directory. For more information about MQTT subscriptions and wildcards, see [the MQTT specification for Topic Names and Topic Filters](https://docs.oasis-open.org/mqtt/mqtt/v5.0/os/mqtt-v5.0-os.html#_Toc3901241).
5. Under **Write Destination**, select an existing InfluxDB bucket to write data to or click **+ Create bucket**. For more information, see [Create a bucket](/influxdb/cloud/organizations/buckets/create-bucket/).
6. Click **Save Subscription** to save and start running the MQTT subscription.
#### Define parsing rules
{{% note %}}
JSON parsing is faster and more efficient than string parsing. We recommend using JSON parsing when your MQTT messages are in JSON format. For examples, see [JSON parsing examples](/influxdb/cloud/reference/json-parsing/).
{{% /note %}}
- Under **Define Data Parsing Rules**, select one of the following MQTT data formats:
- **Line protocol** (no configuration required)
- **JSON**. To define parsing rules to ingest JSON data, click the **JSON** tab below.
- **String**. To define parsing rules to ingest String data, click the **String** tab below.
{{< tabs-wrapper >}}
{{% tabs %}}
[Line protocol](#)
[JSON](#)
[String](#)
{{% /tabs %}}
<!-------------------------------- BEGIN Line protocol -------------------------------->
{{% tab-content %}}
Use line protocol to write data into InfluxDB. Line protocol doesn't require any parsing or configuration.
- Select a **Timestamp precision** from the dropdown menu:
- **MS**: Milliseconds
- **S**: Seconds
- **US**: Microseconds
- **NS**: Nanoseconds
{{% /tab-content %}}
<!-------------------------------- BEGIN JSON -------------------------------->
{{% tab-content %}}
To associate **JSON** key-value pairs with **InfluxDB elements** (measurements, timestamps, fields, or tags) using parsing rules, complete the following steps:
{{< expand-wrapper >}}
{{% expand "Example JSON" %}}
```json
{
"device_type":"temperature_sensor",
"device_id":2036,
"model_id":"KN24683",
"temperature":25.0,
"time":1653998899010000000,
"error_state":"in_error"
}
```
{{% /expand %}}
{{< /expand-wrapper >}}
1. On the **Setting Up - MQTT Connector** page, under **Data Format**, select the **JSON** format:
2. (Optional) In the **JSON path to timestamp** field, specify the path in the
MQTT message to the JSON key that holds the timestamp.
For the [example above](#example-json), use `$.time`.
Otherwise, InfluxDB automatically assigns a timestamp when messages are ingested into InfluxDB.
***Important***: *Configure the timestamp format that **matches the format** in your messages.*
3. Under **Measurement**, do one of the following:
- **Use a JSON path to identify the measurement name**:
1. Select the **JSON Path** {{< icon "toggle-off" >}} toggle.
2. Enter the **JSON path** (starting with `$.`) to assign the InfluxDB measurement key.
For the [example above](#example-json), enter `$.device_type`.
- **Explicitly set the measurement name**:
1. Select the {{< icon "toggle" >}} **Name** toggle.
2. Enter a measurement name.
4. Select the **Data Type** for the measurement.
5. Specify the JSON paths to **tag** and **field** names as needed, and then
select the **data type** for the tag or field. At least one field is required.
For the [example above](#example-json), add fields with the JSON paths
`$.temperature` and `$.error_state` and tags with the paths `$.device_id` and `$.model_id`.
{{% note %}}
The JSON parser supports JSON paths with arrays.
For example, `$.device_information.errors_encountered[0].error_number`.
{{% /note %}}
{{% /tab-content %}}
<!-------------------------------- BEGIN String -------------------------------->
{{% tab-content %}}
To associate **String** key-value pairs with **InfluxDB elements** (measurements, timestamps, fields, or tags),
Use regular expressions to identify each element in a string.
{{% note %}}
#### Parse with regular expressions
InfluxDB Native Subscriptions use Java-flavored regular expression patterns
to identify InfluxDB elements in a string.
Parsing rules only support finding **one value at a time**.
{{% /note %}}
Complete the following steps:
{{< expand-wrapper >}}
{{% expand "Example string" %}}
```string
device_type=temperature_sensor
device_id=2036
model_id=KN24683
temperature=25.0
time=1653998899010000000
error_state=in_error
```
{{% /expand %}}
{{< /expand-wrapper >}}
1. On the **Setting Up - MQTT Connector** page, under **Data Format**, select the **String** format.
2. (Optional) In the **Regex pattern to find timestamp** field, enter the regex
(regular expression) to find the timestamp in the MQTT message.
Otherwise, InfluxDB automatically assigns a timestamp when messages are ingested into InfluxDB.
For the [example above](#example-string), use `time=([\s\S]*?)\n` to capture
everything between `time=` and the next newline (`\n`).
***Important***: *Configure the timestamp format that **matches the format** in your messages.*
3. Under **Measurement**, do one of the following:
- **Use a regular expression to identify the measurement name**:
1. Select the **Regex** {{< icon "toggle-off" >}} toggle.
2. Enter a regular expression to identify the measurement name.
For the [example above](#example-string), use `device_type=([\s\S]*?)\n`
to capture everything between `device_type=` and the next newline (`\n`)
In this case the measurement would be `temperature_sensor`.
- **Explicitly set the measurement name**:
1. Select the {{< icon "toggle" >}} **Name** toggle.
2. Enter a measurement name.
4. Enter **Tag** and **Field**. At least one field is required. For tag and field names,
use the regex to find the tag or field name, and what to capture.
For the [example above](#example-string) use `device_id=(\d{4})` to
capture the 4 digits after `device_id=`.
{{% note %}}
#### All fields are written as strings
When parsing **field values** from a string, the regular expression returns
a string and the field is written to InfluxDB as a string.
To cast field values to other data types, use
[type conversion functions](/{{< latest "flux" >}}/function-types/#type-conversions)
when querying the data.
{{% /note %}}
{{% /tab-content %}}
{{< /tabs-wrapper >}}

148
content/influxdb/v2.3/write-data/no-code/load-data.md
View File

@ -4,7 +4,7 @@ seotitle: Load data source in UI
list_title: Load data source in UI
weight: 101
description: >
Load data from sources in the InfluxDB user interface (UI). Choose from popular client libraries (such as Python, Ruby, Scala, and more!), load data with a Telegraf plugin (like MQTT Consumer, MySQL, File, and many more!), and InfluxDB Cloud users have the option to load data natively by subscribing to an MQTT topic.
Load data from sources in the InfluxDB user interface (UI). Choose from popular client libraries (such as Python, Ruby, Scala, and more!), load data with a Telegraf plugin (like MQTT Consumer, MySQL, File, and others).
menu:
influxdb_2_3:
name: Load data source in UI
@ -17,7 +17,6 @@ Load data from the following sources in the InfluxDB user interface (UI):
- [Line protocol](#load-data-using-line-protocol)
- [Client libraries](#load-data-from-a-client-library-in-the-ui)
- [Telegraf plugins](#load-data-from-a-telegraf-plugin-in-the-ui)
- {{% cloud-only %}}[Native MQTT subscriptions](#set-up-a-native-mqtt-subscription){{% /cloud-only %}}
### Load CSV or line protocol in UI
@ -84,148 +83,3 @@ Load CSV or line protocol data by uploading a file or pasting the data manually
9. Once Telegraf is running, click **Listen for Data** to confirm Telegraf is successfully sending data to InfluxDB.
Once confirmed, a **Connection Found!** message appears.
10. Click **Finish**. Your Telegraf configuration name and the associated bucket name appear in the list of Telegraf configurations.
{{% cloud-only %}}
### Set up a native subscription
{{% note %}}
This feature is available with usage-based plans only. For more information, see [InfluxDB Cloud Plans](/influxdb/cloud/account-management/pricing-plans/).
{{% /note %}}
To ingest MQTT (Message Queuing Telemetry Transport) data into InfluxDB, do the following to set up a native subscription:
1. [Subscribe to an MQTT topic](#subscribe-to-an-mqtt-topic) in InfluxDB Cloud by configuring an MQTT broker, and specifying the topic(s) to subscribe to.
2. [Define parsing rules](#define-parsing-rules) for JSON or regex data (line protocol requires no configuration).
{{% note %}}
For troubleshooting help, see [Troubleshoot MQTT ingest errors](/influxdb/cloud/write-data/troubleshoot/#troubleshoot-mqtt-ingest-errors/)
{{% /note %}}
#### Subscribe to an MQTT topic
1. In the navigation menu on the left, click **Load Data** > **Native Subscriptions**.
{{< nav-icon "data" >}}
2. Click **+ Create Subscription**.
3. On the **Setting Up - MQTT Subscriber** page, under **Connect to Broker**, enter the following:
- Subscription Name
- Description _(optional)_
- Protocol
- Hostname or IP address (hostname or URL of the MQTT broker)
- Port (TCP/IP port number the MQTT broker uses)
- Security details. Choose one of the following:
- **None**
- **Basic** (username/password)
- **Certificate**
4. Under **Subscribe to a topic**, in the **Topic** field, enter the MQTT topic name to subscribe to. Note, MQTT brokers typically support wildcard subscriptions with the wildcard characters `+` and `#`.
- To subscribe to all topics in a directory, use `+`. For example, if an `iotdevices` directory includes two directories called `asia` and `europe`, to subscribe to a `sensor` topic in either directory, use `iotdevices/+/sensors` to subscribe to `iotdevices/asia/sensors`, and `iotdevices/europe/sensors`.
- To subscribe to all topics in a directory, use `#`. For example, `iotdevices/#` subscribes to all topics in the `iotdevices` directory. For more information about MQTT subscriptions and wildcards, see [the MQTT specification for Topic Names and Topic Filters](https://docs.oasis-open.org/mqtt/mqtt/v5.0/os/mqtt-v5.0-os.html#_Toc3901241).
5. Under **Write Destination**, select an existing InfluxDB bucket to write data to or click **+ Create bucket**. For more information, see [Create a bucket](/influxdb/cloud/organizations/buckets/create-bucket/).
6. Click "Save Subscription" to save and start running the MQTT subscription.
#### Define parsing rules
{{% note %}}
JSON parsing is faster and more efficient than string parsing. We recommend using JSON parsing when your MQTT messages are in JSON format.
{{% /note %}}
- Under **Define Data Parsing Rules**, select one of the following MQTT data formats:
- **Line protocol** (no configuration required)
- **JSON**. To define parsing rules to ingest JSON data, click the **JSON** tab below.
- **String**. To define parsing rules to ingest String data, click the **String** tab below.
{{< tabs-wrapper >}}
{{% tabs %}}
[Line protocol](#)
[JSON](#)
[String](#)
{{% /tabs %}}
<!-------------------------------- BEGIN Line protocol -------------------------------->
{{% tab-content %}}
Use line protocol to write data into InfluxDB. Line protocol doesn't require any parsing or configuration.
Select a **Timepstamp precision** from the dropdown menu:
- **MS**: Milliseconds
- **S**: Seconds
- **US**: Microseconds
- **NS**: Nanoseconds
{{% /tab-content %}}
<!-------------------------------- BEGIN JSON -------------------------------->
{{% tab-content %}}
Associate **JSON** key/value pairs with **InfluxDB elements** (measurements, timestamps, fields, or tags) using parsing rules.
{{% expand "Example JSON" %}}
```
{
"device_type":"temperature_sensor",
"device_id":2036,
"model_id":"KN24683",
"temperature":25.0,
"time":1653998899010000000,
"error_state":"in_error"
}
```
{{% /expand %}}
1. On the **Setting Up - MQTT Connector** page, under **Data Format**, do the following:
1. (Optional) In the **JSON path to timestamp** field, specify the path in the MQTT message to the JSON key that holds the timestamp: for the example above, `"time":1653998899010000000`. Otherwise, InfluxDB automatically assigns a timestamp when messages are ingested into InfluxDB.
{{% warn %}}
**Important**: Configure the timestamp format that matches the format in your messages.
{{% /warn %}}
2. Configure the JSON parsing rules:
1. Under **Measurement**, enter the **JSON path** (start with `$.`) to assign the InfluxDB measurement key. For the above example, enter `$.device_type`.
3. Select the **Data Type** for the measurement.
4. Specify the JSON paths to tag and field names as needed, and then select the data type for the tag or field. At least one field is required. For the above example, add fields with the JSON paths `$.temperature` and `$.error_state` and a tag with the path `$.error_state`.
Note that JSON paths with arrays are supported, for example, `$.device_information.errors_encountered[0].error_number`.
{{% /tab-content %}}
<!-------------------------------- BEGIN String -------------------------------->
{{% tab-content %}}
Associate **String** key/value pairs with **InfluxDB elements** (measurements, timestamps, fields, or tags).
1. On the **Setting Up - MQTT Connector** page, under **Data Format**, do the following:
1. (Optional) In the **Regex pattern to find timestamp** field, enter the regex (regular expression) to find the timestamp in the MQTT message. Otherwise, InfluxDB automatically assigns a timestamp when messages are ingested into InfluxDB.
{{% note %}}
**Note**: Parsing rules only support finding one value at a time.
{{% /note %}}
For example, if the timestamp string is `time=1653998899010000000`, use a regex to find the string you're looking for and capture the timestamp:
- `time=([\s\S]*?)\n` (captures value after `=` until the EOL (end of line) is reached)
- `time=([\s\S]*?),` (captures value after `=` until comma is reached)
{{% warn %}}
**Important**: Configure the timestamp format that matches the format in your messages.
{{% /warn %}}
2. Under **Measurement**, if the string is `device_type=temperature_sensor` use regex to find the measurement name. For example:
- `device_type=([\s\S]*?)\n` captures the value after the `=` until the EOL (end of line) is reached), in this case the value would be `temperature_sensor`.
3. Select the **Data Type** for the measurement.
4. Enter **Tag** and **Field**. At least one field is required. For tag and field names, use the regex to find the tag or field name, and what to capture. For example:
- `device_id=\d\d\d\d-([0-9][0-9][0-9][0-9])` (matches on the `device_id=` and also matches on the first four digits of the device id, and then captures the four digits.
5. Select the **Data Type** for the tag or field.
{{% /tab-content %}}
{{< /tabs-wrapper >}}
{{% /cloud-only %}}

32
content/influxdb/v2.3/write-data/troubleshoot.md
View File

@ -28,7 +28,6 @@ Learn how to avoid unexpected results and recover from errors when writing to In
- [Handle `write` and `delete` responses](#handle-write-and-delete-responses)
- [Troubleshoot failures](#troubleshoot-failures)
- [Troubleshoot rejected points](#troubleshoot-rejected-points)
- [Troubleshoot MQTT ingest errors](troubleshoot-mqtt-ingest-errors)
{{% /cloud-only %}}
@ -321,34 +320,3 @@ InfluxDB logs the following `rejected_points` entry to the `_monitoring` bucket:
| _measurement | _field | _value | bucket | field | gotType | measurement | reason | wantType |
|:------------------|:-------|:-------|:-------------------|:--------------|:---------|:------------|:----------------------------------|:---------|
| rejected_points | count | 1 | a7d5558b880a93da | temperature | String | airSensors | field type mismatch with schema | Float |
{{% cloud-only %}}
## Troubleshoot MQTT ingest errors
If you're having issues ingesting [MQTT data](/influxdb/v2.3/write-data/no-code/load-data/#set-up-a-cloud-native-subscription/) into InfluxDB, try the following:
- [Validate parsing rules and subscription path](#validate-parsing-rules-and-subscription-path).
- [View the `_monitoring` bucket](#view-the-monitoring-bucket) to check for parsing errors.
- [Set up a deadman check](#set-up-a-deadman-check).
### Validate parsing rules and subscription path
Verify that your parsing rules don’t have any syntax or other errors by copying and pasting your MQTT message and your parsing rules into a tool. For JSON, we recommend [JSON Path](https://jsonpath.com/). For Regex, we recommend [Regex 101](https://regex101.com/).
### View the `_monitoring`bucket
If your parsing rules and subscription path are valid, check for InfluxDB Cloud errors from executing parsing rules in the `_monitoring` bucket.
1. In the navigation menu on the left, click **Data Explorer**.
2. Select the `_monitoring` bucket, and then the `subscription` measurement.
3. Click the CSV icon to save the contents as a CSV and view error messages.
### Set up a deadman check
If you have a steady stream of MQTT messages, we recommend setting up a deadman alert to detect when messages are not ingested into InfluxDB. See [Create a deadman check](/influxdb/cloud/monitor-alert/checks/create/#deadman-check/).
{{% /cloud-only %}}

1
content/influxdb/v2.4/get-started/write.md
View File

@ -26,7 +26,6 @@ the following:
- [InfluxDB HTTP API](/influxdb/v2.4/reference/api/)
- [`influx` CLI](/influxdb/v2.4/tools/influx-cli/)
- [Telegraf](/{{< latest "telegraf" >}}/)
- {{% cloud-only %}}[MQTT](/influxdb/cloud/write-data/no-code/native-subscriptions/){{% /cloud-only %}}
- [InfluxDB client libraries](/influxdb/v2.4/api-guide/client-libraries/)
This tutorial walks you through the fundamental of using **line protocol** to write

9
content/influxdb/v2.4/write-data/no-code/load-data.md
View File

@ -17,7 +17,6 @@ Load data from the following sources in the InfluxDB user interface (UI):
- [Line protocol](#load-data-using-line-protocol)
- [Client libraries](#load-data-from-a-client-library-in-the-ui)
- [Telegraf plugins](#load-data-from-a-telegraf-plugin-in-the-ui)
- {{% cloud-only %}}[Native MQTT subscriptions](#set-up-a-native-mqtt-subscription){{% /cloud-only %}}
### Load CSV or line protocol in UI
@ -84,11 +83,3 @@ Load CSV or line protocol data by uploading a file or pasting the data manually
9. Once Telegraf is running, click **Listen for Data** to confirm Telegraf is successfully sending data to InfluxDB.
Once confirmed, a **Connection Found!** message appears.
10. Click **Finish**. Your Telegraf configuration name and the associated bucket name appear in the list of Telegraf configurations.
{{% cloud-only %}}
### Set up an MQTT native subscription
For more details about setting up native subscriptions, see [Set up native subscriptions](/influxdb/cloud/write-data/no-code/native-subscriptions).
{{% /cloud-only %}}

1
content/influxdb/v2.5/get-started/write.md
View File

@ -26,7 +26,6 @@ the following:
- [InfluxDB HTTP API](/influxdb/v2.5/reference/api/)
- [`influx` CLI](/influxdb/v2.5/tools/influx-cli/)
- [Telegraf](/{{< latest "telegraf" >}}/)
- {{% cloud-only %}}[MQTT](/influxdb/cloud/write-data/no-code/native-subscriptions/){{% /cloud-only %}}
- [InfluxDB client libraries](/influxdb/v2.5/api-guide/client-libraries/)
This tutorial walks you through the fundamental of using **line protocol** to write

11
content/influxdb/v2.5/write-data/no-code/load-data.md
View File

@ -4,7 +4,7 @@ seotitle: Load data source in UI
list_title: Load data source in UI
weight: 101
description: >
Load data from sources in the InfluxDB user interface (UI). Choose from popular client libraries (such as Python, Ruby, Scala, and more!) or load data with a Telegraf plugin (like MQTT Consumer, MySQL, File, and many more!).
Load data from sources in the InfluxDB user interface (UI). Choose from popular client libraries (such as Python, Ruby, Scala, and more!) or load data with a Telegraf plugin (like MQTT Consumer, MySQL, File, and others).
menu:
influxdb_2_5:
name: Load data source in UI
@ -17,7 +17,6 @@ Load data from the following sources in the InfluxDB user interface (UI):
- [Line protocol](#load-data-using-line-protocol)
- [Client libraries](#load-data-from-a-client-library-in-the-ui)
- [Telegraf plugins](#load-data-from-a-telegraf-plugin-in-the-ui)
- {{% cloud-only %}}[Native MQTT subscriptions](#set-up-a-native-mqtt-subscription){{% /cloud-only %}}
### Load CSV or line protocol in UI
@ -84,11 +83,3 @@ Load CSV or line protocol data by uploading a file or pasting the data manually
9. Once Telegraf is running, click **Listen for Data** to confirm Telegraf is successfully sending data to InfluxDB.
Once confirmed, a **Connection Found!** message appears.
10. Click **Finish**. Your Telegraf configuration name and the associated bucket name appear in the list of Telegraf configurations.
{{% cloud-only %}}
### Set up an MQTT native subscription
For more details about setting up native subscriptions, see [Set up native subscriptions](/influxdb/cloud/write-data/no-code/native-subscriptions).
{{% /cloud-only %}}

15
content/resources/videos/Configuring-and-Parsing-Data-with-InfluxDB-Native-Collector-for-MQTT.md
View File

@ -1,15 +0,0 @@
---
title: Configuring and Parsing Data with InfluxDB Native Collector for MQTT
description: >
Setting up the InfluxDB native collector for MQTT is a simple, three step process. Here, Gary Fowler walks through the configuration process and discusses the different parsing options available.
menu:
resources:
parent: Videos
weight: 162
youtubeID: uI_HYgx_PIQ
date: 2022-7-12
series: [Meet the Developers S7]
metadata: [Meet the Developer Series]
---
{{< resources/video-content >}}

15
content/resources/videos/When-to-use-InfluxDB-Native-Collector-for-MQTT.md
View File

@ -1,15 +0,0 @@
---
title: When to use InfluxDB Native Collector for MQTT
description: >
InfluxDB provides many ways to collect data. The newest one is the Native Collector feature. But when should you use the native collector and when should you use a different option, like Telegraf? Gary Fowler uses MQTT to show the different options and why you might choose one over the other.
menu:
resources:
parent: Videos
weight: 161
youtubeID: I583LSj0bgs
date: 2022-9-12
series: [Meet the Developers S7]
metadata: [Meet the Developer Series]
---
{{< resources/video-content >}}