williamtrelawny
commented
9 months ago Just received this request from a customer as well. Could consider simply displaying a warning if an user on an unlicensed cluster attempts to configure an enterprise Input, if outright hiding the Input is too complicated from a code perspective.
Currently, an unlicensed user can create and go through all the configuration steps for an enterprise Input, and will only receive an error at the very end telling them there is a license issue. This is especially frustrating for API-based Inputs like the Google Workspace/GCP ones where a user goes through all the trouble of configuring their GCP Project, creating Service Accounts, and configuring their Google Workspace environment for this Input, only to find out at the end that they don't even have the ability to use this Input.
ref: HS-2112667784
What?
While doing research on Graylog inputs, what is offered, and which are licensed or not, I noticed that even if I remove my license from the graylog cluster, all licensed inputs are still visible and theres no indication if an input is licensed or not. Only after you create the input and attempt to start it do you get any indication that the input is licensed.
I understand these inputs may not normally appear as long as the integrations plugins are NOT installed. However there could be cases where this is installed but the cluster is not licensed. It would much more clear if the input is licensed or not (similar to how the list of alert notification types show)
Why?
Currently its quite difficult to understand which inputs are part of Graylog Open Source and which are paid/licensed. It would help the experience to both label which are licensed and not show licensed inputs if no valid license is present.
Your Environment