All Posts

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

All Posts

How to show the avg and their status in Flow Map viz connections. index=gc source="log" QUE_NAM="S*" | stats sum(eval(FINAL="MQ SUCCESS")) as good sum(eval(FINAL="CONN FAILED")) as errors sum(e... See more...
How to show the avg and their status in Flow Map viz connections. index=gc source="log" QUE_NAM="S*" | stats sum(eval(FINAL="MQ SUCCESS")) as good sum(eval(FINAL="CONN FAILED")) as errors sum(eval(FINAL="MEND FAIL")) as warn avg(QUE_DEP) as queueAvgDept by QUE_NAM | eval to=QUE_NAM, from="internal" | append [search index=es sourcetype=queue_monitor queue_name IN ("*Q","*R") | bucket _time span=10m | stats max(current_depth) as max_Depth avg(current_depth) as avg_Depth by _time queue_name queue_manager | eval to=queue_name, from="external"] For this query, i got below visualization and i need to connect between internal and external one ( highlighted in red color and how to show the avg count through the flow in between  external and name) Please help me out on this Thanks in advance!  
I believe it is due to my lack of understanding on how the indexers in an indexer cluster treat locally monitored data versus data forwarded to the indexer cluster. I mistakenly thought that locally ... See more...
I believe it is due to my lack of understanding on how the indexers in an indexer cluster treat locally monitored data versus data forwarded to the indexer cluster. I mistakenly thought that locally monitored logs on each indexer don't get treated the same way as logs that were forwarded to the indexer cluster. Thank you for pointing out on the infinite loop, I guess this was the issue when I tried to configure the indexer to forward locally monitored data to its own indexer cluster, which made them spew out alot of errors.  In that case it seems that I should just create an `inputs.conf` on the indexers and monitor whatever I want, as the indexers' logs would get indexed and subsequently replicated, if I'm understanding it correctly.  Thank you for your help!
What I tend to do to get all the results in email or Slack is to use stats as described here https://community.splunk.com/t5/Reporting/Using-result-fieldname-in-email-text-body-splunk-email-alert/m-... See more...
What I tend to do to get all the results in email or Slack is to use stats as described here https://community.splunk.com/t5/Reporting/Using-result-fieldname-in-email-text-body-splunk-email-alert/m-p/399711  
While most instance types should forward their logs to the indexers (using outputs.conf), indexers must not do so lest they cause an infinite loop.  By virtue of the fact the indexer is part of the c... See more...
While most instance types should forward their logs to the indexers (using outputs.conf), indexers must not do so lest they cause an infinite loop.  By virtue of the fact the indexer is part of the cluster, its logs go through the cluster. What problem are you trying to solve?
Run a btool to confirm, but it looks like you have a '[default]' stanza inadvertently assigning the incorrect sourcetype. I'd check for the following in /opt/splunk/etc/apps/splunk_ta_onelogin/local/... See more...
Run a btool to confirm, but it looks like you have a '[default]' stanza inadvertently assigning the incorrect sourcetype. I'd check for the following in /opt/splunk/etc/apps/splunk_ta_onelogin/local/inputs.conf: [default] sourcetype=onelogin:user  
I just set up a free Duo account and installed and configured the add-on without issues. The only other things I can suggest are 1) verify your Splunk instance's public egress address is in the Admin... See more...
I just set up a free Duo account and installed and configured the add-on without issues. The only other things I can suggest are 1) verify your Splunk instance's public egress address is in the Admin API application's "Networks for API access" list, 2) verify any intervening host or network firewalls or transparent proxies allow connectivity to your API hostname, and 3) verify your Splunk host can connect to your API hostname using openssl: $SPLUNK_HOME/bin/splunk cmd openssl s_client -connect api-xxx.duosecurity.com:443 The Duo Admin API Python client used by the add-on supports HTTP proxies, but Duo didn't include proxy support in the modular input. If you need this feature, you'll need to request it from Duo.
I'm trying to create a search where I take a small list of IPs from sourcetype A and compare them against a larger set of IPs in sourcetype B.  I will then make a table using fields from sourcetype B... See more...
I'm trying to create a search where I take a small list of IPs from sourcetype A and compare them against a larger set of IPs in sourcetype B.  I will then make a table using fields from sourcetype B that do not exist in sourcetype A to create a more detailed look of the events involving the IP. Is there a way to do this without using a lookup table? index=paloalto (sourcetype=sourcetype_B OR sourcetype=sourcetype_A) | eval small_tmp=case(log_type="CORRELATION", src_ip) | eval large_tmp=case(log_type!="CORRELATION", src_ip) | where match(small_tmp, large_tmp) | table field A, field B, field C  
Hi @ririzk, _ssl.c is part of Python, not Splunk. A quick look at a non-specific version of the _ssl.c source code shows that error is returned when a connection is closed unexpectedly. You should c... See more...
Hi @ririzk, _ssl.c is part of Python, not Splunk. A quick look at a non-specific version of the _ssl.c source code shows that error is returned when a connection is closed unexpectedly. You should contact Duo support for more detail.
Hi @newbie77, If an instance of Field1=Start is always the earliest event by uid and Field2=Finish is always the latest event by uid, you can use the stats range() function: | stats range(_time) ... See more...
Hi @newbie77, If an instance of Field1=Start is always the earliest event by uid and Field2=Finish is always the latest event by uid, you can use the stats range() function: | stats range(_time) as duration by uid Otherwise, use the stats min() and max() or earliest() and latest() functions with an eval expression: | stats min(eval(case(Field1=="Start", _time))) as start_time max(eval(case(Field2=="Finish"))) as finish_time by uid | eval duration=finish_time-start_time
Hi Thanks for the feedback. We can have a lot of row, I will have a look at the other app cheers Rob
This is very old, but did anyone ever figure this out? We've had a ticket open for a month now about this exact issue and have chased down every error message and possible conf change. If anyone out ... See more...
This is very old, but did anyone ever figure this out? We've had a ticket open for a month now about this exact issue and have chased down every error message and possible conf change. If anyone out there has a possible solution or suggestion for this that would be awesome!    Thanks everyone!!
I've three search in OR for ex  "order success" "order failed" "offer success"  based on the above 3 statement I can perform search but I want to show the result in as pie chart at per hour basis
I have the following setup with Indexer Discovery + Indexer Cluster + Search Head Cluster: - Deployment Server - 3 X Indexer + Cluster Manager (Indexer Cluster) - Search Head Deployer + Search Hea... See more...
I have the following setup with Indexer Discovery + Indexer Cluster + Search Head Cluster: - Deployment Server - 3 X Indexer + Cluster Manager (Indexer Cluster) - Search Head Deployer + Search Head (Set-up as part of a SHC for possible future scaling up)   For forwarding logs from Cluster Manager, I referred to: https://docs.splunk.com/Documentation/Splunk/latest/Indexer/Forwardmanagerdata For forwarding logs from Search Head Cluster nodes, I referred to: https://docs.splunk.com/Documentation/Splunk/latest/DistSearch/Forwardsearchheaddata I believe forwarding logs from the Deployment Server should be similar to the above.   For indexers belonging to an indexer cluster, I have considered the following: 1. Install UF in each indexer to monitor & forward logs to the indexer cluster (via indexer discovery) 2. Just monitor logs locally and allow each indexer to index its own local logs (without going through the indexer cluster) 3. Configure the indexer to forward the locally monitored logs without indexing, to the indexer cluster. I am not sure if is necessary to ensure that it does not index the same data twice. Unsure on how this would play out. Option 2 seems to be the easiest to achieve, but ideally I would like all logs to go through the indexer cluster for indexing. What should be the best practice for forwarding logs from indexers that are part of the indexer cluster?  
Forgot to say, thank you everyone for the assist.
What I need is for the line that starts with Start: to be the break after line. Start: 14-Jun-24 07:55:05, End: 14-Jun-24 07:56:35, Mode: 5, Status: [-11059] No Good Data For Calculation", Break af... See more...
What I need is for the line that starts with Start: to be the break after line. Start: 14-Jun-24 07:55:05, End: 14-Jun-24 07:56:35, Mode: 5, Status: [-11059] No Good Data For Calculation", Break after the ", but since there are a few ",  and not only the ", how do I get it to break at that last comma?
@gcusello Please can you help? How can i prevent truncation of the legend on a classic Splunk dashboard? The output has an ellipsis in the middle of my Legend, but i want to show the full text on th... See more...
@gcusello Please can you help? How can i prevent truncation of the legend on a classic Splunk dashboard? The output has an ellipsis in the middle of my Legend, but i want to show the full text on the legend. See my query below: index=$ss_name$_$nyName_tok$_ sourcetype=plt (Instrument="ZT2" OR Instrument="XY2" OR Instrument="P4") | rex field=Instrument "(Calculated)\.(?<tag>.+)$$" | timechart span=$span$ max(ValueEng) by tag     Thanks
Field1=Start Field2=Finish Field1 and Field2 have multiple events with values Start and Finish for a given uid respectively. I want to pick earliest event for Fiield1 and latest event for Field2 a... See more...
Field1=Start Field2=Finish Field1 and Field2 have multiple events with values Start and Finish for a given uid respectively. I want to pick earliest event for Fiield1 and latest event for Field2 and find the duration. Field3=uid which is the common field. ….| transaction uid startswith=“Start” ends with=“Finish” | stats avg(duration) It’s not giving the expected result.
Hello, Yes I have been able to find a good way to do it. I wanted to write a solution post for this topic but I never had chance. I’ll do it providing all the steps and config. To summarize the way ... See more...
Hello, Yes I have been able to find a good way to do it. I wanted to write a solution post for this topic but I never had chance. I’ll do it providing all the steps and config. To summarize the way I found is: 1- in Azure AKS in diagnostic settings (if I remember well) you can decide to spool the logs you need into a Storage Account or a Streaming Service. If you don’t need real time go with Storage Account that is cheaper.  2- you then read with Microsoft TA from that Storage Account every 5 minutes 3- you set-up a policy to cancel data older than 7 days from your Storage Account. Retention policy can be adjusted as per your preference, but here act mostly like a buffer. In this way the cost will be under control. Also, about the REST API billing I didn’t see much of a difference honestly. 4- the Microsoft TA modular input seems having a bug. Basically scheduling it every 5 minutes after several hours it stopped working. As a workaround I downloaded an app with an SPL command that allows you to reload the endpoint you want. I embedded it into a scheduled search that run every 5 minutes, keeping the modular input every hour. In this way it is the scheduled report that trigger the data download. Schedule frequency need to be higher than the time it takes to download your data from the Storage Account and then parse them 5- once you download the data you then have to parse removing the unwanted data. Unfortunately it is a JSON into another JSON, and you need the nested one. I did this for AKS audit but probably can be easily adjusted for other typology of logs As soon as I have some time I will provide the config as well. Best Regards, Edoardo
This would be helpful, but where do i place this in the below query? index=$ss_name$_$nyName_tok$_ sourcetype=plt (Instrument="ZT2" OR Instrument="XY2" OR Instrument="P4") | rex field=Instrument ... See more...
This would be helpful, but where do i place this in the below query? index=$ss_name$_$nyName_tok$_ sourcetype=plt (Instrument="ZT2" OR Instrument="XY2" OR Instrument="P4") | rex field=Instrument "(Calculated)\.(?<tag>.+)$$" | timechart span=$span$ max(ValueEng) by tag
There are charting options you could try but with long legends this still may not be enough charting.legend.labelStyle.overflowMode (ellipsisEnd | ellipsisMiddle | ellipsisNone | ellipsisStart) ... See more...
There are charting options you could try but with long legends this still may not be enough charting.legend.labelStyle.overflowMode (ellipsisEnd | ellipsisMiddle | ellipsisNone | ellipsisStart) ellipsisMiddle Determines how to display labels that overflow layout bounds by replacing elided text with an ellipsis (...). ellipsisStart: Elides text at the start. ellipsisMiddle: Elides text in the middle of the line. ellipsisEnd: Elides text at the layout boundary. ellipsisNone: Disables text truncation entirely.