About vgenovese

vgenovese · ‎10-01-2014

The following document contains Migration Issues from Splunk Enterprise version 5.x to 6 http://docs.splunk.com/Documentation/Splunk/6.1.4/AdvancedDev/Migration A brief summary of changes: application.css and application.js apply only to advanced XML apps. Use dashboard.css and dashboard.js for simple XML apps. View states are not supported in simple XML apps. JavaScript is no longer available in nav menus. App Bar styling is restricted to only color and logo. Search page restyling is no longer supported. I am not sure if you can hide the Create New Dashboard in version 6.1 The UseCss page you referred to was overlooked in the docs during the update for these migration issues. I plan to update that document soon. Apologies for the confusion. From the other VG.

vgenovese · ‎07-29-2014

is for using a search to populate choices for a dropdown or radio inputs. For a text input, you can set the value with default, but I'm not sure how to set the value of default dynamically. I will research and respond.

vgenovese · ‎06-10-2013

Actually, the app should have an extension of .spl. I just updated the file that is downloaded so it will have the proper extension. The downloaded file now is named: spl_dashboard_examples.spl This should fix the problem.

vgenovese · ‎02-21-2013

I updated the example in the Embed Splunk dashboard elements... documentation to better describe what Splunk chrome is (modules for displaying default header information on dashboards). Also, the sample code now shows what to strip out. if you download and install the latest Dashboard Examples app, you can find many working examples of simple XML and advanced XML, including an example illustrating IFrames.

vgenovese · ‎09-19-2012

This type of question is environment specific. You should file a case with Splunk support on this. However, you could also check Troubleshooting Monitor Inputs on the Community Wiki.

vgenovese · ‎09-07-2012

Access to the REST endpoints is covered by the capabilities for a role. By default, an admin user role has the capabilities to access all of the public REST API. By default, a user role has access based on the capabilities for that role. This includes access to searches, listing inputs, or getting information from the services/properties endpoint. If you want a non-admin user to have additional access, you need to create a role for the user and then add the specific capabilities you want the user to have access to.

vgenovese · ‎09-06-2012

However, a regular user can access their saved searches, but cannot, for example, enumerate or modify inputs. The docs do not cover this use case, so I will be updating them to better answer this question.

vgenovese · ‎09-06-2012

Any admin user can access the REST API. Refer to the REST API Reference manual for details: http://docs.splunk.com/Documentation/Splunk/latest/RESTAPI/RESTcontents Be sure to read the section "Splunk REST API basics": http://docs.splunk.com/Documentation/Splunk/latest/RESTAPI/RESTusing

Posts	8
Solutions	1
Karma Given	0
Karma Received	11
Member Since	‎05-11-2011

Online Status	Offline
Date Last Visited	‎06-05-2020 02:02 AM

Re: To what extent we can customize app if applica...

Re: setting default with seed not working for text...

Re: download file for Dashboard examples not worki...

Re: how to actually embed a view in an IFRAME?

Re: Splunk stops receiving the data from clients

Re: enabling rest api access

Re: enabling rest api access

Re: enabling rest api access