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
Starting the sidecar when the graylog server is unavailable doesn't start any collector processes, even if there are generated collector configs available locally.
Whether it makes sense to start collectors when the graylog server is down is debatable, of course. I think it is useful because some collectors are able to buffer messages if the graylog inputs are not available. Also, some collectors might not even send everything to graylog servers but also to other processes. Additionally, in the future there might be separate graylog ingest nodes which can be available while the API server is not.
The sidecar needs to cache the backend information locally to make this possible.
Steps to reproduce the problem
Configure collectors and assign the config to a sidecar
Start sidecar and wait until collectors are started
Problem description
Starting the sidecar when the graylog server is unavailable doesn't start any collector processes, even if there are generated collector configs available locally.
Whether it makes sense to start collectors when the graylog server is down is debatable, of course. I think it is useful because some collectors are able to buffer messages if the graylog inputs are not available. Also, some collectors might not even send everything to graylog servers but also to other processes. Additionally, in the future there might be separate graylog ingest nodes which can be available while the API server is not.
The sidecar needs to cache the backend information locally to make this possible.
Steps to reproduce the problem
Environment
The text was updated successfully, but these errors were encountered: