


In Splunk 6.5 and earlier versions, to view the complete search commands executed by a macro, you either navigated to Advanced Search > Search Macros or searched for the macro string via job inspector. For comparison, here is a view of the Splunk 6.5 Search Bar, without the syntax highlighting or line numbering.

This would be an invaluable tool when comparing searches or troubleshooting. The line numbering allows you to review commands and adds clarity to functions for the user. Under the ‘Search’ options select Dark Theme for ‘Syntax highlighting’ and set ‘Show line numbers’ to On.Īfter selecting dark-themed highlighting and activating line-numbering, my Splunk search bar now has a black background with line numbering, making it easier to find or edit lines of code. Not only do they add visual appeal by giving the user a theme choice, but they also allow you to write queries on an enhanced search editor. You can activate these features by going to your user account settings. The two features I’ll expand in this section on are line-numbering and syntax-highlighting. Enhanced Search Editor – Line Numbering and Syntax Highlighting In part 2, we will explore new features within the enhanced search editor, such as line-numbering, syntax highlighting and macro expansions.
Splunk advanced search query examples series#
You can explore and get all the queries in the cheat sheet from the GitHub repository.In part 1 of our series into the new features of Splunk Enterprise 6.6, we looked at Splunk Knowledge Object management. This GitHub repo provides access to many frequently used advanced hunting queries across Microsoft Threat Protection capabilities as well as new exciting projects like Jupyter Notebook examples and now the advanced hunting cheat sheet. Microsoft Threat Protection’s advanced hunting community is continuously growing, and we are excited to see that more and more security analysts and threat hunters are actively sharing their queries in the public repository on GitHub.
