You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Invalid key in stanza [] in default.meta, line 5: owner = admin.
Why owner is not allowed for all objects? It works just fine on 9.1.x
outputs.conf
Stanza [tcpout-server://idx01.splunk.lab:9997] does not seem to be a valid stanza.
Invalid key in stanza [tcpout-server://idx01.splunk.lab:9997] in outputs.conf, line 30: sslAltNameToCheck = idx01.splunk.lab.
Perfectly working configuration for SSL configuration with SAN verification.
inputs.conf
Invalid key in stanza [monitor://C:\inetpub\logs\LogFiles\W3SVC*\*.log] in inputs.conf, line 6: ignoreOlderThan = 7d.
Invalid key in stanza [script:alertqueue] in restmap.conf, line 14: match = /alertqueue. Invalid key in stanza [script:alertqueue] in restmap.conf, line 20: requireAuthentication = true.
Here is list of my finding for version 0.3.3:
Why owner is not allowed for all objects? It works just fine on 9.1.x
Why? Since documented under:
https://docs.splunk.com/Documentation/Splunk/9.1.5/Admin/Inputsconf#MONITOR:
Why? Since documented under:
https://docs.splunk.com/Documentation/Splunk/9.1.5/Admin/Inputsconf#HTTP_Event_Collector_.28HEC.29_-_Local_stanza_for_each_token
Option used for encrypted version.
Custom config for modular input.
Documented in: https://docs.splunk.com/Documentation/Splunk/9.1.5/Admin/Appconf#.5Binstall.5D
Per endpoint attributes:
https://docs.splunk.com/Documentation/Splunk/9.1.5/Admin/Restmapconf#GLOBAL_SETTINGS
The text was updated successfully, but these errors were encountered: