Add support for NaN to InfluxDB Publisher
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
If a NaN is passed to InfluxDB the publisher will log an "invalid number" error. It'd be helpful to support NaN in the publisher. NaN support in InfluxDB wasn't introduced until Influx 2.0, we're still on 1.x. This thread suggests using null in the meantime. I'm not sure how this ends up looking on the Grafana end, that should be investigated when this is solved.
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
No file or test is named. Start by locating the InfluxDB publisher and its handling of invalid numbers, then investigate how InfluxDB 1.x represents NaN values and how Grafana renders the result. Done means NaN input is handled without the invalid-number error and its Grafana behavior is understood.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grafana, python
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100