|classId:org.broadleafcommerce.core.order.domain.OrderImpl||Class with fully qualified name: org.broadleafcommerce.core.order.domain.OrderImpl|
|class:OrderImpl||All classes with the exact class name OrderImpl, (often only one match)|
|class.name:Order||All class which contain Order|
|method:addOrderItem||All methods across all classes with the exact name|
|methodId:"org.broadleafcommerce.core.order.domain.OrderImpl::addOrderItem"||All methods with the signature: class::method|
|method.name:Order||All methods across all classes containing Order|
|methodAccess:1||All public methods|
|thread:Thread-12||Only view what occurred on Thread-12 and ignore other threads|
|methodStack:/io.acme.BulkProcessor::main.*/||The use of '/', tell the query engine to treat the contents as a regular expression.
The query, shows all calls which occurred directly and indirectly beneath the main method.
Example source data for this field
To tap into the full power of Search, regular expressions can be used. Use forward slashes to indicate that you would like to use a regular expression. The reference for the regular expressions is at: Regular Expression Reference
Don't use the following filters for evergreen documentation. Object and Call ids change from log to log. If this dashboard is migrated to a new log, the use of these search terms will cause unexpected results.
|object:549||In the sequence diagram each object is preceded by a numerical identifier. This search enables a specific object to be examined. How it was created, all the methods that were invoked on it. If an object gets into a bad state, a search of this type enables the developer to determine the cause of the problem. In this case object: 549 is being examined.|
|classId:org.broadleafcommerce.core.order.domain.*||This search matches all classes which belong to the domain model. And is useful in this case, to see all methods invoked on the domain.|
|class:OrderImpl && method:set.*||
|class:OrderImpl && -method:/get[^IL].*/||