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.
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.
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.
filed a bug with Splunk.
Agreeing with @somesoni2, spaces should not be a problem in loadjob. Try it without the colon. I use dashes in my saved searches .
I believe renaming is the only options here. It seems loadjob doesn't support object name containing colon or semicolon. Spaces works fine.