Optimizing WEF event queries

Question

Hi team

We’ve been seeing a technical issue where the WEF collector server runs into serious delays while processing events. The cause seems to be that many client subscriptions are written with un‑indexed XPath queries, which put a heavy load on client CPUs and slow down the entire pipeline. Because the XML query structures aren’t optimized, the system spends too much time parsing and filtering events instead of forwarding them efficiently. This mismatch between query design and system capacity is creating bottlenecks that impact performance across the environment.

We want to ask how to restructure or optimize the WEF event query XML so that client CPU overhead is reduced. We’re looking for best practices in indexing, query simplification, or alternative approaches that can help align subscription design with system performance

Many thanks