Sidecar Update creates new Nod Id

Hello,

an automated (with Puppet) update of Graylog sidecar from 1.3.0 to 1.5.0 created for every node a new node id.

That’s not what we wanted, but anyway we could fix by reassigning the new nodes to the correct sidecar configurations.

Is there a way to purge (eliminate) the now dead (Unknown) nodes?

Thanks in advance,

Dietmar

Hello @schurd,

You can set global timeout and purge settings under system/configurations/sidecar, unfortunately they can’t be done on a case by case unless you are willing to drop entries from the mongo collection directly.

Hello Wine_Merchant,

thank you very much. This will help…..

Regards,

Dietmar

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.