Anton Ebel

This issue has already been fixed with this PR #13188. In addition, the following issues were created for a better user experience: #13251, #13252

The old Windows Filebeat configuration looks like this: ``` # Needed for Graylog fields_under_root: true fields.collector_node_id: ${sidecar.nodeName} fields.gl2_source_collector: ${sidecar.nodeId} output.logstash: hosts: ["192.168.1.1:5044"] path: data: ${sidecar.spoolDir!"C:\\Program Files\\Graylog\\sidecar\\cache\\filebeat"}\data logs: ${sidecar.spoolDir!"C:\\Program Files\\Graylog\\sidecar"}\logs tags:...

These are the - [cats subcats](https://graylogdocumentation.atlassian.net/wiki/spaces/PROD/pages/3494019099/Attack+Surface+Areas+Visibility+Scores#Attack-Surface-Groups) - plus "generic" subcat

todos for backend: - add additionl API endpoint or extend the existing input updateAPI to set an input to "Setup" mode ( The other input states are calculated at runtime....

To detect whether an input is in setup mode, I suggest adding the `SETUP` status to the input `state`. It would then look like this: ``` GET /api/system/inputstates [{ "id":...

Since the requierements say that an input should be created in `setup_mode = true`, for `POST` calls `setup_mode` field is optional and we would be `true` if not specified.

The call [here](https://github.com/Graylog2/graylog2-server/blob/b9536c5365646f74a98cf76ad67a24d6c2cb1894/graylog2-web-interface/src/pages/SidecarsPage.tsx#L31) shouldn't break the page. If the Sidecar user cannot be fetched, we should instead only hide the selected section: