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
Answered
Hi, We Are Storing Lots And Lots Of Scalars On Worker Resource And Queue Stats. This Totals To About 29 Gb. Is There Any Way Of Limiting The Amount Of Stats Being Logged? We Are Not Very Interested In The Worker Stats And 11G For Just Monitoring The Queue

Hi,
we are storing lots and lots of scalars on worker resource and queue stats.
This totals to about 29 gb. Is there any way of limiting the amount of stats being logged? We are not very interested in the worker stats and 11G for just monitoring the queues seems pretty extreme.

We are using the self-hosted server and elastisearch is really driving us nuts these days.
image

  
  
Posted 6 days ago
Votes Newest

Answers 2


Hi CostlyOstrich36 , yeah we figured as much. Is there a setting in the server that limits logging - or disables it completely?

  
  
Posted 5 days ago

Hi GiganticMole91 , I think you can delete those indices

  
  
Posted 6 days ago
55 Views
2 Answers
6 days ago
5 days ago
Tags