About AntonyPriwin

AntonyPriwin · ‎12-08-2021

Hi, Added intermediate cert but getting below error curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to xyz.com:443 Thanks in advance

AntonyPriwin · ‎12-02-2021

Hi We have a situation, while trying to post a request to a external api from java script, we are getting timeout error. While trying to hit the same url through curl we are getting the below ssl cert error. "curl: (60) SSL certificate problem: unable to get local issuer certificate More details here: https://curl.haxx.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the web page mentioned above. " I have attached the error snip and the related JS here. JS snippet: const userAction = async (pid) => { const url='https://xyz.com:443/PID?ppid='+pid; const response = await fetch(url,{ method: 'POST',mode: 'cors'}) .then(response => console.log(response)) .then(xmlString => console.log($.parseXML(xmlString)) ) .catch(error => console.log(error)) has anyone come across the above issue, any help is appreciated Thanks.

AntonyPriwin · ‎10-13-2020

Hello @gcusello , Hope you are doing good! We tried the same by populating a lookup and querying from the lookup, as for a limited time range(e.g; last 5 days) we have nearly 6000 events flowing into the dropdown. For each click we need to wait for around 8 sec for the dropdown to show up. is there any other way to load the dropdown faster. Thanks, Antony

AntonyPriwin · ‎03-03-2016

@jrodman Thanks for your response. Our requirement is to identify the number of concurrent scheduled searches/alerts ran at a given point of time. We were in an opinion to count them based on the AlertNotifierWorker thread, however it seems of no help. Please let us know how do we approach for the same.

AntonyPriwin · ‎02-24-2016

Hi All, Need some info regarding thread_id in scheduler.log and how it is being assigned. Sample Events 1: 02-03-2016 08:40:01.341 +0000 INFO SavedSplunker - savedsearch_id="admin;search;SS_1minute_23", user="admin", app="search", savedsearch_name="SS_1minute_23", status=success, digest_mode=1, scheduled_time=1454488800, dispatch_time=1454488801, run_time=0.178, result_count=1, alert_actions="", sid="scheduler_adminsearch_RMD5fe320a1798d45e4e_at_1454488800_189", suppressed=0, thread_id="AlertNotifierWorker-1" 02-03-2016 08:40:01.340 +0000 INFO SavedSplunker - savedsearch_id="admin;search;SS_test_threadid_3", user="admin", app="search", savedsearch_name="SS_test_threadid_3", status=success, digest_mode=1, scheduled_time=1454488800, dispatch_time=1454488801, run_time=0.156, result_count=1, alert_actions="", sid="scheduler_adminsearch_RMD506c18cc48c92c389_at_1454488800_190", suppressed=0, thread_id="AlertNotifierWorker-0" Sample Events 2: 02-03-2016 08:59:01.219 +0000 INFO SavedSplunker - savedsearch_id="admin;search;SS_1minute_23", user="admin", app="search", savedsearch_name="SS_1minute_23", status=success, digest_mode=1, scheduled_time=1454489940, dispatch_time=1454489941, run_time=0.089, result_count=1, alert_actions="", sid="scheduler_adminsearch_RMD5fe320a1798d45e4e_at_1454489940_239", suppressed=0, thread_id="AlertNotifierWorker-0" 02-03-2016 08:59:01.211 +0000 INFO SavedSplunker - savedsearch_id="admin;search;SS_23", user="admin", app="search", savedsearch_name="SS_23", status=success, digest_mode=1, scheduled_time=1454489940, dispatch_time=1454489941, run_time=0.087, result_count=1, alert_actions="", sid="scheduler_adminsearch_RMD510bfa07112c26c31_at_1454489940_238", suppressed=0, thread_id="AlertNotifierWorker-0" There are 14 thread_ids in the name of Alertnotifierworker-0 , Alertnotifierworker-1, Alertnotifierworker-2 … Alertnotifierworker-13. We have seen scenarios like the scheduled_time and dispatch_time of a savedsearch/alert is the same, thread_id is getting incremented. (E.g: Alertnotifierworker-0, Alertnotifierworker-1, Alertnotifierworker-2 … Alertnotifierworker-13) However, in some cases, we have only one thread_id for all these savedsearch/alerts with same scheduled_time (E.g: Alertnotifierworker-0) When would Splunk assign same thread_id and different thread_id for scheduled searches/alerts?

Posts	5
Solutions	0
Karma Given	4
Karma Received	0
Member Since	‎02-24-2016

Online Status	Offline
Date Last Visited	‎12-08-2021 12:48 PM

SSL Certificate issue

How does Splunk assign thread_id for scheduled sea...

Re: SSL Certificate issue

SSL Certificate issue

Re: Drop-down selection is slow with large data

Re: How does Splunk assign thread_id for scheduled...

How does Splunk assign thread_id for scheduled sea...