influxdata / influxdata/telegraf
jolokia2 input plugin need parse long field into new field and new tags
- Dominant language
- Go
- Stars
- 17.8k
- Forks
- 5.8k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 161
Description
## Feature Request
jolokia2 input plugin need parse long field into new field and new tags
### Proposal:
hbase regionserver jmx have many long fields, which are not inconvenient to select later for stored in influxdb or prometheus
so, jolokia2 input plugin need parse long field into new field and new tags
for example
"Namespace_testnamespace_table_tablexxxx_region_829218468187127c482da79er1cso34o_metric_storeCount": 3
### Current behavior:
the influxdb or prometheus ouput will store as
"Namespace_testnamespace_table_tablexxxx_region_829218468187127c482da79er1cso34o_metric_storeCount": 3
### Desired behavior:
field
storeCount : 3
tag
"namespace": "testnamespace",
"table": "tablexxxx",
"region": "829218468187127c482da79er1cso34o",
### Use case:
1, are inconvenient to select later for stored in influxdb or prometheus
2, long field may be influence the performance of influxdb or prometheus
Contributor guide
Research direction
Start with the jolokia2 input plugin and trace how its fields reach the InfluxDB or Prometheus output. Use the supplied HBase JMX key/value as the acceptance example, and clarify parsing rules for namespace, table, region, and metric names before implementation. Done means the value is emitted as storeCount with the requested tags.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, prometheus
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100