How to assign a bug number to a source file with stack trace

[vincenty]

New to Splunk. We want to see if we can search and analyze log files (from source) with stack traces and assign bug number to it (or tag it with bug number created with external bug DB). Not sure if anyone have done this? Or if there's other apps that can do this with Splunk.

Should we apply a "tag" with bug number to the source file?
Is there a way to link with the bug system?
other considerations?

thx in advance

[dart]

I'd do this with an eventtype - craft a search that matches the bug in question and then save it with a name indicating the bug number. It's the most flexible way to do this.

As an additional bonus, you can define a workflow action to link to your bug database, assuming it's web based and you can construct a URL from the bug number. (Or indeed, in a dashboard customize drilldown to go to the bug database)