You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Problem
The interval option in demo_logs is broken since vector 0.28, and it is still broken in vector 0.31. It was still working in vector 0.27. The "interval" option in the "demo_logs" source seems to be rounded up or down to the nearest integer. We should be able to use decimal values such as "0.01" to control how often a new message is created. Now, it behaves as if we put an integer number. For example if we use "interval = 0.49" it will be rounded down to 0 and produce as many messages as possible. If we use "interval = 0.51" it will behave as if we had used "interval = 1" so it will wait one second.
Configuration
[sources.my_source_id]
type = "demo_logs"
format = "json"
interval = 0.1
Version
0.31
Debug Output
No response
Example Data
No response
Additional Context
No response
References
No response
The text was updated successfully, but these errors were encountered:
A note for the community
Problem
The interval option in demo_logs is broken since vector 0.28, and it is still broken in vector 0.31. It was still working in vector 0.27. The "interval" option in the "demo_logs" source seems to be rounded up or down to the nearest integer. We should be able to use decimal values such as "0.01" to control how often a new message is created. Now, it behaves as if we put an integer number. For example if we use "interval = 0.49" it will be rounded down to 0 and produce as many messages as possible. If we use "interval = 0.51" it will behave as if we had used "interval = 1" so it will wait one second.
Configuration
Version
0.31
Debug Output
No response
Example Data
No response
Additional Context
No response
References
No response
The text was updated successfully, but these errors were encountered: