2.0.0

New release

• App now ships with UBA validation data models (non-accelerated) to extend CIM validation with specific UBA product needs. Thank you @annettefo!!
• Added a filter select a "product" type to validate against, ie Core, ES and UBA.
• Support for district field validation regex per datamodel. This allows for different rules to apply to different datamodel schemas
• CIM Dictionary was reworked to pull information from datamodel schema, instead of relying on a static lookup that needed constant upkeep or version assumption.
• Clarified instructions on differences between _raw and generating search type. The generating search type, formally called datamodel is for use with commands such as | datamodel, | from, | inputlookup, or even | makeresults. This change will help to unlock new validation use-cases, no-matter where the data is located!
• Recommended fields are now pulled from datamodel schema definition OR the recommended field lookup, allowing for additional flexibility for custom schemas.
• Fixed a bug where fields containing _host might be inadvertently filtered out from the Vladiator UI, for example dest_host, src_host, etc.

What's Changed

• Uba support by @hire-vladimir in #35

Full Changelog: 1.8.2...2.0.0

1.8.2

Going forward, the app will also be hosted on Splunkbase. This will make it easier to install and update the app going forward.

The release addresses items related to the Splunkbase conversion and corrects the JQuery issues to ensure app passes app-inspect.

1.8.0 - Splunk 8.x and Python 3 support

In this release:

• Splunk 8.x support
• Python 3 support
• Splunk Cloud self install support
• App Inspect validation fixes

Big thanks to @lowell80 for python 3 support changes