From 5129932db67f4a4c50213121d6aba1b1c588b2a1 Mon Sep 17 00:00:00 2001
From: noramullen1 <42354779+noramullen1@users.noreply.github.com>
Date: Tue, 13 Oct 2020 11:12:35 -0700
Subject: [PATCH] Add influxdb v2 listener plugin

---
 data/telegraf_plugins.yml | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)

diff --git a/data/telegraf_plugins.yml b/data/telegraf_plugins.yml
index 06309cf98..ba3129447 100644
--- a/data/telegraf_plugins.yml
+++ b/data/telegraf_plugins.yml
@@ -643,6 +643,30 @@ input:
     introduced: 1.9.0
     tags: [linux, macos, windows, data-stores]
 
+  - name: InfluxDB v2 Listener
+    id: influxdb_listener
+    description: |
+      The InfluxDB Listener input plugin listens for requests sent
+      according to the [InfluxDB HTTP API](https://docs.influxdata.com/influxdb/latest/guides/writing_data/).
+      The intent of the plugin is to allow Telegraf to serve as a proxy, or router,
+      for the HTTP `/write` endpoint of the InfluxDB HTTP API.
+
+      > This plugin was previously known as `http_listener`.
+      > To send general metrics via HTTP, use the [HTTP Listener v2 input plugin](#http_listener_v2) instead.
+      >
+      > This plugin is compatible with **InfluxDB 2.x** only.
+
+      The `/write` endpoint supports the `precision` query parameter and can be set
+      to one of `ns`, `u`, `ms`, `s`, `m`, `h`.  All other parameters are ignored and
+      defer to the output plugins configuration.
+
+      When chaining Telegraf instances using this plugin, `CREATE DATABASE` requests
+      receive a `200 OK` response with message body `{"results":[]}` but they are not
+      relayed. The output configuration of the Telegraf instance which ultimately
+      submits data to InfluxDB determines the destination database.
+    introduced: 1.16.0
+    tags: [linux, macos, windows, data-stores]
+
   - name: Intel RDT
     id: intel_rdt
     description: |