influxdata / influxdata/helm-charts
[DOC] how to build nested telegraf.conf
- Dominant language
- Mustache
- Stars
- 257
- Forks
- 347
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 9
Description
The instructions are a bit vague and I'm unable to sort how to build a telegraf.conf like:
```toml
[[inputs.kafka_consumer]]
brokers = [
"kafka-bootstrap.kafka:9092"
]
client_id = "opmon-telegraf"
consumer_group = "opmon-telegraf"
data_format = "json_v2"
topics = [
"opmon"
]
version = "3.4.0"
[[inputs.kafka_consumer.json_v2]]
measurement_name_path = "measurement"
timestamp_format = "2023-07-13T14:59:51Z"
timestamp_path = "time"
[[inputs.kafka_consumer.json_v2.object]]
tags = [ "tags" ]
[inputs.kafka_consumer.json_v2.object.fields]
key = "fields"
```
Contributor guide
Research direction
Locate the Helm chart documentation that explains building telegraf.conf and compare its instructions with the nested TOML example in this issue. Clarify the steps needed to reproduce the shown inputs.kafka_consumer configuration, then verify that the documentation accurately reflects the example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100