topic Re: scheduler.log _internal index "reason" field bug? in Splunk Enterprise

How d I fix: scheduler.log _internal index "reason" field bug?

splunkadmin — Tue, 30 Aug 2022 13:40:11 GMT

In Splunk Enterprise 9.0.0.1, I scheduled a saved search with an invalid macro name in it. When run, I receive the following error message as I should:

Error in 'SearchParser': The search specifies a macro 'my_macro' that cannot be found. Reasons include: the macro name is misspelled, you do not have "read" permission for the macro, or the macro has not been shared with this application. Click Settings, Advanced search, Search Macros to view macro information.

The search was skipped, the error was logged to scheduler.log, and the log ingested into _internal all as expected. However, the reason field gets cut off because of the quotation marks in the error message. It thinks the field value ends at "have" when it should end at "information."

I believe this is a minor defect. Is there any way to submit a bug report? I tried creating a case but received a message saying I don't have a Support Contract or entitlement to do so. Can anyone point me in the right direction?

Thanks!

Edit: Created Splunk Ideas post: https://ideas.splunk.com/ideas/EID-I-1586

Re: scheduler.log _internal index "reason" field bug?

richgalloway — Thu, 25 Aug 2022 20:02:16 GMT

You may be right about that. Go to https://ideas.splunk.com to report it.

Re: scheduler.log _internal index "reason" field bug?

splunkadmin — Thu, 25 Aug 2022 21:17:09 GMT

I'll post there, but is there really no better way for Splunk to accept user-found bugs than this? It feels like a bug report would get lost in a sea of feature requests there

Re: scheduler.log _internal index "reason" field bug?

richgalloway — Fri, 26 Aug 2022 00:18:26 GMT

"This is the way." We used to submit P4 support tickets, but now Splunk says to go to Ideas.