Skip to content
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.

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

Default Sidecar collector in configuration for stateless clients? – features request #12279

Closed
vigo332 opened this issue Mar 14, 2022 · 1 comment

Comments

@vigo332
Copy link

vigo332 commented Mar 14, 2022

Hi, Developers,

New to Graylog.
I managed to get a cluster of 500 stateless CentOS 7 nodes installed with graylog-sidecar and filebeat. The feature I would like to have is a default sidecar collector when a new node joins, and persistent node-id:

Eg, when a node reboot, it will boot to the image, and start afresh, and it will rerun the graylog-sidecar -service install and get the new node-id. It will connect to the server, but with a new node-id, so I have to configure it to use the collector, it still shows two entries in the sidecar lists with new and old/inactive node-id, they should be merged. I have 500+ stateless clients, when they all reboot, they are all treated new(new node-id).

So two functions needed:
A: retain the node-id when a node-id file is polluted or lost,
B: ability to set a default sidecar collector config on the server, so nodes will work after reimaging and retained the logs.

I checked around briefly, a close request is issue #10454 but don’t find a track of work immediately. Apologies if I missed it. But it is a year from the previous issue.

Thanks,

  1. Describe your environment:

OS Information: CentOS 7.9 3.10.0-1160.45.1.el7.x86_64

Package Version:
graylog -4.2-repository-1-4.noarch

graylog -server-4.2.6-1.noarch

filebeat -8.0.0-1.x86_64

graylog -sidecar-1.1.0-1.x86_64

graylog -sidecar-repository-1-2.noarch

Service logs, configurations, and environment variables:
NA
3. What steps have you already taken to try and solve the problem?
NA

  1. How can the community help?
    A: retain the node-id when a node-id file is polluted or lost,
    B: ability to set a default sidecar collector config on the server, so nodes will work after reimaging and retained the logs.
@mpfz0r
Copy link
Contributor

mpfz0r commented Oct 19, 2022

Hi,

Graylog 5.0 and Sidecar 1.3 will have support for tagged assignments again.
#13433

Regarding your stateless setup, you can also define the node-id yourself directly in the sidecar.yml.
It does not have to be a file (which is the default).
The only importance is that it is unique. So you could even use your hostname, for instance.

HTH

@mpfz0r mpfz0r closed this as completed Oct 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants