icon/x Created with Sketch.

Splunk Cookie Policy

We use our own and third-party cookies to provide you with a great online experience. We also use these cookies to improve our products and services, support our marketing campaigns, and advertise to you on our website and other websites. Some cookies may continue to collect information after you have left our website. Learn more (including how to update your settings) here.
Accept Cookie Policy

Accept License Agreements

This app is provided by a third party and your right to use the app is in accordance with the license provided by that third-party licensor. Splunk is not responsible for any third-party apps and does not provide any warranty or support. If you have any questions, complaints or claims with respect to this app, please contact the licensor directly.

Thank You

Downloading Update Notable Command for ES
SHA256 checksum (update-notable-command-for-es_010.tgz) 0a6095a4f9f786f652dd881ce4c385d10305a96786c418c54c075c3d93ad2be4
To install your download
For instructions specific to your download, click the Details tab after closing this window.

Flag As Inappropriate

Update Notable Command for ES

Admins: Please read about Splunk Enterprise 8.0 and the Python 2.7 end-of-life changes and impact on apps and upgradeshere.
Have you ever wanted to be able to change the status/urgency of a notable, assign it to someone or add a comment to it based upon the results of a search? This app provides the `updatenotable` search command that allows you to do just that. Simply pipe notable search results to the command with the event_id field and one or more of the following fields: owner, status, urgency, comment.

This opens up a range of possibilities not previously available because you can now on a notable by notable basis use the analytics in Splunk to change notables. Here's a simple example of what this makes possible:

`notable` | where status==5 AND isnull(comment) AND risk_score>=80 | fields event_id risk_score | eval status=1, comment="Changing status of Closed notable to New because it has a high risk score (" . risk_score . ") but hasn't yet been commented on." | updatenotable

If this was to be made into a scheduled search (preferably without an owner), it could look every few minutes for notables with a risk score 80 or above that don't appear to have been triaged and change their status to 'New'.

Please find documentation and source here: https://github.com/doksu/TA-updatenotable

May this app improve the security of organisations great and small.

Release Notes

Version 0.1.0
Aug. 28, 2020

Initial Release


Subscribe Share

AppInspect Tooling

Splunk AppInspect evaluates Splunk apps against a set of Splunk-defined criteria to assess the validity and security of an app package and components.

Are you a developer?

As a Splunkbase app developer, you will have access to all Splunk development resources and receive a 10GB license to build an app that will help solve use cases for customers all over the world. Splunkbase has 1000+ apps and add-ons from Splunk, our partners and our community. Find an app or add-on for most any data source and user need, or simply create your own with help from our developer portal.

Follow Us:
© 2005-2020 Splunk Inc. All rights reserved.
Splunk®, Splunk>®, Listen to Your Data®, The Engine for Machine Data®, Hunk®, Splunk Cloud™, Splunk Light™, SPL™ and Splunk MINT™ are trademarks and registered trademarks of Splunk Inc. in the United States and other countries. All other brand names, product names, or trademarks belong to their respective owners.