Are you a member of the Splunk Community?
- Find Answers
- :
- Using Splunk
- :
- Splunk Search
- :
- Re: loadjob command has issues with colons in my s...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've got a saved search name with colons, like this:
savedsearch_name="Mysearch: has a colon"
The loadjob command doesn't seem to like it and I can't figure out how to make it work other than to rename my search to something without spaces:
" | loadjob "admin:search:Mysearch:
has a colon"
Splunk (5.0.3) reports:
"Error in 'loadjob' command: Option
'savedsearch_name=admin:search:Mysearch:
has a colon' is invalid.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, the loadjob command has an issue with colons. Not sure about any other characters. It would be nice to have this documented so I can name my searches in a manner that they can be used with the loadjob command.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, the loadjob command has an issue with colons. Not sure about any other characters. It would be nice to have this documented so I can name my searches in a manner that they can be used with the loadjob command.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
filed a bug with Splunk.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Agreeing with @somesoni2, spaces should not be a problem in loadjob. Try it without the colon. I use dashes in my saved searches .
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I believe renaming is the only options here. It seems loadjob doesn't support object name containing colon or semicolon. Spaces works fine.
Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain
Splunk Lantern’s Guide to The Most Popular .conf25 Sessions
Unlock What’s Next: The Splunk Cloud Platform at .conf25
