All Posts

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

All Posts

Hi, I have business use case of creating an alert wherein it has to search and trigger if the condition is matched, this alert is cron scheduled at 1pm from Monday through Friday.   The query:... See more...
Hi, I have business use case of creating an alert wherein it has to search and trigger if the condition is matched, this alert is cron scheduled at 1pm from Monday through Friday.   The query: index=xyz | head 1 | eval month_year=strftime(now(),"%c") | table month_year   I work on IST zone, the splunk server is CST/CDT zone, but from the alert mail we can see that the search was executed on 1pm(13:00), but trigger time is 1:14 am CST, I received the alert mail on 11:44am IST. Actually I should receive the mail on 11pm IST, Please help me out there.     Thanks  
Can you give an example of what 45123 is supposed to be as a date? I can make a guess but it might be wrong which would waste everyone's time.
Hi, We are running many applications with JAVA_AGENT and out of those, a few applications are discovering the JDBC calls and a few are not discovering the JDBC backend. I even tried to manually add ... See more...
Hi, We are running many applications with JAVA_AGENT and out of those, a few applications are discovering the JDBC calls and a few are not discovering the JDBC backend. I even tried to manually add a custom discovery with rule of matching URL. What all other factors impacting this and anything needs to be changed? Have attached the samples here. Note: 1. Both apps are using same version of MySQL connector jar.  mysql-connector-java : 5.1.49 For the application where the JDBC details and queries are captured.  For the similar application where JDBC details are not captured. Note:  1. For the app where details are captured is a web-app where business-transaction are present. but for the app where this is not captured is a core java app without transaction. ( More like a monitoring app ). Does this have any impact? Thanks & Regards. Akshay
Hello Splunkers!! Every week, my report runs and gathers the results under the summary index=analyst. You can see that several stash files are being created for the specific report in the screenshot... See more...
Hello Splunkers!! Every week, my report runs and gathers the results under the summary index=analyst. You can see that several stash files are being created for the specific report in the screenshot below. Conversely, multiple stash files won't be created for other reports.   Report with multiple stash files. Report with no duplicate no stash files. Please provide me an assistance on this.
How can we ingest MDI logs to Splunk?
After upgrade from 9.1.0 to 9.2.1, my heavy forwarder has many following lines in log:   04-01-2024 08:56:16.812 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 afte... See more...
After upgrade from 9.1.0 to 9.2.1, my heavy forwarder has many following lines in log:   04-01-2024 08:56:16.812 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:16.887 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:16.951 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:16.982 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.008 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.013 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.024 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.041 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.079 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.097 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.146 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.170 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.190 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.257 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.292 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.327 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.425 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.522 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.528 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.549 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped. 04-01-2024 08:56:17.551 +0700 INFO TcpInputProc [103611 FwdDataReceiverThread] - Input queue has pds 0 after reader thread stopped.     How to disable this log? Does any error related this INFO log?
Shouldn't we be looking for xz-utils rather than xz-libs? like this source=package sourcetype=package NAME=xz-utils
Hi @PickleRick , i tried the query u suggested its working as expected. please find the below query. but my concern is we want to use this query as an alert, where condition as getperct >50  , putp... See more...
Hi @PickleRick , i tried the query u suggested its working as expected. please find the below query. but my concern is we want to use this query as an alert, where condition as getperct >50  , putperct >10 , deleteperct >80 trigger alert but when i give this 3 conditions its not working as expected, here alert should trigger even if one condition meets. |mstats sum(Transactions) as Transaction_count where index=metrics-logs application=login services IN(get, put, delete) span=1h by services |timechart span=1h values(Transaction_count) by services |autoregress get as old_get |autoregress get as old_put |autoregress get as old_delete |eval getperct=round(old_get/get*100,2) |eval putperct=round(old_put/put*100,2) |eval deleteperct=round(old_delete/delete*100,2) |table getperct putperct deleteperct  
It’s supposed to be based on the data @PickleRick 
You need to "carry over" value from one results row to another using autoregress command or streamstats. Autoregress is pretty straightforward. For example in this case | autoregress get as old_get... See more...
You need to "carry over" value from one results row to another using autoregress command or streamstats. Autoregress is pretty straightforward. For example in this case | autoregress get as old_get Streamstats seems a bit more complicated but can be a pretty powerful tool. Alternative to autoregress here would be | streamstats current=f window=1 values(get) as old_get One caveat to both those commands - they are applied in order of the returned events which by default is the reverse chronological order which means you'd be copying values from a newer result to the older one. If that's not what you want, you'll need to resort your results.
You're trying do dig out a thread from some 8 years ago. Most probably most of the participants are no longer actively following Answers. Your best bet would be to create a new thread and desciribe ... See more...
You're trying do dig out a thread from some 8 years ago. Most probably most of the participants are no longer actively following Answers. Your best bet would be to create a new thread and desciribe your problem there (possibly providing a link to this one if your case is similar.
Again - what dates are these numbers supposed to be?
I tried to convert it but i couldn't get the exact results. Are there any other ways to convert it @ITWhisperer ?
Thank You @Richfez  As a first need (and I should have said this in the opening), I was not asking to access them at all. I just want to know where they are, to backup them just like everything el... See more...
Thank You @Richfez  As a first need (and I should have said this in the opening), I was not asking to access them at all. I just want to know where they are, to backup them just like everything else in /etc/apps folder. But editing them could also be a need, ex: in case of db inputs info  loss of any kind.  And if it be the case, I guess to better edit them (at one's own risk) directly into the OS via a text editor since they are json. regards Altin
It may be complicated, but I think it's necessary.  Perhaps it could be better, though. Even if the SH did expand the query (and maybe it does) before sending to the peers, that's just a part of wha... See more...
It may be complicated, but I think it's necessary.  Perhaps it could be better, though. Even if the SH did expand the query (and maybe it does) before sending to the peers, that's just a part of what the bundle is used for.  Search-time field extractions and lookups done by the indexers make the query more efficient.
Thanks a lot @richgalloway  That behavior of SH seems to be unnecessarily complicated. Instead of sending all of those KO bundles to indexers, could not SH first expand SPL query (to resolve all of... See more...
Thanks a lot @richgalloway  That behavior of SH seems to be unnecessarily complicated. Instead of sending all of those KO bundles to indexers, could not SH first expand SPL query (to resolve all of the names/variables which are search-time) and then sent it to indexers ?  Thanks, Michal
The first example runs entirely on the Search Head where the lookup definition is available. The second example runs on the indexers, which apparently is unaware of the lookup definition.  Either th... See more...
The first example runs entirely on the Search Head where the lookup definition is available. The second example runs on the indexers, which apparently is unaware of the lookup definition.  Either the app defining the lookup is not installed on the indexers or the lookup file is blocked from the knowledge bundle ([replicationDenyList] in distsearch.conf).
Yes, you understand correctly.
Hi @marnall, soory I did not understand. But I tried to combine 2 queries to get combined output but I am not getting it. Can u pls share me the query 
Can you please explain a little bit more about this approach?