influxdb: Make clear which agent published invalid timestamps
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
As raised here, we should make it so that if a timestamp that overflows is published to the InfluxDB publisher, the logs indicate which agent the timestamp came from.
We might also consider validating the timestamp on the agent end when publishing, like we do for field names, etc. See the discussion in #466.
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 with the InfluxDB publisher and the agent-side publishing path, then read the discussion in #466 for the timestamp overflow context. Trace how invalid timestamps are logged and make the originating agent identifiable; if pursuing the optional validation, compare it with existing field-name validation. Done means the logs identify the agent for an overflowing timestamp.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100