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
Using the automatic-namespacing scenario, and after successfully starting with the command "vector -C /etc/vector -w", if you edit the configuration in the sources, transforms, and sinks directories and find that hot reloading is not working
jszwedko
changed the title
--watch-config hot reloading is not working
--watch-config hot reloading is not working with config namespacing
May 22, 2024
@Ficklecode note that --watch-config only looks for changes to loaded files. I don't believe it rescans for new ones (though ideally it should). Can you confirm if you are making edits to existing files or writing new ones?
@jszwedko It is to modify the existing files before startup, and according to my tests, when using the command 'vector -C /etc/vector -w', creating, modifying, and deleting configurations under /etc/vector can all be hot-reloaded. However, hot reloading does not take effect when modifying files in /etc/vector/sources. I tried specifying /etc/vector/* at startup, and automatic-namespacing causes an exception to be thrown
A note for the community
Problem
Using the automatic-namespacing scenario, and after successfully starting with the command "vector -C /etc/vector -w", if you edit the configuration in the sources, transforms, and sinks directories and find that hot reloading is not working
https://vector.dev/docs/reference/configuration/#automatic-namespacing
Configuration
No response
Version
0.38.0
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: