Hello,
I have an external script which sends queries to Splunk via API. My script sends 10 identical query same time. In jobs inspector, I see them as 10 different inputs. I assume that because they are run in parallel, they consume search head resources discretely.
The question is: if there is any mechanism in Splunk which could recognize that identical queries were sent to Search Head and optimize queries execution?
↧