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
Sometimes our remote systems stop outputting events. When this happens its fatal until restart.
vector[1972]: 2025-12-05T02:55:24.938488Z WARN sink{component_kind="sink" component_id=output component_type=vector}:request{request_id=89517}: vector::sinks::util::retries: Internal log [Request timed out. If this happens often while the events are actually reaching their destination, try decreasing `batch.max_bytes` and/or using `compression` if applicable. ...
Other remotes dont usually show any issue at the same time and its very infrequent.
vector_logging_server is a DNS name resolving to multiple records (kubernetes nodeport)
I'm not entirely sure how to troubleshoot this. We recently updated to 0.51.1 to see if the issue would go away, it didnt. Theory is ever a stalled connection or stalled dns request. Is either a likely cause?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Sometimes our remote systems stop outputting events. When this happens its fatal until restart.
This is the sink configuration.
Other remotes dont usually show any issue at the same time and its very infrequent.
vector_logging_server is a DNS name resolving to multiple records (kubernetes nodeport)
I'm not entirely sure how to troubleshoot this. We recently updated to 0.51.1 to see if the issue would go away, it didnt. Theory is ever a stalled connection or stalled dns request. Is either a likely cause?
Beta Was this translation helpful? Give feedback.
All reactions