-
Notifications
You must be signed in to change notification settings - Fork 1
Provide health-measures per index #2
Comments
We can add this, but I likely would not enable this by default, but rather add a switch to the plugin-configuration to only fetch and provide these measures when the user decides that they are useful for him/her. Reasons are:
|
We have 42 indices as of now. Is that a lot? |
No, that is not a lot, Elasticsearch can easily handle hundreds, maybe up to a few thousand, depending on complexity of mappings. But I am speaking for the general case in the plugin where we need to avoid disrupting other peoples environments by simply adding this in a too naive way. With a switch you can easily enable it for you and everybody else who wants this level of detail can as well, but it will not affect others immediately who do not need it. |
Hi Dominik, You are right. Switch is a brilliant idea. People who need it can switch it on. I am not a coding person. Will you be able to work on this and add a switch? Thank you, |
I'll try to squeeze it in eventually when I revisit the plugin for things that we need ourselves, but I cannot work on this just now... |
Sure, thanks a lot Dominik. Appreciate it. |
Migrated from #1, originally submitted by user @keertisurapaneni
I have a request for the ES fastpack you are developing. Is there a way you can create measures for different indices (like index name, doc count, delete count, health, status, pri, rep, store size, etc..)
The below command will pull those values:
curl -XGET http://chdd-es01.cps.local:9200/_cat/indices?v
That way we can create a dashbord for index health. The dashboard can have tables for each measure (doc count, delete count, health, etc..)
For ex: We can have a dashlet table for measure 'document count' which would have splittings by index name.
below is the command to extract doc count for each index:
curl -XGET http://chdd-es01.cps.local:9200/_cat/indices?v | awk "{print $3, $6}"
example output:
index docs.count
unilog_04 99377
cps_documents 495303
customer_alias-20160331 160917
The text was updated successfully, but these errors were encountered: