ISW - Troubleshooting Box

[grotlue]

• Have a generic copy to place in here where none is specified for input type. We’d need separate generic copy forthe listener, and pull, input types. Where copy is specified for an input type, this would take precedence and show instead of generic cooy.
• For listener inputs, it would be helpful to provide a copy-pastable command the user can enter into the terminal, either on the graylog node or on a remote server, to test connectivity to the input.
• could put this on the UI under the top-left box containing input details.
• the command should be provided with the cluster’s http_publish_uri and the port of the input included.
• command will likely differ per input type.
• Engineering will be provided with a spreadsheet of such command/input combinations.

Copy

“Use the command below to test server connectivity to this input.
Run it on the local Graylog node(s) to confirm the Input is working.
Run it on the remote server(s) hosting the log data to confirm network connectivity to Graylog.”

• For pull inputs, we can provide input-specific troubleshooting copy. For example, the Azure 365 Input simply doesn’t work unless conditions are met (“You need to have Azure AD open_in_new, Office 365 open_in_new subscriptions and have turned on unified logging.”)

• Engineering will be provided with a spreadsheet of such command/input combinations.