There is no in-built way but if you are willing to create a custom query component then it should be easy to mandate that every query must have a tag parameter by throwing an exception otherwise. Any query param you pass to a distributed query request should be propagated to all query nodes as well.
On Wed, Aug 9, 2017 at 8:58 AM, suresh pendap <sureshfors...@gmail.com> wrote: > Hi, > We have found that application teams often fire ad-hoc queries, some of > these are very expensive queries and can bring the solr cluster down. Some > times they just build custom scripts which does some offline analytics by > firing expensive queries, the solr cluster was originally not sized for > executing such queries. > > When an issue happens we identify from the solr logs the query which is > taking long time. But some times we do not even know who is firing these > queries and hence it takes a while to stop them. > > We would like be able to identify the source of the solr queries. > > Is there a way to tag the solr queries? > Can we associate some tags or query identifier with the query? > These tags should be made mandatory without which the solr query should > fail? > > We would like to build a custom component which logs the query, the query > identifier (the tag which user provides) and the IP address of the client > machine which fired this query. > > > Thanks > Suresh -- Regards, Shalin Shekhar Mangar.
