Wading through Splunk documents concerning things which have deprecated over time is a pain, as no timeline can be found that explains things clearly. Case in point: Hunk.
Hunk used to be a Splunk product. Legacy documentation exists. But a history of Hunk? Tough luck. Here's what I've pieced together so far:
In 2013 (June), Splunk introduced its virtual index technology that enabled the seamless use of the entire Splunk technology stack—including the Splunk Search Processing Language (SPL)—for interactive exploration, analysis, and visualization of data stored anywhere, as if it were stored in a normal Splunk index. Hunk was the first product to exploit this innovation, delivering Splunk’s interactive data exploration, analysis, and visualizations for Hadoop. Splunk quickly opened this API to NoSQL and other data stores (reference required). In 2014, MongoDB partnered with Splunk to offer a MongoDB results provider for Hunk. By late 2016, Hunk’s functionality was completely incorporated into the Splunk Analytics for Hadoop Add-On (Splunkbase 3311) and Splunk Enterprise itself (versions 6.5+).
The question then is what is the status of the Hunk App for MongoDB (Splunkbase 1810), one of only three MongoDB-related entries in Splunkbase? Shouldn't this app be retired? And what of the eternal question of hooking MongoDB databases up as data sources for Splunk? Shouldn't that be handled by a simple add-on or app? The latest (June 2019) post on that question points to a Unity JDBC driver for MongoDB from a vaguely suspicious URL.
... View more