Kibana with routing awareness

Hello everyone, I just saw that ElasticSearch is able to route requests according to the attributes attached to the cluster nodes (Cluster-level shard allocation and routing settings | Elasticsearch Guide [7.7] | Elastic).

Is it possible to do the same with Kibana please? (I couldn't find anything that explained how to do it, so I guess not).

Thanks in advance, have a nice day!

Can you explain what exactly you mean by routing awareness in case of Kibana? As Kibana is mostly translating/forwarding Elasticsearch requests, it will benefit from this ES setting as well, as the requests issued by Kibana will respect these settings as well.

One related thing I can think of - it's a common pattern to have a coordinating Elasticsearch node running along with the Kibana instance on the same host and have Kibana only connected to this node. This way the full power of Elasticsearch routing logic can be leveraged.

1 Like

Hello and thank you for the quick response.

  • I am running ELK in a Kubernetes cluster deployed in multiple zones.
  • I am using attributes to route shards and queries in the cluster (a query launched in a coordinating node in a zone would run only in the same zone)
  • Multiple Kibana instances are running in the cluster (and they are all identical with the same config)

But I am facing this issue:

When Kibana is doing queries on ES, it doesn't know which coordinating node to use => and a Kibana in zone "A" can use a coordinating node in zone "B"

I don't know if it is clear, I can draw if needed :slight_smile:

I see 2 solutions here:

  • Kibana is routing aware (if it's possible)
  • I must use 2 Kibana with 2 different configurations

Ah, I see, thanks a lot for this explanation. To my knowledge Kibana doesn't offer any features around this. In this case the "routing awareness" would be setting elasticsearch.hosts to just the ES hosts in the same zone or a single dedicated coordinating node just for Kibana in that zone - Kubernetes would have to handle this additional complexity.

I have almost no Kubernetes knowledge (as you probably realized by now), but "topology aware hints" seem like a related feature: Topology Aware Hints | Kubernetes

Maybe you could also create a single pod which contains Kibana and Elasticsearch coordinating node together.

1 Like

"Topology Aware Hints" feature is very new and our cluster is not able to do it now but great idea !
One pod with ES+Kibana could be a good solution too.

I will try these solutions, thank you very much !!!

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.