All Posts

Find Answers
Ask questions. Get answers. Find technical product solutions from passionate members of the Splunk community.

All Posts

This is an indication of inefficient bucket use, meaning buckets roll `before they fill up.  This can happen when indexers restart often, but in this case I suspect it's just a matter of the main ind... See more...
This is an indication of inefficient bucket use, meaning buckets roll `before they fill up.  This can happen when indexers restart often, but in this case I suspect it's just a matter of the main index getting very few events before maxHotSpecSecs is reached and the bucket rolls to warm. The answer for buckets that are known to contain few events is to set maxDataSize to a value that makes the bucket at least 50% full before it rolls.  The default bucket size is 750MB.  The dbinspect command can tell you the current size of buckets to give you an idea of how to set maxDataSize. Best Practice is to not use the main index at all.  All incoming data should go into a custom index, leaving main empty (and not needing to roll).
I have the same question
We've added documentation to dev.splunk.com to cover Custom REST Endpoints.   (apologies for thread necromancy but this is still one of the top hits on gsearch for this topic somehow, 14 years late... See more...
We've added documentation to dev.splunk.com to cover Custom REST Endpoints.   (apologies for thread necromancy but this is still one of the top hits on gsearch for this topic somehow, 14 years later) 
I have a list of email addresses being returned by a query that I want to use to update a custom list. My goal is to have one value per row. If I add a utility block "add_to_list" to my playbook, the... See more...
I have a list of email addresses being returned by a query that I want to use to update a custom list. My goal is to have one value per row. If I add a utility block "add_to_list" to my playbook, then all the values get added in as a single row, with a separate value per column. I assume this is because the values being returned are seen as a single long comma-delimited list. What is the best practice for ensuring my playbook is updating the custom list with just one value per row, and adding new rows for each value in my list?
Hi @Gururaj1  The UF does not have a web UI.  Check /opt/splunkforwarder/var/log/splunk/splunkd.log to see if the server is running (it should update quite regularly)  Did this answer help you? ... See more...
Hi @Gururaj1  The UF does not have a web UI.  Check /opt/splunkforwarder/var/log/splunk/splunkd.log to see if the server is running (it should update quite regularly)  Did this answer help you? If so, please consider: Adding karma to show it was useful Marking it as the solution if it resolved your issue Commenting if you need any clarification Your feedback encourages the volunteers in this community to continue contributing
@marisstella- Kindly please accept the answer @isoutamo if that help you resolve/understand your query by clicking on "Accept as Solution" so future Splunk Community users will get benefited from you... See more...
@marisstella- Kindly please accept the answer @isoutamo if that help you resolve/understand your query by clicking on "Accept as Solution" so future Splunk Community users will get benefited from your question as well.
Hello @livehybrid , thank you for the update,  I would have ignored this if I was able to access the splunk UF webpage. But the issue here the webpage timeout appears and I tested the exact scenario... See more...
Hello @livehybrid , thank you for the update,  I would have ignored this if I was able to access the splunk UF webpage. But the issue here the webpage timeout appears and I tested the exact scenario with splunk HF and Splunk Enterprise  9.4.1 and it works perfectly fine[No errors while installation]. Am i missing something here ? However, thank you. If you find any resolution to this, please do let me know. As the issue is unknown, not sure how to tackle..
Good morning, I got a query like this [| makeresults count=0] | append [ search (index="my_index"] When I use to setup analert like  earliest="04/11/2025:12:10:01" latest="04/11/2025:12:20:01" `... See more...
Good morning, I got a query like this [| makeresults count=0] | append [ search (index="my_index"] When I use to setup analert like  earliest="04/11/2025:12:10:01" latest="04/11/2025:12:20:01" `mymacro` | table _time IP this is not picking up the events in that time frame. however when I expand to 8hours from dropdown it is showing results.   Any one can help provide approach for this issue?
Hi @Gururaj1  Just to check - apart from the errors you mentioned - Does Splunk install correctly? Those errors dont necessarily mean there is an issue - its likely that part of the debian preinst s... See more...
Hi @Gururaj1  Just to check - apart from the errors you mentioned - Does Splunk install correctly? Those errors dont necessarily mean there is an issue - its likely that part of the debian preinst script which calls a "temp_splunk-preinstall" file - this is looking for those locations to do *something* - "find" is usually used to "find" something (file/folder) and then do something to it like update permissions or something.  If the find returns no files the script looks to continue, finally finishing with "complete" - at this point I'd expect your install to be complete - Since you splunk validate command returned a success I thing these "errors" are benign.  The existence of them is either a mistake in that script - OR - it could be for something we arent necessarily aware of. Either way, If the files get installed then I'm confident this isnt an issue.  Did this answer help you? If so, please consider: Adding karma to show it was useful Marking it as the solution if it resolved your issue Commenting if you need any clarification Your feedback encourages the volunteers in this community to continue contributing
Oh, thanks for the confirmation.. 
Hi @wm  Given that you are using the same connection details and the servers should be setup the same, it feels like the issue could be either network related or authentication related, as you have ... See more...
Hi @wm  Given that you are using the same connection details and the servers should be setup the same, it feels like the issue could be either network related or authentication related, as you have proven Splunk to be working. Try and establish a telnet connection between your Splunk host and the non-working database host on the relevant DB port. If this works then it demonstrates that the firewall is allowing connection. Double check the authentication credentials - are you using different passwords for the 2 databases or are they using a domain account? If a domain account, does it have the relevant permissions for the non-working server?  Are there any logs you can see on the database server around the connection?  Did this answer help you? If so, please consider: Adding karma to show it was useful Marking it as the solution if it resolved your issue Commenting if you need any clarification Your feedback encourages the volunteers in this community to continue contributing
Hi @tech_g706  The last version that was listed as supporting Windows 2008 was 7.2.10 (See https://docs.splunk.com/Documentation/Splunk/7.2.10/Installation/Systemrequirements) - This lists it as Dep... See more...
Hi @tech_g706  The last version that was listed as supporting Windows 2008 was 7.2.10 (See https://docs.splunk.com/Documentation/Splunk/7.2.10/Installation/Systemrequirements) - This lists it as Deprecated and it was removed from the next version. UF 7.2.10 actually went out of Splunk support in April 2021 (With P3 support ending in 2023). The following shows a matrix of supported forwarders->Indexers which might also be useful: https://docs.splunk.com/Documentation/VersionCompatibility/current/Matrix/Compatibilitybetweenforwardersandindexers Unfortunately it looks like you might already be on the latest version known to work with Windows 2008. It not being listed doesnt necessarily mean it wont work with 2008 - but it wont be supported and there may be issues we arent aware of.  Did this answer help you? If so, please consider: Adding karma to show it was useful Marking it as the solution if it resolved your issue Commenting if you need any clarification Your feedback encourages the volunteers in this community to continue contributing
I wouldn't expect any modern UF to be not only supported but also to work. That windows release is so out of support that I'd be more concerned with the OS itself than the UF version.
Hi @tech_g706 , there isn't any 8.x version certified compatible with Windows 2008/R2 and supported by Splunk. Probably the 9.4.x version runs on Windows 2008/R2 but it isn't certified and supporte... See more...
Hi @tech_g706 , there isn't any 8.x version certified compatible with Windows 2008/R2 and supported by Splunk. Probably the 9.4.x version runs on Windows 2008/R2 but it isn't certified and supported by Splunk. The only that  can formally answer to your question is Splunk Support. Ciao. Giuseppe
Although it looks like you should be able to use the "move" link in "Lookup definitions", you cannot. The best way to achieve this is to create a new KVstore in the desired location then copy the KV... See more...
Although it looks like you should be able to use the "move" link in "Lookup definitions", you cannot. The best way to achieve this is to create a new KVstore in the desired location then copy the KVstore data there. | inputlookup my_old_kvstore | outputlookup my_new_kvstore I did create a Splunk Idea to resolve this issue. Please vote for it here.
After moving a KVstore to a new Application, Splunk can not longer render the lookup. When moving a KVstore using the "move" link in "Lookup definitions" it only moves the transforms.conf stanza and... See more...
After moving a KVstore to a new Application, Splunk can not longer render the lookup. When moving a KVstore using the "move" link in "Lookup definitions" it only moves the transforms.conf stanza and not the collections.conf stanza. The on-prem solution is to manually move collections.conf but this cannot be done in Splunk Cloud.
Thanks, Upon checking the logs, it seems MongoDB is not running on the heavy forwarder, and that would be required. ta_netskopeappforsplunk_netskope_alerts_v2.log splunklib.binding.HTTPError: ... See more...
Thanks, Upon checking the logs, it seems MongoDB is not running on the heavy forwarder, and that would be required. ta_netskopeappforsplunk_netskope_alerts_v2.log splunklib.binding.HTTPError: HTTP 503 Service Unavailable -- KV Store initialization failed. 2: splunkd.log: ERROR KVStoreConfigurationProvider [15442 KVStoreConfigurationThread] - Failed to start mongod on first attempt reason=KVStore service will not start because kvstore process terminated  ERROR KVStoreConfigurationProvider [15442 KVStoreConfigurationThread] - Could not start mongo instance. Initialization failed.  ERROR KVStoreBulletinBoardManager [15442 KVStoreConfigurationThread] - Failed to start KV Store process. See mongod.log and splunkd.log for details. INFO  KVStoreConfigurationProvider [15442 KVStoreConfigurationThread] - Mongod service shutting down
Hi, We have some Windows 2008 R2 machines where UF 7.2 is running, and in Splunk Cloud CMC, we are getting the forwarder status as critical. My question is, can we install 9.4 or above 9 on the  Wi... See more...
Hi, We have some Windows 2008 R2 machines where UF 7.2 is running, and in Splunk Cloud CMC, we are getting the forwarder status as critical. My question is, can we install 9.4 or above 9 on the  Windows 2008 R2 machines? If not, what is the minimum supported UF version for Windows 2008 R2, and possible workaround to mitigate the critical status notification on Splunk Cloud CMC?   Thank you!
You should not need to enable the inputs separately on each indexer. That's what the CM-pushed apps are for.
@wm  Did you check the primary server is reachable from the Splunk server:  telnet <ServerName> <port>. Given the secondary database works, the issue is likely network-related (firewall, port, DNS)... See more...
@wm  Did you check the primary server is reachable from the Splunk server:  telnet <ServerName> <port>. Given the secondary database works, the issue is likely network-related (firewall, port, DNS) or authentication-related on the primary server. Ensure that no firewalls, network security groups, or proxies are blocking or interrupting the connection between the Splunk server and the HPC primary database.