Assistance with HTML/CSS/JS Support and Feature Limitations in Splunk Cloud Studio Dashboard

[Sundaravarathan]

Hello Splunk Community,

We are currently transitioning a live dashboard from Splunk Enterprise to Splunk Cloud. The original dashboard was built using HTML, CSS, and JavaScript to monitor three critical KPIs: Success, Response, and Availability.

In our Splunk Enterprise version, we implemented:

A custom alarm beep and red colour flash when any KPI drops below 99%.

Pagination to manage and display data effectively.

However, while recreating this dashboard in Splunk Cloud Studio, we’ve encountered limitations:

1. It seems that Studio doesn’t support custom pagination features.
2. We're unable to add the alarm beep and visual alerts as we did use HTML/CSS/JS in Enterprise.
   3. Federated searches limitation and how we can use for this requirement and how to their license usage
   
   

Could someone please clarify: 

What are the limitations of using HTML, CSS, and JavaScript in Splunk Cloud and Studio dashboards?

Are there any workarounds or supported methods to implement these types of visual and audio alerts in Splunk Cloud?

Any suggestions or examples on how to handle pagination and threshold-based alerts within Studio?

Your insights or best practices would be greatly appreciated.

 Thank you in advance for your support!

[livehybrid]

Hi @Sundaravarathan 

You're correct in that Dashboard Studio does not allow custom CSS/JS as you are currently able to use with Classic XML dashboards, therefore you might be better sticking to your existing setup for your cloud move.

From my experience, Cloud migrations should be exactly that - a migration. If you start making too many changes then this becomes a "transformation" rather than a "migration" and it becomes significantly harder to compare your existing workflows/dashboards/alerts etc to your new Splunk Cloud versions and makes the user-acceptance phase of the migration so much harder.

I would recommend sticking to your existing dashboards until you have migrated to Splunk Cloud, and then when you are ready iterate over to convert existing classic XML dashboards into Dashboard Studio dashboards based on features available etc.

🌟 Did this answer help you? If so, please consider:

• Adding karma to show it was useful
• Marking it as the solution if it resolved your issue
• Commenting if you need any clarification

Your feedback encourages the volunteers in this community to continue contributing

[ITWhisperer]

Studio is still limited in the finer aspects of dashboard control and visualisation. Best practice (in my opinion) at the moment is to stick with Classic Simple XML, especially if you already have a working dashboard on-prem, just copy (the source) to Cloud.