Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Unanswered
Hello, We Have Noticed That Debug Images Takes Way Too Long To Load 6 To 8 Seconds When Requesting Events.Debug_Images We Also Notice That The Returned Object Is Quite Heavy, About 2-3 Mb, I Think It Contains A Lot Of Unnecessary Info We Also Have 20 Mill


@<1855782479961526272:profile|CleanBee5> , in that case you should beef up the resources running the apiserver.

In the end of the day, this 2-3mb payload basically contains all the events (including debug samples metadata + links) of thousands of iterations. You could modify FE code to load a smaller range of iterations or remove some metadata (the metadata should be minimal, such as iteration and name of the metric)

Additionally, I believe the enterprise version supports rolling indexes.

  
  
Posted one month ago
38 Views
0 Answers
one month ago
one month ago