In the first post about Splunk Cloud Gateway I talked about not being able to use Saved Searches with the Splunk Cloud Gateway. I worked with Splunk and got the official response back about the issue.
So you discovered a bug! I will have a fix for this before the next release of the Cloud gateway app. The issue is with the name of the saved search. We are not url encoding the ref string when we should be which is causing the parser to fail. If you want to work around this issue use a name for the saved search that doesn’t have any spaces.
After working with Splunk, I can confirm that this works. Using camel case (CamelCaseWorks) is a great way to accomplish this without spaces.
User Group Meeting:
Thank you to everyone that came out to our meeting. We had a great time learning about Splunk for AWS. We also had a great discussion afterwards with many people sharing their experiences to help other members of the group.
The WebEx recording of Splunk for AWS is at:
PowerPoint (in PDF form) from the WebEx:
Splunk AWS Presentation
The marketing video for Splunk for AWS – Gain End-to-End AWS Visibility:
From the data collect in the web survey, we will continue to have our meeting over lunch or after work. During these meetings we will focus on technical solutions. I will work to find ways for the meeting to be more interactive with more troubleshooting type of meetings.
- Problems & Solutions; or a session to work through issues faced.
- less sales, more tech details and app usage cases