Skip to content

improve dropped point logging [port to main-2.x] #26295

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
davidby-influx opened this issue Apr 18, 2025 · 0 comments · Fixed by #26303
Closed

improve dropped point logging [port to main-2.x] #26295

davidby-influx opened this issue Apr 18, 2025 · 0 comments · Fixed by #26303
Assignees
Labels

Comments

@davidby-influx
Copy link
Contributor

Port #26252 to main-2.x

@davidby-influx davidby-influx self-assigned this Apr 18, 2025
davidby-influx added a commit that referenced this issue Apr 22, 2025
Log the reason for a point being dropped,
the type of boundary violated, and the
time that was the boundary. Prints the
maximum and minimum points (by time)
that were dropped

closes #26252

* fix: better time formatting and additional testing

* fix: differentiate point time boundary violations

* chore: clean up switch statement

* fix: improve error messages

(cherry picked from commit 62e803e)

closes #26295
@davidby-influx davidby-influx linked a pull request Apr 22, 2025 that will close this issue
davidby-influx added a commit that referenced this issue May 6, 2025
Log the reason for a point being dropped,
the type of boundary violated, and the
time that was the boundary. Prints the
maximum and minimum points (by time)
that were dropped

closes #26252

(cherry picked from commit 62e803e)

closes #26295
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant