I am currently getting this failure when running my add-on through appinspect:
check_inputs_conf_spec_stanzas_has_python_version_property
My README/inputs.conf.spec
[a...
....spec are explicitly set the python.version to python3. Modular input "example" is defined in README/inputs.conf.spec, python.version should be explicitly set to python3 under each stanza. File: R...
...fter the name of the input in the inputs.conf.spec name stanza (for example, //default in the twitter modinput example)? And how is it used by the app/modinput and Slunk Enterprise once your app has b...
...nput.conf instead inputs.conf) and that they say to modify a .spec file, but how commented statements can solve an issue? Obviously this solution didn't solved my issue. Is there anyone that can hint a...
Did the blacklist/whitelist got replaced by denylist/allowlist in Splunk 9? In some Blogs i read that Splunk 9 replaced blacklist with denylist? Or is blacklist still usable? In the Changelogs ...
Hello Splunkers,
I have a question, would it be possible to assign a specific sourcetype to some logs inside a input stanza, depending on the content of the log itself (based on the key / fields ex...
Invalid key in stanza [workday://user_activity] in /opt/splunk/etc/apps/TA-workday/local/inputs.conf, line 2: include_target (value: 0). [workday://user_activity] include_target = 0 index = w...
...ection of the Microsoft 365 App for Splunk. I checked in Azure and Incident.Read has permissions enabled on the app. The Splunk documentation says that I should go to Add-on > Inputs and click Create N...