You have two options: Email the original app author, suggest changes and get them to update the app. Post a new version to Splunkbase yourself. Instructions on how to package your app for Splunkbase are here: http://docs.splunk.com/Documentation/Splunk/5.0/AdvancedDev/PackageApp ... View more

There's a lot of core javascript objects in the Splunk UI that provide functionality. Once you know how it works it's not that hard to use, but that's the trick. These objects are not documented beyond the comments in the code, and we havent invested any time in making examples for external development. In a nutshell Gerald is right- it could be a pretty frustrating experience to try and do anything real right now. But if anyone out there wants to play around with things, you can read some of the source code. For fun you can run a search in the main search UI, and then use firebug's JS console to run things like: header = Splunk.Globals.ModuleLoader.getModuleInstanceById("ResultsHeader_2_9_2"); search = header.getContext().get("search"); ("ResultsHeader_2_9_2" is just the id of one of the modules in the flashtimeline view) Once you have that search object you can get the working urls to access events, results, timeline, summaries. And if you're familiar with good old jquery you would just hit those URL's to get the actual data . search.getUrl("results") search.getUrl("timeline") as for newing up a new Search object and dispatching it and binding event handlers to do something custom, in a perfect world this would be easy. In the real world the first two are super easy but the last one would be annoyingly difficult to do from outside the framework so I'll spare you. ... View more