Typical ranges in marvel metrics


(T Vinod Gupta) #1

hi,
i just installed marvel on my production cluster to try it out and i have
bunch of questions. can someone help?

  1. for the most important graphs, like jvm memory, load, query rate, etc
    what should be the ideal range or high water mark? i mean if i were to
    determine if i need to add more nodes, what should be my criteria?

  2. what does load(1M) mean? i couldn't find a definition.

  3. where is search latency metric? that is most important to me. also
    metrics on slow queries.

  4. i have bunch of background processes that are doing queries and then
    updating documents. but i care more about user search latency. is there a
    way to create distinction by source IP or something (all user queries will
    come from web server nodes)

thanks

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAHau4yuSrFT7FwLrxFAyFVUtGtpiJcrtkOGoF8m_peg138sDfw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


(system) #2