Are you a member of the Splunk Community?
- Find Answers
- :
- Splunk Administration
- :
- Monitoring Splunk
- :
- Re: performance of form
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
hi,
i have views/forms that consists of a dropdown box and several other panels(single value panels, tables, charts) derived from this dropdow box. the time taken by the form to load is really long. i have another issue like, some times, only some of the panels will load and others will not(i have already posted this question). i have posted my code here
How can i improve the performance? Is this issue because of the transaction commands used in the form ?
please help
thank you
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The best way to look into what is causing long load times is to use the Jobs link in the top right. Here you can inspect your searches, even ones that are embedded into dashboards, and look at the overall times they take to execute. It also provides a breakdown of the different parts that take the longest - this way you can identify if its transaction that is taking the time.
Also, another major cause of slowdown like you describe is if a timerange isn't being appended to your search correctly, this can result in searches in your jobs window as showing as earliest=1970 sometime 😉 This can take a while to run..
Search Job Inspector;
http://docs.splunk.com/Documentation/Splunk/4.3/SearchReference/SearchJobInspector
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The best way to look into what is causing long load times is to use the Jobs link in the top right. Here you can inspect your searches, even ones that are embedded into dashboards, and look at the overall times they take to execute. It also provides a breakdown of the different parts that take the longest - this way you can identify if its transaction that is taking the time.
Also, another major cause of slowdown like you describe is if a timerange isn't being appended to your search correctly, this can result in searches in your jobs window as showing as earliest=1970 sometime 😉 This can take a while to run..
Search Job Inspector;
http://docs.splunk.com/Documentation/Splunk/4.3/SearchReference/SearchJobInspector
Take Action Automatically on Splunk Alerts with Red Hat Ansible Automation Platform
Calling All Security Pros: Ready to Race Through Boston?
Beyond Detection: How Splunk and Cisco Integrated Security Platforms Transform ...
