You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: default/data/ui/nav/default.xml
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,8 @@
21
21
</collection>
22
22
<collectionlabel="Performance">
23
23
<ahref="/app/SplunkAdmins/alert?s=%2FservicesNS%2Fnobody%2FSplunkAdmins%2Fsaved%2Fsearches%2FAllSplunkEnterpriseLevel%20-%20Splunk%20Servers%20with%20resource%20starvation">Splunk Servers with resource starvation</a>
24
+
<ahref="/app/SplunkAdmins/alert?s=%2FservicesNS%2Fnobody%2FSplunkAdmins%2Fsaved%2Fsearches%2FAllSplunkEnterpriseLevel%20-%20Splunk%20servers%20with%20resource%20starvation%20v2">Splunk servers with resource starvation v2</a>
25
+
24
26
<ahref="/app/SplunkAdmins/alert?s=%2FservicesNS%2Fnobody%2FSplunkAdmins%2Fsaved%2Fsearches%2FAllSplunkLevel%20-%20Time%20skew%20on%20Splunk%20Servers">Time skew on Splunk Servers</a>
Copy file name to clipboardExpand all lines: default/savedsearches.conf
+30-2Lines changed: 30 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -3297,7 +3297,7 @@ alert.suppress = 0
3297
3297
alert.track = 1
3298
3298
counttype = number of events
3299
3299
cron_schedule = 13 */2 * * *
3300
-
description = Chance the alert requires action? Moderate. Detect when a Splunk enterprise host is reporting that it is seeing excessive response times while running operations
3300
+
description = Chance the alert requires action? Moderate. Detect when a Splunk enterprise host is reporting that it is seeing excessive response times while running operations. A simpler alternative to this alert is "AllSplunkEnterpriseLevel - Splunk servers with resource starvation v2"
search = ```Attempt to find entries in the splunkd logs that indiciate that Splunk is resource constrained and requires more CPU or similar```\
3314
-
index=_internal `indexerhosts` sourcetype=splunkd `splunkadmins_splunkd_source` "Might indicate hardware or splunk limitations" OR "took longer than" ```This is useful for reporting but not so useful for alerting... OR "WARN PeriodicReapingTimeout"``` NOT "Might indicate slow ldap server." ```Add in OR (WARN ConfMetrics) ?)``` \
3314
+
index=_internal `splunkenterprisehosts` sourcetype=splunkd `splunkadmins_splunkd_source` "Might indicate hardware or splunk limitations" OR "took longer than" ```This is useful for reporting but not so useful for alerting... OR "WARN PeriodicReapingTimeout"``` NOT "Might indicate slow ldap server." ```Add in OR (WARN ConfMetrics) ?)``` \
[AllSplunkEnterpriseLevel - Splunk servers with resource starvation v2]
8894
+
alert.suppress = 0
8895
+
alert.track = 1
8896
+
alert.digest_mode = 1
8897
+
alert.severity = 2
8898
+
counttype = number of events
8899
+
cron_schedule = 51 * * * *
8900
+
description = Chance the alert requires action? Moderate. The goal is to find splunk enterprise instances that are showing signs of a performance issue so action can be taken. A more thorough version of this alert exists as "AllSplunkEnterpriseLevel - Splunk Servers with resource starvation"
8901
+
dispatch.earliest_time = -1h@h
8902
+
dispatch.latest_time = now
8903
+
display.general.type = statistics
8904
+
display.page.search.tab = statistics
8905
+
display.visualizations.charting.chart = area
8906
+
enableSched = 1
8907
+
quantity = 0
8908
+
relation = greater than
8909
+
request.ui_dispatch_app = SplunkAdmins
8910
+
request.ui_dispatch_view = search
8911
+
search = index=_internal sourcetype=splunkd `splunkadmins_splunkd_source` `splunkenterprisehosts` "Either time adjusted forwards by" OR "event loop was descheduled" ``` this is an early indicator but a little bit noisy OR "CallbackRunnerThread is unusually busy"``` OR "took longer than seems reasonable"\
8912
+
| rex "\((?P<milliseconds>\d+) milliseconds"\
8913
+
| where isnull(milliseconds) OR milliseconds>50000\
0 commit comments