What are some best practices for knowledge object relationships mapping?

[genesiusj]

Hello,
In MS Access there is a Relationships Manager "tool" to keep track of how the tables, forms, searches, etc. relate to each other in a database app. Is the same available in Splunk? If not, what has been your own Best Practices, besides using a spreadsheet, to keep track of what reports, dashboards, lookup tables, and definitions, etc. are interrelated to each other?
Thanks in advance and God bless,
Genesius

[sloshburch]

Such a thing sounds like a solution to a problem. Would you elaborate on your problem or challenge? It would be interesting to hear what gaps exist and how such a UI could help you.

[DavidHourani]

Hi @genesiusj.

No, there is no relationships manager tool. You can get a listing of all dashboards, reports, and other knowledge objects using REST commands. So it would be pretty easy to build dashboards and get this kind of info.

Relationships becomes a problem easily though because there is no way to link and find where a macro is being used or on which dashboard a report is used.

[genesiusj]

Thanks for the answer, @DavidHourani
Perhaps a nice-to-have Splunk can add to version 8.
God bless,
Genesius

[DavidHourani]

Yeah, could be a great ad on.

It's actually possible to build it if you're indexing your configuration files but it's not easy to make as you'll have to manually put trackers for all newly added knowledge objects.