Adding upstream version 1.34.4.

Signed-off-by: Daniel Baumann <daniel@debian.org>

.github/ISSUE_TEMPLATE/BUG_REPORT.yml

@@ -0,0 +1,74 @@
+name: Bug Report
+description: Create a bug report to help us improve
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking time to fill out this bug report! We reserve Telegraf issues for bugs for reproducible problems.
+        Please redirect any questions about Telegraf usage to our [Community Slack](https://influxdata.com/slack) or [Community Page](https://community.influxdata.com/) we have a lot of talented community members there who could help answer your question more quickly.
+  - type: textarea
+    id: config
+    attributes:
+      label: Relevant telegraf.conf
+      description: Place config in the toml code section. This will be automatically formatted into toml, so no need for backticks.
+      render: toml
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Logs from Telegraf
+      description: Please include the Telegraf logs, ideally with `--debug` used.
+      render: text
+    validations:
+      required: true
+  - type: input
+    id: system-info
+    attributes:
+      label: System info
+      description: Include Telegraf version, operating system, and other relevant details
+      placeholder: ex. Telegraf 1.20.0, Ubuntu 20.04, Docker 20.10.8
+    validations:
+      required: true
+  - type: textarea
+    id: docker
+    attributes:
+      label: Docker
+      description: If your bug involves third party dependencies or services, it can be very helpful to provide a Dockerfile or docker-compose.yml that reproduces the environment you're testing against.
+    validations:
+      required: false
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: Steps to reproduce
+      description: Describe the steps to reproduce the bug.
+      value: |
+        1.
+        2.
+        3.
+        ...
+    validations:
+      required: true
+  - type: textarea
+    id: expected-behavior
+    attributes:
+      label: Expected behavior
+      description: Describe what you expected to happen when you performed the above steps.
+    validations:
+      required: true
+  - type: textarea
+    id: actual-behavior
+    attributes:
+      label: Actual behavior
+      description: Describe what actually happened when you performed the above steps.
+    validations:
+      required: true
+  - type: textarea
+    id: additional-info
+    attributes:
+      label: Additional info
+      description: Include gist of relevant config, logs, etc.
+    validations:
+      required: false
+

.github/ISSUE_TEMPLATE/FEATURE_REQUEST.yml

@@ -0,0 +1,37 @@
+name: Feature request
+description: Create a feature request to make Telegraf more awesome
+labels: ["feature request"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking time to share with us this feature request! Please describe why you would like this feature to be added to Telegraf and how you plan to use it to make your life better.
+  - type: textarea
+    id: use-case
+    attributes:
+      label: Use Case
+      description: Describe how you plan to use this feature. 
+    validations:
+      required: true
+  - type: textarea
+    id: expected-behavior
+    attributes:
+      label: Expected behavior
+      description: Describe what you expected to happen when you performed the above steps.
+    validations:
+      required: true
+  - type: textarea
+    id: actual-behavior
+    attributes:
+      label: Actual behavior
+      description: Describe what actually happened when you performed the above steps.
+    validations:
+      required: true
+  - type: textarea
+    id: additional-info
+    attributes:
+      label: Additional info
+      description: Include gist of relevant config, logs, etc.
+    validations:
+      required: false
+

.github/ISSUE_TEMPLATE/SUPPORT.yml

@@ -0,0 +1,22 @@
+name: Support request
+description: Open a support request
+labels: ["support"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        WOAH, hold up. This isn't the best place for support questions. 
+        You can get a faster response on slack or forums:
+
+        Please redirect any QUESTIONS about Telegraf usage to 
+        - InfluxData Slack Channel: https://www.influxdata.com/slack 
+        - InfluxData Community Site: https://community.influxdata.com
+
+        Check the documentation for the related plugin including the troubleshooting
+        section if available.
+
+        https://docs.influxdata.com/telegraf
+        https://github.com/influxdata/telegraf/tree/master/docs
+  - type: textarea
+    attributes:
+      label: "Please direct all support questions to Slack or the forums. Thank you."