Reporting

How can I organize reports better for improved visibility and categorization?

JPaule
Explorer

We have hundreds of reports (saved searches) which all show up when you click on the Reports tab. How can you better organize reports so they are easily findable by category, similar to how the filters at the top work for "All", "Yours", and "This App's". Is there any way to add a tagging column to filter by the tag? So, the types of filters for example could be: IIS, Audit, SQL, Windows, ULS, etc. Then when the respective tag is selected only those reports would show up.

Any help would be great, I've done a fair share of Googling and couldn't find anything except creating new dropdowns at the top, but that seems inefficient especially when new reports are created.

0 Karma
1 Solution

rsennett_splunk
Splunk Employee
Splunk Employee

Altering the Report view (tab) would be difficult to maintain through upgrades. What I have seen people do is two fold, and it does take a bit of work to implement.

What you're talking about is socializing the concept of a naming convention... in the form of a prefix or suffix when people name saved searches. You then build your own "Tabs" on the navigation menu:
Change to the app who's menu you would like to alter:
Then select: settings>user interface>Navigation Menus>default

By default you see something that looks like this:

<nav search_view="search" color="#65A637">
  <view name="search" default="true" />
  <view name="datasets" />
  <view name="reports" />
  <view name="alerts" />
  <view name="dashboards" />
</nav>

Insert the following before the closing </nav> tag (replacing "error" with your match txt) :

<nav search_view="search" color="#65A637">
      <view name="search" default="true" />
      <view name="datasets" />
    <!-- Dynamically list all reports with the word "error"-->
        <collection label="Reports (errors)">
            <saved source="all" match="error"/>
        </collection>
<!-- Dynamically list all unclassified reports -->
    <collection label="Others">
        <saved source="unclassified" />
    </collection>
<view name="alerts" />
      <view name="dashboards" />
    </nav>

You'll find further detail here:

http://dev.splunk.com/view/webframework-developapps/SP-CAAAEP9

So while you probably could dig under the hood and alter the Report Tab (which in the end, is just a view) it's better to get folks to use a known key word in their report names... and have it automagically picked up by the dropdown that will appear in the menu. (you can do this with dashboards too)

To affect the existing reports, folks would have to save them again with the new name (best way to get people familiar with the new process and have them WANT to have their stuff listed.) It also makes it easy for you to run reports and see who hasn't changed their stuff so you can see if they still care about it or if it's just noise.

With Splunk... the answer is always "YES!". It just might require more regex than you're prepared for!

View solution in original post

rsennett_splunk
Splunk Employee
Splunk Employee

Altering the Report view (tab) would be difficult to maintain through upgrades. What I have seen people do is two fold, and it does take a bit of work to implement.

What you're talking about is socializing the concept of a naming convention... in the form of a prefix or suffix when people name saved searches. You then build your own "Tabs" on the navigation menu:
Change to the app who's menu you would like to alter:
Then select: settings>user interface>Navigation Menus>default

By default you see something that looks like this:

<nav search_view="search" color="#65A637">
  <view name="search" default="true" />
  <view name="datasets" />
  <view name="reports" />
  <view name="alerts" />
  <view name="dashboards" />
</nav>

Insert the following before the closing </nav> tag (replacing "error" with your match txt) :

<nav search_view="search" color="#65A637">
      <view name="search" default="true" />
      <view name="datasets" />
    <!-- Dynamically list all reports with the word "error"-->
        <collection label="Reports (errors)">
            <saved source="all" match="error"/>
        </collection>
<!-- Dynamically list all unclassified reports -->
    <collection label="Others">
        <saved source="unclassified" />
    </collection>
<view name="alerts" />
      <view name="dashboards" />
    </nav>

You'll find further detail here:

http://dev.splunk.com/view/webframework-developapps/SP-CAAAEP9

So while you probably could dig under the hood and alter the Report Tab (which in the end, is just a view) it's better to get folks to use a known key word in their report names... and have it automagically picked up by the dropdown that will appear in the menu. (you can do this with dashboards too)

To affect the existing reports, folks would have to save them again with the new name (best way to get people familiar with the new process and have them WANT to have their stuff listed.) It also makes it easy for you to run reports and see who hasn't changed their stuff so you can see if they still care about it or if it's just noise.

With Splunk... the answer is always "YES!". It just might require more regex than you're prepared for!

jaredhartman1
Engager

How about a dynamic drop down menu which matches based on a standard naming convention for your reports? When a new report is created it will automatically be added to the menu. e.g.

 <collection label="REPORT_TYPE1">
      <collection label="REPORT_NAME_SQLs">
        <saved source="unclassified" match="SQL" />
      </collection>
         <collection label="REPORT_NAME_2">
        <saved source="unclassified" match="NAME" />
      </collection>
  </collection>
0 Karma
Get Updates on the Splunk Community!

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics GA in US-AWS!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...