8000 Duplicate logs in graphql clients when vector config is reloaded by config watcher · Issue #23027 · vectordotdev/vector · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
8000

Duplicate logs in graphql clients when vector config is reloaded by config watcher #23027

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.

Sign up for GitHub

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

Jump to bottom
Open
utibeabasi6 opened this issue May 11, 2025 · 0 comments
Open

Duplicate logs in graphql clients when vector config is reloaded by config watcher #23027

utibeabasi6 opened this issue May 11, 2025 · 0 comments
Labels
type: bug A code related bug.

Comments

@utibeabasi6
Copy link

A note for the community

  • 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

Logs are getting duplicated in the graphql client when i have the --watch-config flag set and i make a change to the config file
Ive seen this happening on both the macos and alpine versions

How to reprocuce

  • Start vector with the graphql api enabled and --watch-config flag set
  • Subscribe to log events using the outputEventsByComponentIdPatterns graphql subscription
  • Make a change to the config file and save
  • The logs get duplicated

Before reloading the config

Image

After reloading the config

Image

Configuration

Version

0.46.1 (aarch64-apple-darwin 9a19e8a 2025-04-14 18:36:30.707862743)

Debug Output

Example Data

No response

Additional Context

No response

References

No response
@utibeabasi6 utibeabasi6 added the type: bug A code related bug. label May 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: bug A code related bug.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@utibeabasi6
0