Asymmetry between Type->Find and Type->Exclude
Each event provides a drop down under "Type" that includes "Find" and "Exclude". When selecting "Find", the current behavior is to replace the existing query with something like "@EventType = 0xED5F661B". When selecting "Exclude", the current behavior is to add to the existing new signal (or a new new signal if there wasn't one before) a filter containing something like "Not(@EventType = 0xED5F661B)".
This is not what I expected to happen. I expected either that both would add their respective query text to the same location: either the current query or the current (or new) new signal, but not one of each.
Why is the current behavior the way it is?
I would prefer that both modified the current query instead of the current/new new signal. I have two reasons for this. First, there is an easy way to make the current query into a filter in the current/new new signal but not the other way around. Second, the current query is reflected in the URL, which means that duplicating the browser tab also duplicates the query. In contrast to this, filters in a new signal are not copied to a duplicated browser tab.
On a related note. I would prefer if selecting "Find" would add to the existing query instead of replacing it.
Posted by Tyson Williams over 3 years ago