Dashboards & Visualizations

Dynamic Hyperlinks between Pre-Production and Production

El_Franco
Explorer

We have a pre-production environment which is totally separate to our production environment. A number of our dashboards utilise hyperlinks back into source systems to view complete records, and part of the urls are different due to IP addresses on the two environemnts. What I would like to do is be able to set a global setting so that we can utilise the same dashboards without having to recode the link when we migrate from pre-produciton to production. I have tried to use a marco but as these are limited to search it did not effect the link target, is there any other way that we can do this without having to put in steps in migration to ammend the URLs?

Thanks,
Steven

Labels (1)
0 Karma

PickleRick
SplunkTrust
SplunkTrust

You could try using tokens as parts of URLs. If all else fails, you could of course try to write custom JS (if it's a SimpleXML dashboard; won't work for Dashboard Studio dashboards AFAIR) but it's not a pretty solution.

0 Karma

El_Franco
Explorer

I have added the following to a dashboard to try and set the variable when it loads:

<init>
<condition match="$env:instance_type$ == cloud">
    <set token="URL">Chips</set>
</condition>
<condition>
    <set token="URL">Fish</set>
</condition>
</init>

While the $env:instance_type$ works to bring back the details of the environment when I map it directly in an HTML block it does not seem to want to evaluate in the initiate tags... I do not really want to push this into the parameters on the dashboard as this will confuse users and end up with mistakes happening - is there anywhere else I can set this seamlessly as the dashboard loads?

0 Karma

El_Franco
Explorer

Thanks - tokens look promising enough... i can check if it is Cloud and if so set the token to one value, if not as another. 

0 Karma

eriegner
Splunk Employee
Splunk Employee

When I have seen something similar with others, we ended up leveraging cname records within DNS to set aliases - similar to a macro that you would only have to change once at the source. 

Do you think that would be a viable solution within your environment? 

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...