What's the latest from Splunk Developer? Check out the Spring Update!

[tchavez_splunk]

We posted a blog recently with Spring updates from Splunk Developer and wanted to share it here, too where we can discuss! Already working on the Summer update so let us know if there's anything you'd like to see in that upcoming newsletter.

https://www.splunk.com/en_us/blog/tips-and-tricks/splunk-developer-spring-2020-update.html

Is it the middle of Spring already? (And Fall, for our Southern Hemisphere readers!) A lot has happened at Splunk since our last developer updates at .conf19. In case you missed any of the great developer sessions there, grab some time to watch what you missed! 

Python 2 to Python 3 Migration

With the new year came the EOL of Python 2, and while runtimes for both Python 2 and Python 3 were included in Splunk Enterprise 8.0 and Splunk Cloud 8.0, the July update of Splunk Cloud 8.0.x will be the last to include the Python 2 runtime, and the next major or minor release of Splunk Enterprise 8.0 after July 1 will no longer include the Python 2 runtime. Read the “Migrating your Splunkbase App and Users to Python 3 and Splunk 8.0” blog for more information and the Python 3 migration documentation.

Splunkbase Updates

Beginning in July, the Splunkbase App Archive Policy will be updated to align with the Splunk Support Policy and the currently supported versions of Splunk Enterprise. Apps in Splunkbase that have not been updated within two years, or are not compatible with a currently-supported version of Splunk Enterprise, will be archived.

App authors will still receive pre-archive notification one month in advance. To prevent an app from being archived, just submit an update that is compatible with a supported release of Splunk Enterprise.

Also starting in June, Product Compatibility options for Splunk Enterprise will no longer have Splunk Enterprise 7.0 and older release options to select when submitting an app, updating an app, or searching for an app.

SimData 1.1

Are you testing your application with data? Instead of using a sample set of data that is repetitive and unrealistic, SimData generates a rich and robust set of events from real-world situations by mimicking how multiple systems work together and affect the performance of your system. Download SimData v1.1.0 here and try the examples here.

Visual Studio Code Splunk Extension

Writing an extension to Splunk in Python? You could be using Microsoft Visual Studio Code to speed your development. Visual Studio Code is a free, cross-platform, highly rated code editor from Microsoft that provides a rich development environment including debugging capabilities such as breakpoints, stepping into code, variable inspection, and displaying the call stack. Visual Studio Code is extensible, and the Splunk integration takes advantage of the extensibility to provide intelligence about Splunk .conf files and interact with Splunk via the editor. Read more here.

More New Releases and Updates

• Did you see the release of Java Logging Libraries v1.8? This update includes feature improvements and bug fixes to address memory leaks, decrease memory usage, and stop data loss!
• Splunk Enterprise Python SDK v1.6.13 added Bearer token support using Splunk Token in Splunk Enterprise v7.3 in v1.6.12 and a bug fix in v1.6.13.
• Want to extend the Splunk Enterprise REST API with custom endpoints? The docs were recently updated so you can add functionality to your app that Splunk Enterprise doesn’t support natively or to manage your app’s custom configuration files.
• The updated AppInspect CLI and API v2.1.0 add a lot of great new checks for Python 3 and testing against Splunk 8.0.2 for improved measurement of readiness with Splunk Cloud. 

Splunk Supported Versions Notification

Keep up to date with the latest supported versions of Splunk products on the Splunk Support Policy page. Here you’ll find the dates when releases of Splunk products are no longer supported. End of support for Splunk Enterprise 7.1 is extended to October 31, 2020 (unless otherwise noted on the Support Policy page).