Alerts For Splunk Admins
Overview
Details
The 2017 conf presentation is linked from the detailed notes, the overall idea behind this application is to provide a variety of alerts that detect issues or potential issues within the splunk log files and then advise via an alert that this has occurred.
This application was built as there were a variety of messages in the Splunk console and logs in Splunk that if acted upon could have prevented an issue within the environment.
In addition to the alerts there are a few dashboards that relate to troubleshooting indexer/heavy forwarder performance issues.
Many of the alerts are informational and the description and comments inside the alert explain which alerts are likely to generate the most noise.
All alerts are disabled by default so you can choose which alerts may be appropriate for your environment.
Feedback is welcome!
The conf 2017 presentation How did you get so big? Tips and tricks for growing your Splunk instance from 50GB/day to 1TB/day
The conf 2017 presentation recording is available here, and PDF only here. The powerpoint presentation is available here
Introduction
This application accompanies the Splunk conf 2017 presentation "How did you get so big? Tips and tricks for growing your Splunk installation from 50GB/day to 1TB/day"
The overall idea behind this application is to provide a variety of alerts that detect issues or potential issues within the splunk log files and then advise via an alert that this has occurred
This application was built as there were a variety of messages in the Splunk console and logs in Splunk that if acted upon could have prevented an issue within the environment
There are many potential alerts that might cause an issue so this application has all alerts disabled by default, post-installation once the required macros are configured you can enable the alerts you wish to use and add the required actions
There are also a few dashboards for investigating indexer performance, heavy forwarder queue usage and data model acceleration issues
Please note that the all alerts & dashboards were tested on Linux-based Splunk infrastructure, with AIX, Linux and Windows forwarders
If you are running your Splunk enterprise installation on Windows or have customised your installation directory you will need to customise some of the macros such as splunkadmins_splunkd_source to point to the correct splunkd log file location
Macros - required configuration
The various saved searches and dashboards use macros within their searches, you will need to update the macros to ensure the searches/dashboards work as expected
To check the contents of the macros in Splunk 7 or newer, use CTRL-SHFT-E within the search window
The macros are listed below, many expect a host=A OR host=B item to assist in narrowing down a search while others expect only a single value...note that for splunk_server values they are always lower-case and case-sensitive!
indexerhosts - a host=... list of your indexers (for example host=indexer1 OR host=indexer2)
heavyforwarderhosts - a host=... list of your heavy forwarders (for example host=heavyforwarder1 OR host=heavyforwarder2)
searchheadhosts - a host=... list of your search head(s) (for example host=searchhead1 OR host=searchhead2)
localsearchheadhosts - a host=... list of your search head(s) within the cluster that these alerts are running on
splunkenterprisehosts - a host=... list of any Splunk enterprise instance (for example host=indexer1 OR host=searchhead1 OR ...)
deploymentserverhosts - a host=... list of deployment server(s) (for example host=splunkdeploymentserver)
licensemasterhost - a host=... entry for the license master server (for example host=splunklicensemaster)
searchheadsplunkservers - a splunk_server=... list of any Splunk search head hosts (for example splunk_server=searchhead*)
splunkindexerhostsvalue - a splunk_server=... list of any Splunk indexer hosts (for example splunk_server=indexer*)
splunkadmins_splunkd_source - this defaults to source=*splunkd.log, for a slight improvement in performance you can make this a specific file such as /opt/splunk/var/log/splunk/splunkd.log
splunkadmins_splunkuf_source - this defaults to source=*splunkd.log, you may wish to narrow down this location if your splunkd logs on universal forwarders have consistent installation directories
splunkadmins_mongo_source - this defaults to source=*mongod.log, for a slight improvement in performance you can make this a specific file such as /opt/splunk/var/log/splunk/mongod.log
splunkadmins_clustermaster_oshost - a host=... entry for the cluster master server (for example host=splunkclustermaster)
The macros are used in various alerts which you can optionally enable, the alerts will raise a triggered alert only as emails are not allowed for Splunk app certification purposes
The macros are also used in the dashboards for this application
The vast majority of the alerts also have a macro(s) which you can customise to tweak the search results, for example the macro splunkadmins_weekly_truncated allows the alert, IndexerLevel - Weekly Truncated Logs Report, to be customised without changing the alert itself. This will make upgrading to a new version of this app more straightforward
I have attempted to provide an appropriate macro in any alert where I deemed it appropriate, feedback is welcome for any alert that you believe should have a macro or requires further improvement
Installation
The application is designed to work on a search head or search head cluster instance, installation on the indexing tier is not required
There are a few searches that use REST API calls which are specific to the search head cluster they run on. These alerts will have to be placed on each search head or search head cluster, alternatively any server with the required search peers will also work, the relevant alerts are:
- SearchHeadLevel - Accelerated DataModels with All Time Searching Enabled
- SearchHeadLevel - Realtime Scheduled Searches are in use
- SearchHeadLevel - Realtime Search Queries in dashboards
- SearchHeadLevel - Scheduled Searches without a configured earliest and latest time
- SearchHeadLevel - Scheduled searches not specifying an index
- SearchHeadLevel - Scheduled searches not specifying an index macro version
- SearchHeadLevel - Scheduled Searches Configured with incorrect sharing
- SearchHeadLevel - Saved Searches with privileged owners and excessive write perms
- SearchHeadLevel - User - Dashboards searching all indexes
- SearchHeadLevel - User - Dashboards searching all indexes macro version
- SearchHeadLevel - Users exceeding the disk quota (recent jobs list uses a REST call so you may need to adjust the search), the SearchHeadLevel - Users exceeding the disk quota introspection is a non-search head specific alternative
The following reports also are specific to a search head or search head cluster:
- SearchHeadLevel - Alerts that have not fired an action in X days
- SearchHeadLevel - Data Model Acceleration Completion Status
- SearchHeadLevel - Macro report
- What Access Do I Have?
The following dashboards are search head or search head cluster specific:
- Data Model Rebuild Monitor
- Data Model Status
The following reports / alert must either run on the cluster master or a server where the cluster master is a peer:
- ClusterMasterLevel - Per index status
- ClusterMasterLevel - Primary bucket count per peer
Using the application
Once the application is installed, all alerts are disabled by default and you can enable those you require or want to test in your local environment.
If you choose not to customise the macros then many searches will search for all hosts, which will make the alerts and dashboards inaccurate!
Which alerts should be enabled?
The alerts are all useful for detecting a variety of different scenarios which may or may not be applicable within your Splunk environment
The description field has an (extremely) simple way of determining if an alert will require action, there are three levels:
- Low - the alert is informational and likely relates to a potential issue, these alerts may produce false alarms
- Moderate - the alert is a warning, most likely further action will need to be taken, a moderate chance of false alarms
- High - the alert is likely relating to something that requires action and there is a very low chance that this will create false alarms
I do not have a nice way to auto-enable various alerts excluding editing the local/savedsearches.conf or via the GUI, any contribution of a setup file would be welcome here!
How is this application used?
In the current environment the vast majority of the alerts are enabled to detect issues, they raise automated tickets or email depending on the urgency of the specific alert.
There are a few environment characteristics that may require changes to the way the app is used, and feedback is welcome if there is a nicer way to structure the alerts/application
The overall assumption is that the admin(s) are not carefully watching the splunkd logs or the messages in the console of the monitoring server/Splunk servers
How is this application tested?
Before 2019 the universal forwarders in use are installed on a mix of Windows, Linux & AIX servers, in 2019 and beyond the testing scope has been vastly reduced to focus primarily on Splunk enterprise servers
All heavy forwarders, and Splunk enterprise installations are Linux based, while I expect the alerts will work with only changes to the macros.conf for a Windows based environment this remains untested
The test environment for this application has a single indexer cluster and two search head clusters
Why was this application and associated conf talk created?
Inspired by articles such as "Things I wish I knew then" and knowledge collected from various conference replays, SplunkAnswers, 200+ support tickets & nearly four years of working on a Splunk environment I decided that I would attempt to share what I have learned in an attempt to prevent others from repeating the same mistakes
There are many Splunk conf talks available on this subject in various conference replays, however my goal was to provide practical steps to implement the ideas. That is why this application exists
Which alerts are best suited to automation?
- SearchHeadLevel - Scheduled searches not specifying an index
- SearchHeadLevel - Scheduled Searches Configured with incorrect sharing
- SearchHeadLevel - Splunk login attempts from users that do not have any LDAP roles
- SearchHeadLevel - Scheduled Searches That Cannot Run
- SearchHeadLevel - Scheduled Searches without a configured earliest and latest time
- SearchHeadLevel - Users exceeding the disk quota
- SearchHeadLevel - User - Dashboards searching all indexes
Are all well suited to an automated email using the sendresults command or a similar function as they involve end user configuration which the individual can change/fix
Custom search commands
Due to the current SPL not handling a particular task well, and the lookup commands not supporting regular expressions, I found that the only workable solution was to create a custom lookup command.
Two exist:
- streamfilter - based on a single (or multivalue) field name, and a single (or multivalue) field with patterns, apply the regular expression in the pattern field against the nominated field(s)
- streamfilterwildcard - identical to streamfilter except that this takes a field name with wildcards, and assumes an index-style expression, so * becomes (?i)^[^_].*$, and example* becomes (?i)^example.*$
Search help is available and these are used within the reports in this application. The Splunk python SDK version 1.6.5 is also included as this is required as part of the app, an example from the reports is:
| streamfilterwildcard pattern=indexes fieldname=indexes srchIndexesAllowed
Where indexes is a field name containing a list of wildcards (_int*, _aud*) or similar, indexes is the output field name, srchIndexesAllowed is the field name which the indexes field will be compared to.
Each entry in the pattern field will be compared to each entry in the srchIndexesAllowed field in this example
To make this command work the Splunk python SDK is bundled into the app, if the bin directory is wiped due to issues with other applications this only disables the two commands which are used in Search Queries summary non-exact match so far
KVStore Usage
Some CSV lookups are now replaced with kvstore entries due to the ability to sync the kvstore across multiple search head or search head cluster(s) via apps like TA-SyncKVStore https://splunkbase.splunk.com/app/3519/
Feedback?
Feel free to provide feedback via SplunkBase and contributions are welcome!
GitHub Location
This project is open source and hosted on github SplunkAdmins
Release Notes
2.5.2
New modular input - Lookup Watcher - details in the README.md file
Introduced a new sub-menu in the navigation menu for Search Head Level "Recommended (externally hosted)" with links to external dashboards
Updated reports:
SearchHeadLevel - Search Queries By Type Audit Logs
SearchHeadLevel - Search Queries By Type Audit Logs macro version
SearchHeadLevel - Search Queries By Type Audit Logs macro version other
To reduce the number of unknown queries
Updated reports:
SearchHeadLevel - Search Queries summary exact match
SearchHeadLevel - Search Queries summary non-exact match
To improve the statistics around indexes found
2.5.1
Updated alert - SearchHeadLevel - Scheduled Searches That Cannot Run tweak to find more results
Updated dashboard issues per sourcetype to handle message becoming event_message in newer Splunk versions (7.1 or 7.2)
Updated macros splunkadmins_shutdown_list, splunkadmins_shutdown_keyword, splunkadmins_shutdown_time, splunkadmins_transfer_captain_times to handle message becoming event_message in newer Splunk versions (7.1 or 7.2)
Updated python files streamfilter/streamfilterwildcard to import lib relative to the current app name
Updated alerts / reports:
- AllSplunkLevel execprocessor errors
- AllSplunkLevel - TCP Output Processor has paused the data flow
- AllSplunkEnterpriseLevel - Detect LDAP groups that no longer exist
- AllSplunkEnterpriseLevel - Email Sending Failures
- AllSplunkEnterpriseLevel - File integrity check failure
- AllSplunkEnterpriseLevel - Non-existent roles are assigned to users
- AllSplunkEnterpriseLevel - Replication Failures
- AllSplunkEnterpriseLevel - TCP or SSL Config Issue
- AllSplunkEnterpriseLevel - Unable to dispatch searches due to disk space
- DeploymentServer - btool validation failures occurring on deployment server
- DeploymentServer - Unsupported attribute within DS config
- ForwarderLevel - crcSalt or initCrcLength change may be required
- ForwarderLevel - Splunk Universal Forwarders Exceeding the File Descriptor Cache
- IndexerLevel - Buckets are been frozen due to index sizing
- IndexerLevel - IndexConfig Warnings from Splunk indexers
- IndexerLevel - Index not defined
- IndexerLevel - Peer will not return results due to outdated generation
- IndexerLevel - Time format has changed multiple log types in one sourcetype
- IndexerLevel - Too many events with the same timestamp
- IndexerLevel - Valid Timestamp Invalid Parsed Time
- SearchHeadLevel - KVStore Or Conf Replication Issues Are Occurring
- SearchHeadLevel - LDAP users have been disabled or left the company cleanup required
- SearchHeadLevel - Scheduled Searches That Cannot Run
- SearchHeadLevel - Scheduled searches failing in cluster with 404 error
To handle message becoming event_message in newer Splunk versions (7.1 or 7.2)
2.5.0
New dashboard HEC Performance (original from camrunr's github)
New macro - splunkadmins_shutdown_keyword
New report - IndexerLevel - Knowledge bundle upload stats
Updated alert - AllSplunkEnterpriseLevel - Replication Failures with new criteria and excluded shutdowns
Updated alert - AllSplunkEnterpriseLevel - Splunk Scheduler skipped searches and the reason to handle another skipped scenario
Updated alert - AllSplunkEnterpriseLevel - Splunk Servers with resource starvation with new comments
Updated alert - SearchHeadLevel - Detect MongoDB errors with update to handle tstats issue in Splunk (issue #3 in github)
Moved splunklib into "lib" directory of app as per updated appinspect recommendations
2.4.9
Updated alert - SearchHeadLevel - Detect MongoDB errors to include " W " based on git feedback
2.4.8
New alert - ForwarderLevel - Splunk HEC issues
New dashboard - Lookups in use finder
New macro - splunkadmins_license_usage_source
New report - IndexerLevel - Maximum memory utilisation per search
New report - SearchHeadLevel - Lookup updates within SHC
New report - SearchHeadLevel - Maximum memory utilisation per search
New report - SearchHeadLevel - Detect Excessive Search Use - Dashboard - Automated
Updated alert - AllSplunkEnterpriseLevel - Replication Failures to match more results
Updated alert - ForwarderLevel - Splunk HTTP Listener Overwhelmed comment/description update
Updated dashboard - Rolled buckets by index - to no longer hardcode Linux paths to the license usage log
Updated dashboard - Heavy Forwarders Max Data Queue Sizes by name to use the thruput in the metrics.log
2.4.7
New README (README.md replaces README)
New dashboard Detect excessive search usage
New dashboard Cluster Master Jobs
New dashboard Knowledge Objects by app (and drilldown dashboard)
New report - IndexerLevel - Corrupt buckets via DBInspect
New report - SearchHeadLevel - Detect changes to knowledge objects
New report - SearchHeadLevel - Detect changes to knowledge objects directory
New report - SearchHeadLevel - Detect changes to knowledge objects non-directory
Updated alert ForwarderLevel - Splunk Universal Forwarders Exceeding the File Descriptor Cache (comment update)
Updated alert IndexerLevel - Uneven Indexed Data Across The Indexers to handle a varying number of indexers
Updated various reports to include the splunkadmins_restmacro, this ensures splunk_server=local is used where appropriate
Updated dashboard heavyforwarders_max_data_queue_sizes_by_name, now has a filter for hosts to look at, corrected TCPOut KB per second panel
Updated macro splunkadmins_splunkd_source now defaults to *splunkd.log (previously /opt/splunk/var/log/splunk/splunkd.log)
Updated macro splunkadmins_mongo_source now defaults to *mongod.log (previously /opt/splunk/var/log/splunk/mongod.log)
Updated report SearchHeadLevel - Search Queries summary exact to remove the mvexpand and selfjoin (replaced by stats)
Older releases
Refer to the README file for the full history of release notes
Other
Icons made by Freepik from www.flaticon.com is licensed by Creative Commons BY 3.0
Release Notes
Version 2.5.2
New modular input - Lookup Watcher - details in the README.md file
Introduced a new sub-menu in the navigation menu for Search Head Level "Recommended (externally hosted)" with links to external dashboards
Updated reports:
SearchHeadLevel - Search Queries By Type Audit Logs
SearchHeadLevel - Search Queries By Type Audit Logs macro version
SearchHeadLevel - Search Queries By Type Audit Logs macro version other
To reduce the number of unknown queries
Updated reports:
SearchHeadLevel - Search Queries summary exact match
SearchHeadLevel - Search Queries summary non-exact match
To improve the statistics around indexes found
Please note that if you are upgrading from a version pre 2.5.0 the bin/splunklib directory can be deleted from this app ($SPLUNK_HOME/etc/apps/SplunkAdmins/bin/splunklib is no longer required)
If you like this app you may also be interested in VersionControl For Splunk https://splunkbase.splunk.com/app/4355/
Version 2.5.1
Updated alert - `SearchHeadLevel - Scheduled Searches That Cannot Run` to find more results
Updated dashboard `issues per sourcetype` to handle message becoming event_message in newer Splunk versions (7.1 or 7.2)
Updated macros `splunkadmins_shutdown_list`, `splunkadmins_shutdown_keyword`, `splunkadmins_shutdown_time`, `splunkadmins_transfer_captain_times` to handle message becoming event_message in newer Splunk versions (7.1 or 7.2)
Updated python files streamfilter/streamfilterwildcard to import lib relative to the current app name
Updated many alerts/reports to handle the message field becoming event_message in newer Splunk versions (7.1 or 7.2), full list in the details tab or the README.md file
Please note that if you are upgrading from a version pre 2.5.0 the bin/splunklib directory can be deleted from this app ($SPLUNK_HOME/etc/apps/SplunkAdmins/bin/splunklib is no longer required)
If you like this app you may also be interested in VersionControl For Splunk https://splunkbase.splunk.com/app/4355/
Version 2.5.0
New macro - splunkadmins_shutdown_keyword
New report - IndexerLevel - Knowledge bundle upload stats
Updated alert - AllSplunkEnterpriseLevel - Replication Failures with new criteria and excluded shutdowns
Updated alert - AllSplunkEnterpriseLevel - Splunk Scheduler skipped searches and the reason to handle another skipped scenario
Updated alert - AllSplunkEnterpriseLevel - Splunk Servers with resource starvation with new comments
Updated alert - SearchHeadLevel - Detect MongoDB errors with update to handle tstats issue in Splunk (issue #3 in github)
Moved splunklib from bin to lib directory as per new appinspect recommendations
Please note that if you are upgrading from an older version the bin/splunklib directory can be deleted from this app ($SPLUNK_HOME/etc/apps/SplunkAdmins/bin/splunklib is no longer required)
If you like this app you may also be interested in VersionControl For Splunk https://splunkbase.splunk.com/app/4355/
Version 2.4.9
Change summary:
New alert - ForwarderLevel - Splunk HEC issues
New dashboard - Lookups in use finder
New macro - splunkadmins_license_usage_source
New report - IndexerLevel - Maximum memory utilisation per search
New report - SearchHeadLevel - Lookup updates within SHC
New report - SearchHeadLevel - Maximum memory utilisation per search
New report - SearchHeadLevel - Detect Excessive Search Use - Dashboard - Automated
Updated alert - AllSplunkEnterpriseLevel - Replication Failures to match more results
Updated alert - ForwarderLevel - Splunk HTTP Listener Overwhelmed comment/description update
Updated alert - SearchHeadLevel - Detect MongoDB errors` to include " W " based on git feedback
Updated dashboard - Rolled buckets by index - to no longer hardcode Linux paths to the license usage log
Updated dashboard - Heavy Forwarders Max Data Queue Sizes by name to use the thruput in the metrics.log
If you like this app you may also be interested in VersionControl For Splunk https://splunkbase.splunk.com/app/4355/
Version 2.4.8
Change summary:
New alert - ForwarderLevel - Splunk HEC issues
New dashboard - Lookups in use finder
New macro - splunkadmins_license_usage_source
New report - IndexerLevel - Maximum memory utilisation per search
New report - SearchHeadLevel - Lookup updates within SHC
New report - SearchHeadLevel - Maximum memory utilisation per search
New report - SearchHeadLevel - Detect Excessive Search Use - Dashboard - Automated
Updated alert - AllSplunkEnterpriseLevel - Replication Failures to match more results
Updated alert - ForwarderLevel - Splunk HTTP Listener Overwhelmed comment/description update
Updated dashboard - Rolled buckets by index - to no longer hardcode Linux paths to the license usage log
Updated dashboard - Heavy Forwarders Max Data Queue Sizes by name to use the thruput in the metrics.log
If you like this app you may also be interested in VersionControl For Splunk https://splunkbase.splunk.com/app/4355/
Version 2.4.7
Introduced an updated navigation menu to navigate around the alerts, reports and dashboards available in the app
Created a number of reports from Splunk audit logs around user search activity
New dashboards for troubleshooting poor user behaviour (Detect excessive search usage)
Change summary
2.4.7
New README (README.md replaces README)
New dashboard Detect excessive search usage
New dashboard Cluster Master Jobs
New dashboard Knowledge Objects by app (and drilldown dashboard)
New report - IndexerLevel - Corrupt buckets via DBInspect
New report - SearchHeadLevel - Detect changes to knowledge objects
New report - SearchHeadLevel - Detect changes to knowledge objects directory
New report - SearchHeadLevel - Detect changes to knowledge objects non-directory
If you like this app you may also be interested in VersionControl For Splunk https://splunkbase.splunk.com/app/4355/
Version 2.4.6
Minor changes since 2.4.5
Introduced an updated navigation menu to navigate around the alerts, reports and dashboards available in the app
Created a number of reports from Splunk audit logs around user search activity
Change summary
2.4.6
New alert - AllSplunkLevel - Data Loss on shutdown
New macro - whataccessdoihave - can be used with | `whataccessdoihave` by users
New report - SearchHeadLevel - Dashboard load times
New report - SearchHeadLevel - Scheduled searches status
Updated dashboard - Troubleshooting Resource Usage Per User Drilldown - now uses search_et/search_lt
Upgraded Splunk python SDK to 1.6.6, if this causes problems remove the bin directory this only disables the "Search Queries summary non-exact match" report
2.4.5
New dashboard - Troubleshooting Resource Usage Per User (&drilldown)
New commands - streamfilter, streamfilterwildcard
New reports around search query info
If you like this app you may also be interested in VersionControl For Splunk https://splunkbase.splunk.com/app/4355/
Version 2.4.5
Introduced an updated navigation menu to navigate around the alerts, reports and dashboards available in the app
Changed label of all dashboards to have Dashboard - ... this is just to make the navigation menu work as expected
Created a number of reports from Splunk audit logs around user search activity
Updated and corrected a number of alerts/reports, full details in the release notes
Change summary
New dashboard - Troubleshooting Resource Usage Per User
New dashboard - Troubleshooting Resource Usage Per User Drilldown
New command - streamfilter
New command - streamfilterwildcard
New reports around search query information
Version 2.4.3
No functional changes from 2.4.1/2.4.2, commenting out sendresults in 1 alert and removed 2 harmless errors to obtain the appinspect badge
Introduced an updated navigation menu to navigate around the alerts, reports and dashboards available in the app
Changed label of all dashboards to have Dashboard - ... this is just to make the navigation menu work as expected
New alert IndexerLevel - Buckets changes per day
New alert IndexerLevel - Timestamp parsing issues combined alert
New report SearchHeadLevel - Audit log search example only
Updated alert IndexerLevel - Future Dated Events that appeared in the last week to +10y instead of +20y
Updated alert IndexerLevel - Indexer Queues May Have Issues - to work with multiple pipelines
Updated alert IndexerLevel - Buckets rolling more frequently than expected with an improved regex
Updated alert SearchHeadLevel - Captain Switchover Occurring - to ignore manual captain transfers
Corrected alert SearchHeadLevel - Determine query scan density with a relevant query
Version 2.4.2
No functional changes from 2.4.1, commenting out sendresults in 1 alert to obtain the appinspect badge
Introduced an updated navigation menu to navigate around the alerts, reports and dashboards available in the app
Changed label of all dashboards to have Dashboard - ... this is just to make the navigation menu work as expected
New alert IndexerLevel - Buckets changes per day
New alert IndexerLevel - Timestamp parsing issues combined alert
New report SearchHeadLevel - Audit log search example only
Updated alert IndexerLevel - Future Dated Events that appeared in the last week to +10y instead of +20y
Updated alert IndexerLevel - Indexer Queues May Have Issues - to work with multiple pipelines
Updated alert IndexerLevel - Buckets rolling more frequently than expected with an improved regex
Updated alert SearchHeadLevel - Captain Switchover Occurring - to ignore manual captain transfers
Corrected alert SearchHeadLevel - Determine query scan density with a relevant query
Version 2.4.1
Introduced an updated navigation menu to navigate around the alerts, reports and dashboards available in the app
Changed label of all dashboards to have Dashboard - ... this is just to make the navigation menu work as expected
New alert IndexerLevel - Buckets changes per day
New alert IndexerLevel - Timestamp parsing issues combined alert
New report SearchHeadLevel - Audit log search example only
Updated alert IndexerLevel - Future Dated Events that appeared in the last week to +10y instead of +20y
Updated alert IndexerLevel - Indexer Queues May Have Issues - to work with multiple pipelines
Updated alert IndexerLevel - Buckets rolling more frequently than expected with an improved regex
Updated alert SearchHeadLevel - Captain Switchover Occurring - to ignore manual captain transfers
Corrected alert SearchHeadLevel - Determine query scan density with a relevant query
Version 2.3.9
Please note that this release renames the alert IndexerLevel - ERROR from linebreaker to IndexerLevel - Data parsing error
Also note that the app certification program is now over, a new badge for "app inspect certified" will appear in September
Creating new reports around users exceeding the disk quota, updates to a few other reports/alerts.
Update summary:
Updated alert SearchHeadLevel - Users exceeding the disk quota to include username
Updated report ForwarderLevel - Forwarders connecting to a single endpoint for extended periods (and UF level version)
Renamed alert IndexerLevel - ERROR from linebreaker to IndexerLevel - Data parsing error
New report SearchHeadLevel - Users exceeding the disk quota introspection
New report SearchHeadLevel - Users exceeding the disk quota introspection cleanup
Version 2.3.8
New reports for diagnosing forwarder issues, alerts around bucket corruption and peer connection failures
New dashboards for troubleshooting sourcetypes or buckets rolled per day
Updated all alerts with an investigationQuery to use index=* explicitly rather than assume the admin has all indexes listed in the indexes searched by default list
Updated alert ClusterMasterLevel - Per index status to 5 minute intervals for certification purposes
Refer to the details tab or README for more information
Version 2.3.7
New reports for diagnosing forwarder issues, alerts around bucket corruption and peer connection failures
New dashboards for troubleshooting sourcetypes or buckets rolled per day
New reports around forwarders connected to indexers or HF's for extended periods
New dashboard - Issues per sourcetype, a combination of timestamp parsing, future based and past data searches to look at a single problematic sourcetype
New dashboard - Rolled buckets by index, a dashboard to assist with determing which index is rolling the most buckets
Updated all alerts with an investigationQuery to use index=* explicitly rather than assume the admin has all indexes listed in the indexes searched by default list
Version 2.3.6
New reports for diagnosing forwarder issues, alerts around bucket corruption and peer connection failures
New dashboards for troubleshooting sourcetypes or buckets rolled per day
New reports around forwarders connected to indexers or HF's for extended periods
New dashboard - Issues per sourcetype, a combination of timestamp parsing, future based and past data searches to look at a single problematic sourcetype
New dashboard - Rolled buckets by index, a dashboard to assist with determing which index is rolling the most buckets
Updated all alerts with an investigationQuery to use index=* explicitly rather than assume the admin has all indexes listed in the indexes searched by default list
Version 2.3.5
Minor tweaks to support 7.1
Updated IndexerLevel - Cold data location approaching size limits to handle only maxTotalDataSizeMB been set
Updated Future Dated Events that appeared in the last week to use +10y and 7.1 rejects +20y
Corrected AllSplunkEnterpriseLevel - TCP or SSL Config Issue to remove extra ( symbol
Corrected SearchHeadLevel - User - Dashboards searching all indexes macro version to refer to correct lookup name
Corrected dashboard for troubleshooting indexer CPU to handle standalone server
Inclusion of alternative app icons to work in 7.1
Updated SearchHeadLevel - Scheduled searches not specifying an index to exclude 1 additional type of search
Updated SearchHeadLevel - KVStore Or Conf Replication Issues Are Occurring to detect a disconnected member scenario
Updated Troubleshooting indexer CPU & drilldown dashboards to include commmas and the search head field (to make it easier to update to search head instead of indexer hosts)
Note 2.3.4 was not released
Version 2.3.4
Update summary:
Updated SearchHeadLevel - Scheduled searches not specifying an index to exclude 1 additional type of search
Updated SearchHeadLevel - KVStore Or Conf Replication Issues Are Occurring to detect a disconnected member scenario
Updated Troubleshooting indexer CPU & drilldown dashboards to include commas and the search head field (to make it easier to update to search head instead of indexer hosts)
Version 2.3.3
Update summary:
New alert SearchHeadLevel - Disabled modular inputs are running
Updated SearchHeadLevel - Detect MongoDB errors to timechart to have no limit on the number of hosts involved
Updated the shutdown macros to find one additional scenario
Version 2.3.2
Due to resourcing issues on the search heads this includes a few warnings/errors related to performance issues
Update summary:
New alert AllSplunkEnterpriseLevel - Splunk Servers with resource starvation
New alert IndexerLevel - S2SFileReceiver Error
New alert SearchHeadLevel - Captain Switchover Occurring
Various miscellaneous updates (refer to README)
Corrected AllSplunkEnterpriseLevel - sendmodalert errors to not show random savedsearch_names when no match is found
Corrected SearchHeadLevel - Alerts that have not fired an action in X days to only show alerts relevant to the current search head/cluster
Version 2.3.1
Update summary:
New alert AllSplunkEnterpriseLevel - Non-existent roles are assigned to users
New alert IndexerLevel - Index not defined
New alert IndexerLevel - Search Failures
New alert SearchHeadLevel - Saved Searches with privileged owners and excessive write perms (detect 1 way of accessing data outside your level of access)
New report SearchHeadLevel - Macro report (required by "macro version" alerts)
New alerts for detecting macro usage within saved searches/dashboards
Various minor updates
Corrected AllSplunkLevel - Unable To Distribute to Peer
Corrected IndexerLevel - Failures To Parse Timestamp Correctly (excluding breaking issues) to correctly exclude broken events & to handle newer 7.0.2 errors
Version 2.3.0
Attempt to reduce false alarms and improve investigationQuery searches
Created macros for shutdown events for indexers/search heads/enterprise servers for excluding false alarms related to restarts
Update summary:
New alert ClusterMasterLevel - Per index status
New macro splunkadmins_shutdown_list
New macro splunkadmins_shutdown_time
New report ClusterMasterLevel - Primary bucket count per peer
Updated various alerts to use new shutdown macros
Updated SearchHeadLevel - Scheduled Searches That Cannot Run - to detect errors in splunkd related to saved searches
Corrected SearchHeadLevel - User - Dashboards searching all indexes - a newline resulted in it working in search but not via the scheduler!
Version 2.2
Attempted to reduce false alarms and made further improvements to investigationQueries, the idea behind the "investigationQuery" is that you can copy and paste the output into a search window and see results relevant to the particular alert
Macros now exist for shutdown events for indexers/search heads/enterprise servers this helps reduce false alarms related to restart events
In the previous release macros were added to the majority of alerts, this should remove the requirement for the alerts to be customised locally and ensure upgrades are more straightforward
Update summary (see README for more details):
New macro splunkadmins_shutdown_list
New macro splunkadmins_shutdown_time
Updated various alerts to use the above macros
Version 1.5
Updated Splunk Alert Failures alert and the Time format has changed alerts to have more clear output via email
Includes changes from 1.4 (and 1.3 which was the application icon), two new alerts LicenseMaster - Duplicated License Situation, DeploymentServer - Unsupported attribute within DS config
Simplified "Scheduled Searches without a configured earliest and latest time", and "Scheduled searches not specifying an index"
Created a macro splunkadmins_splunkd_source for Windows users or others using non-standard Splunk installation directories
Updated the README