All Posts

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

All Posts

Please share your sql query, table structure and some sample events.
Hi @NanSplk01 , why do you want to use the subsearch? if I correctly understand you need only to truncate the Message field to the first 3 chars, is it correct? index=replicate category=* action=*... See more...
Hi @NanSplk01 , why do you want to use the subsearch? if I correctly understand you need only to truncate the Message field to the first 3 chars, is it correct? index=replicate category=* action=* Message=* | eval Msg=substr(Message,1,30) | stats values(category) AS category values(Msg) AS Msg BY action Ciao. Giuseppe
Hi @bond77s , not having your search (as also @isoutamo said) it's difficoult to help you, at least, please better describe your requirements. anyway supponing that you have a search and you want t... See more...
Hi @bond77s , not having your search (as also @isoutamo said) it's difficoult to help you, at least, please better describe your requirements. anyway supponing that you have a search and you want to check if the hostname from the search is listed in the lookup and that MESSAGE_TEXT is a field in your main search and yu want only the events with this condition, you could try something like this: index=your_index MESSAGE_TEXT="Radius" [ |inputlookup filename | rename hostname AS host | fields host ] | ... Then, if in your main search you have also a field called ip and you want to check both host and ip, you could try something like this: index=your_index MESSAGE_TEXT="Radius" ([ |inputlookup filename | rename hostname AS host | fields host ] OR [ |inputlookup filename | fields ip ] Ciao. Giuseppe
Please share some sample data and explain how and where you configured the props.conf.
Check out following helpful docs and specifications files How Splunk Enterprise handles your data - Splunk Documentation props.conf - Splunk Documentation transforms.conf - Splunk Documentation
Hi @super_edition , my hint is to continue to try using stats to reach the wanted output, because join is a very slow command that requires many resources and it's always better to avoid it. Ciao. ... See more...
Hi @super_edition , my hint is to continue to try using stats to reach the wanted output, because join is a very slow command that requires many resources and it's always better to avoid it. Ciao. Giuseppe
Hi, I have deployed AppServerAgent-1.8-24.9.0.36347 with following steps but agent is showing errors and not getting uploaded.  ENV APPDYNAMICS_CONTROLLER_HOST_NAME=" abc" ENV APPDYNAMICS_CONTROLL... See more...
Hi, I have deployed AppServerAgent-1.8-24.9.0.36347 with following steps but agent is showing errors and not getting uploaded.  ENV APPDYNAMICS_CONTROLLER_HOST_NAME=" abc" ENV APPDYNAMICS_CONTROLLER_PORT="443" ENV APPDYNAMICS_AGENT_ACCOUNT_NAME="abc" ENV APPDYNAMICS_AGENT_ACCOUNT_ACCESS_KEY="your-access-key"  point. ENVAPPDYNAMICS_AGENT_APPLICATION_NAME=" -----------" ENV APPDYNAMICS_AGENT_TIER_NAME=" ----------- "ENV APPDYNAMICS_AGENT_NODE_NAME="your-node name" agent is not getting loaded and giving error: Error: it is because if application name is not get resolved or do i need to make some other configurations? 024-11-14 13:02:18 OpenJDK 64-Bit Server VM warning: Sharing is only supported for boot loader classes because bootstrap classpath has been appended 2024-11-14 13:02:18 Java 9+ detected, booting with Java9Util enabled. 2024-11-14 13:02:18 Full Agent Registration Info Resolver found env variable [APPDYNAMICS_AGENT_APPLICATION_NAME] for application name [measurement-api-service-637966829491.us-east1.run.app] 2024-11-14 13:02:18 Full Agent Registration Info Resolver found env variable [APPDYNAMICS_AGENT_TIER_NAME] for tier name [measurement-api-service-637966829491.us-east1.run.app] 2024-11-14 13:02:18 Full Agent Registration Info Resolver found env variable [APPDYNAMICS_AGENT_NODE_NAME] for node name [measurement-api-service-637966829491.us-east1.run.app] 2024-11-14 13:02:19 Full Agent Registration Info Resolver using selfService [false] 2024-11-14 13:02:19 Full Agent Registration Info Resolver using selfService [false] 2024-11-14 13:02:19 Full Agent Registration Info Resolver using ephemeral node setting [false] 2024-11-14 13:02:19 Full Agent Registration Info Resolver using application name [measurement-api-service-637966829491.us-east1.run.app] 2024-11-14 13:02:19 Full Agent Registration Info Resolver using tier name [measurement-api-service-637966829491.us-east1.run.app] 2024-11-14 13:02:19 Full Agent Registration Info Resolver using node name [measurement-api-service-637966829491.us-east1.run.app] 2024-11-14 13:02:19 Install Directory resolved to[/opt/appdynamics] 2024-11-14 13:02:19 getBootstrapResource not available on ClassLoader 2024-11-14 13:02:20 Class with name [com.ibm.lang.management.internal.ExtendedOperatingSystemMXBeanImpl] is not available in classpath, so will ignore export access. 2024-11-14 13:02:20 Class with name [jdk.internal.util.ReferencedKeySet] is not available in classpath, so will ignore export access. 2024-11-14 13:02:20 Failed to locate module [jdk.jcmd] 2024-11-14 13:02:20 Failed to locate module [jdk.attach] 2024-11-14 13:02:23 [AD Agent init] Thu Nov 14 07:32:23 GMT 2024[DEBUG]: JavaAgent - Setting AgentClassLoader as Context ClassLoader 2024-11-14 13:02:25 [AD Agent init] Thu Nov 14 07:32:25 GMT 2024[INFO]: JavaAgent - Low Entropy Mode: Attempting to swap to non-blocking PRNG algorithm 2024-11-14 13:02:25 [AD Agent init] Thu Nov 14 07:32:25 GMT 2024[INFO]: JavaAgent - UUIDPool size is 10 2024-11-14 13:02:25 Agent conf directory set to [/opt/appdynamics/ver24.9.0.36347/conf] 2024-11-14 13:02:25 [AD Agent init] Thu Nov 14 07:32:25 GMT 2024[INFO]: JavaAgent - Agent conf directory set to [/opt/appdynamics/ver24.9.0.36347/conf] 2024-11-14 13:02:25 [AD Agent init] Thu Nov 14 07:32:25 GMT 2024[DEBUG]: AgentInstallManager - Full Agent Registration Info Resolver is running 2024-11-14 13:02:25 [AD Agent init] Thu Nov 14 07:32:25 GMT 2024[INFO]: AgentInstallManager - Full Agent Registration Info Resolver found env variable [APPDYNAMICS_AGENT_APPLICATION_NAME] for application name [measurement-api-service-637966829491.us-east1.run.app] 2024-11-14 13:02:25 [AD Agent init] Thu Nov 14 07:32:25 GMT 2024[INFO]: AgentInstallManager - Full Agent Registration Info Resolver found env variable [APPDYNAMICS_AGENT_TIER_NAME] for tier name [measurement-api-service-637966829491.us-east1.run.app] 2024-11-14 13:02:25 [AD Agent init] Thu Nov 14 07:32:25 GMT 2024[INFO]: AgentInstallManager - Full Agent Registration Info Resolver found env variable [APPDYNAMICS_AGENT_NODE_NAME] for node name [measurement-api-service-637966829491.us-east1.run.app] 2024-11-14 13:02:26 [AD Agent init] Thu Nov 14 07:32:26 GMT 2024[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using selfService [false] 2024-11-14 13:02:26 [AD Agent init] Thu Nov 14 07:32:26 GMT 2024[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using selfService [false] 2024-11-14 13:02:26 [AD Agent init] Thu Nov 14 07:32:26 GMT 2024[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using ephemeral node setting [false] 2024-11-14 13:02:26 [AD Agent init] Thu Nov 14 07:32:26 GMT 2024[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using application name [measurement-api-service-637966829491.us-east1.run.app] 2024-11-14 13:02:26 [AD Agent init] Thu Nov 14 07:32:26 GMT 2024[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using tier name [measurement-api-service-637966829491.us-east1.run.app] 2024-11-14 13:02:26 [AD Agent init] Thu Nov 14 07:32:26 GMT 2024[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using node name [measurement-api-service-637966829491.us-east1.run.app] 2024-11-14 13:02:26 [AD Agent init] Thu Nov 14 07:32:26 GMT 2024[DEBUG]: AgentInstallManager - Full Agent Registration Info Resolver finished running 2024-11-14 13:02:26 [AD Agent init] Thu Nov 14 07:32:26 GMT 2024[INFO]: AgentInstallManager - Agent runtime directory set to [/opt/appdynamics/ver24.9.0.36347] 2024-11-14 13:02:26 [AD Agent init] Thu Nov 14 07:32:26 GMT 2024[INFO]: AgentInstallManager - Agent node directory set to [measurement-api-service-637966829491.us-east1.run.app] 2024-11-14 13:02:26 Agent runtime conf directory set to /opt/appdynamics/ver24.9.0.36347/conf 2024-11-14 13:02:26 [AD Agent init] Thu Nov 14 07:32:26 GMT 2024[INFO]: AgentInstallManager - Agent runtime conf directory set to /opt/appdynamics/ver24.9.0.36347/conf 2024-11-14 13:02:26 [AD Agent init] Thu Nov 14 07:32:26 GMT 2024[INFO]: JavaAgent - JDK Compatibility: 1.8+ 2024-11-14 13:02:26 [AD Agent init] Thu Nov 14 07:32:26 GMT 2024[INFO]: JavaAgent - Using Java Agent Version [Server Agent #24.9.0.36347 v24.9.0 GA compatible with 4.4.1.0 r8d55fc625d557c4c19f7cf97088ecde0a2e43e82 release/24.9.0] 2024-11-14 13:02:26 [AD Agent init] Thu Nov 14 07:32:26 GMT 2024[INFO]: JavaAgent - Running IBM Java Agent [No] Thanks & Regards Rupinder Kaur 
@gcusello  I was able to get the desired output with inner join
I'm creating it from scratch, 8080,9887 is not in listen state. i'm unable to connect to master from peer ProxyConfig  - Failed to initialize http_proxy from server.conf for splunkd. P lease mak... See more...
I'm creating it from scratch, 8080,9887 is not in listen state. i'm unable to connect to master from peer ProxyConfig  - Failed to initialize http_proxy from server.conf for splunkd. P lease make sure that the http_proxy property is set as http_proxy=http://host:port in case HTTP proxying needs to be enabled. INFO ProxyConfig  - Failed to initialize https_proxy from server.conf for splunkd. Please make sure that the https_proxy property is set as https_proxy=http://host:port in case HTTP proxying needs to be enabled. INFO ProxyConfig - Failed to initialize the proxy_rules setting from server.conf f or splunkd. Please provide a valid set of proxy_rules in case HTTP proxying needs to be enabled. INFO ProxyConfig - Failed to initialize the no_proxy setting from server.conf for splunkd. Please provide a valid set of no_proxy rules in case HTTP proxying needs to be enabled. INFO WatchedFile  - File too small to check seekcrc, probably truncated. Will re-re ad entire file='/opt/splunk/var/log/introspection/http_event_collector_metrics.log'. WARN SSLOptions  - server.conf/[search_state]/sslVerifyServerCert is false disab ling certificate validation; must be set to "true" for increased security  WARN SSLOptions- <internal>.conf/[<internal>]/sslVerifyServerCert is false disabling certificate validation; must be set to "true" for increased security  IntrospectionGenerator:resource_usage - RU_main - I-data gathering (Resource Usage) starting; period=10s
Can you add your whole SPL query here, as @ITWhisperer said, your example didn't contains any fields which have value Radius.
Hello experts. I'm a Splunk newbie. I am using the Jira Service Desk simple AddOn to send Splunk alarms to Jira tickets. We also confirmed that Splunk alarms were successfully raised through Jira... See more...
Hello experts. I'm a Splunk newbie. I am using the Jira Service Desk simple AddOn to send Splunk alarms to Jira tickets. We also confirmed that Splunk alarms were successfully raised through Jira tickets. However, sometimes it is the same alarm, but a specific alarm receives the customfield value well, but there are cases where no value is retrieved.   In Splunk, it is confirmed that the value exists, but the value cannot be retrieved. No matter how much I searched, I couldn't find out what the reason was. If the Jira and Splunk field mappings are incorrect, you shouldn't be able to get the value from all tickets, but you can't get it from a specific ticket... What's the problem? Example here... The Client value is always a value. However, as shown in the images, the customer value does not exist.  [Error Ticket]   [Normal Ticket]        
Have this cluster work earlier or are you just putting it up from scratch? Did you see any connections attemps in master's internal logs? Are there any other messages in peer's internal logs? Can y... See more...
Have this cluster work earlier or are you just putting it up from scratch? Did you see any connections attemps in master's internal logs? Are there any other messages in peer's internal logs? Can you use e.g. curl or nc to connect masters management port from peer?
hi @isoutamo  yes, this is on indexer cluster - on all 3 nodes ID1,ID2,ID3 yes, master node is up and running, I can see no error logs from splunkd.log from master
Hi Was this on indexer? Have you checked that master node is up and running? If it's up and running, there should be some more hints on its internal logs. Just check those to get more hints. r. Ismo
hi @phanichintha , is this issue resolved ? if yes, could you post you solution, even I am facing the same issue https://community.splunk.com/t5/Deployment-Architecture/ERROR-CMSlave-Waiting-for-the-... See more...
hi @phanichintha , is this issue resolved ? if yes, could you post you solution, even I am facing the same issue https://community.splunk.com/t5/Deployment-Architecture/ERROR-CMSlave-Waiting-for-the-cluster-manager-to-come-up/m-p/704380#M28826
Anyone don't have same problem here ? 
hi guys After adding [clustering] stanza and [replication_port://9887] in indexer cluster,  getting the below error ERROR  - Waiting for the cluster manager to come up... (retrying every second),bu... See more...
hi guys After adding [clustering] stanza and [replication_port://9887] in indexer cluster,  getting the below error ERROR  - Waiting for the cluster manager to come up... (retrying every second),but  service is running, but it stuck at this point - Waiting for web server at http://<ip>:8000 to be available. later, got this warning, WARNING: web interface does not seem to be available! how to I fix this issue ? 8000,9887 ports are already open, I've passed same pass4SymmKey for all 3 servers in indexer cluster tags: @any  
Our add-on requires dateparser and within dateparser the regex library is required. I added the libraries to my addon (built with Add-on Builder 4.3) however, it fails in Splunk 9.2 with: File "/opt... See more...
Our add-on requires dateparser and within dateparser the regex library is required. I added the libraries to my addon (built with Add-on Builder 4.3) however, it fails in Splunk 9.2 with: File "/opt/splunk/etc/apps/.../regex/_regex_core.py", line 21, in <module> import regex._regex as _regex ModuleNotFoundError: No module named 'regex._regex' If I try on Splunk 9.3 it works fine.  I know Python version changed from 3.7 to 3.9 on Splunk 9.3 but the regex version 2024.4.16 seems to be good for Python 3.7 I will appreciate any insight on how to solve this issue.
Several problems with the illustrated search.  Most important one is use of join.  This is rarely the solution to any problem in Splunk.  Then, there is the problem of bad quotation marks. Even with... See more...
Several problems with the illustrated search.  Most important one is use of join.  This is rarely the solution to any problem in Splunk.  Then, there is the problem of bad quotation marks. Even without this, like @ITWhisperer says, illustrating useful data input is the best way to enable volunteers to help you.  Your illustrated search syntax is so mixed up I cannot even tell whether the two searches are using the same index. Without any assumption about which data source(s) are used, you can get desired result using append and stats, assuming that my speculation about your syntax reflects the correct filter. index=source "status for : *" "Not available" | rex field=_raw "status for : (?<ORDERS>.*?)" | fields ORDERS | dedup ORDERS | eval status = "Not available" | append [search Message="Request for : *" | rex field=_raw "data=[A-Za-z0-9-]+\|(?P<ORDERS>[\w\.]+)" | rex field=_raw "\"unique\"\:\"(?P<UNIQUEID>[A-Z0-9]+)\"" | fields ORDERS UNIQUEID | dedup ORDERS UNIQUEID] | stats values(*) as * by ORDERS | where status == "Not available" | fields - status Note in search command, AND between terms is implied and rarely need to be spelled out. Now, if the two searches use the same index, it is perhaps more efficient to NOT use append. (Much less join.)  Instead, combine the two in one search. index=source (("status for : *" "Not available") OR Message="Request for : *") | rex field=_raw "status for : (?<ORDERS>.*?)" | rex field=_raw "data=[A-Za-z0-9-]+\|(?P<ORDERS>[\w\.]+)" | rex field=_raw "\"unique\"\:\"(?P<UNIQUEID>[A-Z0-9]+)\"" | fields ORDERS UNIQUEID | eval not_available = if(searchmatch("Not available"), "yes", null()) | stats values(*) as * by ORDERS | where isnotnull(not_available) | fields - not_available  
Is it possible to hide these two options also from the setting in Splunk ?