Hello Miki ,
Can you try
index.search.slowlog.threshold.query.info: 0s
alone and see
Thanks
Vineeth
On Sat, Apr 19, 2014 at 8:33 PM, miki haiat <[email protected]> wrote:
> that an excellent approach ,
> i edit the the configuration file to this and restart the server
>
>
> # Shard level query and fetch threshold logging.
>
>
> index.search.slowlog.threshold.query.warn: 10s
> index.search.slowlog.threshold.query.info: 5s
> index.search.slowlog.threshold.query.debug: 2s
> index.search.slowlog.threshold.query.trace: 500ms
>
>
> index.search.slowlog.threshold.fetch.warn: 1s
> index.search.slowlog.threshold.fetch.info: 800ms
> index.search.slowlog.threshold.fetch.debug: 500ms
> index.search.slowlog.threshold.fetch.trace: 200ms
>
>
> index.indexing.slowlog.threshold.index.warn: 10s
> index.indexing.slowlog.threshold.index.info: 5s
> index.indexing.slowlog.threshold.index.debug: 2s
> index.indexing.slowlog.threshold.index.trace: 500ms
>
> i was expecting the data to written in _index_indexing_slowlog.log
>
> but nothing happened , what im missing ?
>
> thanks miki
>
>
> On Saturday, April 19, 2014 2:31:44 PM UTC+3, vineeth mohan wrote:
>
>> Hello Miki ,
>>
>> I believe the right approach would be to enable slow log -
>> http://www.elasticsearch.org/guide/en/elasticsearch/
>> reference/current/index-modules-slowlog.html#search-slow-log
>>
>> Thanks
>> Vineeth
>>
>>
>> On Sat, Apr 19, 2014 at 4:21 PM, miki haiat <[email protected]> wrote:
>>
>>>
>>> Hi,
>>> im using elastic search on a local node configuration,
>>> also im using a client (elastic4s) in order to index the data ,
>>> so i want to see that the client is actually sending to the server .
>>> i configure Wireshark to capture like that (tcp.port >= 9200 and
>>> tcp.port <= 9300)
>>> but i cant figure out which data was sent to the ES Server
>>> can you recommend a better Wireshark filter OR another tool in order to
>>> catch ES requests .
>>>
>>> thanks
>>>
>>> miki
>>>
>>> --
>>> 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 [email protected].
>>>
>>> To view this discussion on the web visit https://groups.google.com/d/
>>> msgid/elasticsearch/a2a5717a-b6c1-4826-a36e-38ff51d7f755%
>>> 40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/a2a5717a-b6c1-4826-a36e-38ff51d7f755%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> 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 [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elasticsearch/e5aa6d22-781e-44d4-afef-473b9a6c2c81%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/e5aa6d22-781e-44d4-afef-473b9a6c2c81%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAGdPd5%3DXieB83ytrLOjS8eU3RG5QyZzKGGi3Ja5VyNA%3D1_f9AA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
