Using different indexes in splunk app for jenkins

[ivohechmann]

Hi all;

Regarding the Splunk App for Jenkins

We have multiple jenkins instances in our environment; Each project is in charge of its own jenkins. As there are ways to prevent sensible data to be logged by jenkins, the risk that something that shouldn't be viewed by everyone gets logged by jenkins is considered high. 

my first approach was to modify the splunk app, one instance of the app per jenkins/project, but until now the result is useless.. before I dig deeper: is there another way to "separate" the data or the view on the data in the app?

Thank you very much for any input...

ivo

[PickleRick]

The first thing to do if you want to limit access to data would be to separate the events into different indexes. Then you'll be able to assign different permissions for each of those indexes.

Depending on how the app is written (I haven't seen it) it might require additional configuration but just as well it might be all it requires.

[ivohechmann]

Yes indeed. The app references 3 indexes which can be extended by macros:

jenkins_statistics_index
jenkins_console_index
jenkins_index

but as long as the index jenkins_statistics is directly referenced in 

• appserver/static/pages/audit.js
• appserver/static/pages/build.js
• appserver/static/pages/health.js
• appserver/static/pages/node.js

the app does not work as designed...

Creating a splunk support case for this, hope for support for unsupported app 🙂

Thank you for your hints, 

ivo

[PickleRick]

As you already noticed - this is not a Splunk supported app so there is a very very remote probability that anyone looks into it. This is mostly on a "as-is" basis so short of manually fiddling with the app yourself your choices are fairly limited.