As a Forward Deployed Software Engineer, I've had several interesting use cases presented to me. But one of the more recent challenging ones was the implementation of the Breadcrumb Feature with Splunk dashboards. In this post, I will be demonstrating one of the many implementations of this feature and the conditions under which it could be used.
To start off with a basic naming convention, we have :
parent: The dashboard where we start off.
child: The dashboard that populates when we drilldown on the panels of the parent.
second_child: The dashboard that populates when we drilldown from a hyperlink on the child.
Points to keep in mind:
2. When navigating back to the parent/child pages from the breadcrumb, the initial search state of these dashboards will be lost. The dynamic implementation that retains the state of the current page along with tokens used on the dashboard, will require use of user sessions, cookies and stack model. This would require further research to fully develop, more than our typical 1-week turn time (thus leaving the door open for further PS engagements later on).
3. A link to the respective app is also provided at the start of the breadcrumb, which would lead the user to the dashboards page of the app.
The code on the parent dashboard would look like below:
The code on the child dashboard would look like this.
The code on the second child dashboard would look like this.
Finally, our output would look like so in the child and second child dashboards respectively.
Happy Splunking !