Hey there community and welcome to the 75th installment of Smart AnSwerS.
The “Where Will Your Karma Take You” contest officially ended this past Monday, and the winners were announced in a Splunk blog post by piebob earlier this week. BIG congratulations to sundareshr, skoelpin, and jkat54 for accruing the most karma points during the competition period, earning them each a free pass to .conf2016! If any of these guys have helped you solve your issues on Splunk Answers, be sure to thank them for being such awesome community contributors if you happen to cross paths.
Check out this week’s featured Splunk Answers posts:
How to encode a URL for a Hipchat notification alert action if there is no urlencode() function?
floriancoulmier wanted to have a link prefilled with elements from the alert to display on a dashboard, but needed the URL to be encoded to handle special characters so the link could be opened by a browser. jkat54 created a custom urlencode command for the job, sharing the Python code he mustered up and how to configure commands.conf to make it ready for use.
How to set a default timezone for an entire multisite Splunk deployment?
wweiland was looking for a way to use a default timezone for all users in a multisite environment, but didn’t know what setting needed to be configured and on what Splunk instances. lguinn explains that the two main locations for timezone are during the data ingestion process and at search time. She notes the configuration for data ingestion must be done on forwarders and indexers with props.conf. For search time, however, the timezone has to be explicitly set for each role or defined in user-prefs.conf on the search heads.
Why am I getting error “’newline’ is an invalid keyword argument” using the CLI to run my Python script that writes a CSV file?
jenniferleenyc created a Python script in $SPLUNK_HOME/bin, but was getting an error every time she tried to run it in the command line. Luckily, richgalloway and Masa came in to help her understand how scripted and modular inputs work in Splunk. They provided examples of proper syntax to run them via CLI and supporting Splunk documentation for further education.
Thanks for reading!
Missed out on the first seventy-four Smart AnSwerS blog posts? Check ‘em out here!