Graylog inactive sidecars stuck

Hi guys!

At our company we deployed graylog as a solution for collecting logs from our infrastucture. We are at our deployment, in the last step we started deploying the sidecars in our endpoints. For testing the automation of the deployment I had some test cases where I installed several instances of the sidecar on one of our system. I have set the timeout and expiration treshold in our graylog server, however I found that even if the sidecar reaches that time it still is available in the sidecar catalogue. Is there a way to manually remove these inactive sidecars from the catalogue?

Thank you in advance for your help!!

RE:

I wanted to add another image showing the instances in question but it only allowed to upload one image, so these are the sidecars in question:

Hey @kelematth,

Are configurations still attached to those Sidecar instances?

Does a reboot of the service cause them to disappear?

It seems you are using and older Sidecar version, 1.4, I would suggest the latest release.

Hey!

I have removed the configurations from the Sidecars. Also I removed the services (both winlogbeat and the sidecar) from the endpoint.

It seems like the issue is fixed - I have restarted the graylog server for other reasons-, and now the inactive sidecars are gone.

As for the last recommendation - I was not aware of the latest release. I will let the team know and deploy/update the sidecars. :slight_smile:

Thank you!

1 Like