search

Graylog2 / collector-sidecar

Manage log collectors through Graylog
https://www.graylog.org/
Other
268 stars 56 forks source link

Please document silent install flags for Windows #387

Open JulioQc opened 4 years ago

JulioQc commented 4 years ago

Everything is in the title. In current documentation I can only see a single example for Windows...

Or in silent mode with: $ graylog_sidecar_installer_1.0.0-1.exe /S -SERVERURL=http://10.0.2.2:9000/api -APITOKEN=yourapitoken

Flags seem to be demanded in other "issues" I can see here but no proper documentation doesn't help to know which work and which don't. I can reverse engineer it using some win32 tools but documentation would spare me this trouble.

Overall, this would greatly help to have it documented so sysadmins can have the collector push silently.

Thank you!

mariussturm commented 4 years ago

What flag do you mean is missing? The silent flag is here: http://docs.graylog.org/en/latest/pages/sidecar.html#windows

JulioQc commented 4 years ago

What flag do you mean is missing? The silent flag is here: http://docs.graylog.org/en/latest/pages/sidecar.html#windows

Silent is there, found SERVERURL in new doc (link provided), found there's also a TAGS flag in 2.5 doc and I was hoping or a flag for the node_id (which could be NODEID) which would be nice. Flag for other settings of the .yml would be a nice plus as well.

edit: from testing, the assumed NODEID flag worked!

mpfz0r commented 4 years ago

edit: from testing, the assumed NODEID flag worked!

That can't be right. The only supported flags are: https://github.com/Graylog2/collector-sidecar/blob/master/dist/recipe.nsi#L181-L186

mpfz0r commented 4 years ago

What would be useful is a /H help switch in the installer that shows all options

JulioQc commented 4 years ago

edit: from testing, the assumed NODEID flag worked!

That can't be right. The only supported flags are: https://github.com/Graylog2/collector-sidecar/blob/master/dist/recipe.nsi#L181-L186

Scripted deployment over my infra using that flag so you can trust me when I say it works. But I understand your confusion from the code you quote, so am I!

mpfz0r commented 4 years ago

Could that be because the node-id was already persisted in the node-id file from a previous install?

JulioQc commented 4 years ago

Mixed deployment, some upgrade, some new installations, so I would say possibly not the explanation :(