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
Use Cases
A recent change to the NATS sink meant we need to flush the connection for each event so we can guarantee that the event was delivered before reporting success.
This could potentially affect the throughput. It could well be worth considering introducing batching to the sink so that we flush only after each batch.0
Version
V0.32.0
The text was updated successfully, but these errors were encountered:
Note: this sort of batching (of NATS messages) would be different from the existing batch concept (batching within a NATS message) in Vector sinks so we wouldn't want to expose it to users in the same way.
A note for the community
Use Cases
A recent change to the NATS sink meant we need to flush the connection for each event so we can guarantee that the event was delivered before reporting success.
This could potentially affect the throughput. It could well be worth considering introducing batching to the sink so that we flush only after each batch.0
Version
V0.32.0
The text was updated successfully, but these errors were encountered: