Customization options and caching
Options for customization
There are several styling, behavior, and text customization options available for different components of the Splunk platform.
| To learn about | See |
|---|---|
| Customizing the login page | Customize the login page |
|
Using CSS or JavaScript files to
|
Customize dashboard styling and behavior |
| Configuring UI internationalization | UI internationalization |
| Adding HTML or images to a dashboard | The <html> Simple XML element reference in Dashboards and Visualizations |
| Customizing integrated PDFs | Additional configuration options for integrated PDF generation in the Reporting Manual |
Clear client and server assets caches after customization
Static assets for apps are cached on the client and server side. If you update an item in the /appserver/static directory, you can see changes by clearing both the client and server caches. Clear the browser cache to update the client side.
To clear the server cache, use one of the following options:
- Clear Splunk Enterprise's server-side Splunk Web resources using:
_bump:http://<host:mport>/<locale_string>/_bump
- Clear all splunkd registered EAI handlers that support reload using:
debug/refresh:http://<host:mport>/debug/refresh
- Restart
splunkd. For more information, see Start and stop Splunk Enterprise in the Admin Manual.
- Set
cacheEntriesLimit=0inweb.conf. This setting is recommended only for development use cases and not for production. For more information, see theweb.confspec file in the Admin Manual.
Last modified on 06 December, 2022
| Example script that polls a database | Customize the login page |
This documentation applies to the following versions of Splunk Cloud Platform™: 8.2.2203, 8.2.2112, 8.2.2201, 8.2.2202, 9.0.2205, 9.0.2208, 9.0.2209, 9.0.2303, 9.0.2305, 9.1.2308, 9.1.2312, 9.2.2403, 9.2.2406 (latest FedRAMP release), 9.3.2408
Download manual
Feedback submitted, thanks!