Skip to content
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

Add internal telemetry for identifying when the file source is reading to EOF for deleted files #18864

Open
neuronull opened this issue Oct 17, 2023 · 0 comments
Labels
domain: observability Anything related to monitoring/observing Vector source: file Anything `file` source related type: enhancement A value-adding code change that enhances its existing functionality.

Comments

@neuronull
Copy link
Contributor

Users come across the behavior described in #11742 , and part of the problem is there is not much telemetry that Vector provides users to help understand what might be causing the behavior they are seeing.

This issue represents the work to add this internal telemetry. Note that due to the nature of the code in question , the implementation will need to be performant and will need to be performance tested.

@neuronull neuronull added source: file Anything `file` source related type: feature A value-adding code addition that introduce new functionality. type: enhancement A value-adding code change that enhances its existing functionality. domain: observability Anything related to monitoring/observing Vector and removed type: feature A value-adding code addition that introduce new functionality. labels Oct 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
domain: observability Anything related to monitoring/observing Vector source: file Anything `file` source related type: enhancement A value-adding code change that enhances its existing functionality.
Projects
None yet
Development

No branches or pull requests

1 participant