influxdata / influxdata/telegraf
Telegraf Aerospike Plugin with Latency Info
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 17.8k
- Forks
- 5.8k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 161
Description
### Use Case
We can get number of operation took >1ms,>8ms and >64ms in Aerospike Server
### Expected behavior
We will get node statistics & stats for all the configured namespaces with every namespace Read, Write, UDF and Query operations latency in counts
### Actual behavior
We are getting only queries aerospike server(s) and get node statistics & stats for all the configured namespaces
### Additional info
_No response_
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Telegraf Aerospike plugin and reviewing how it currently collects node and namespace statistics. Check how Aerospike exposes operation latency counts for reads, writes, UDFs, and queries; done means those per-namespace latency metrics are collected alongside the existing statistics and covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100