You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 6, 2023. It is now read-only.
We have a scenario, that consists of 2 Elasticsearch(ES) master nodes deployed on Kubernetes and exposed as 'NodePort' service. So, that we can access the ES service using both the node ip/port and can also use multiple node addresses for Logstash configuration as an example.
In such case, we should be able to use both node ip/port as publishHost and publishPort (as a failover mechanism).
I think it will be a required feature in Weblogic exporter unless there is already a way to do this.
Also, in cases, when the ES service is exposed via Loadbalancer, Weblogic exporter should also support the configuration of loadbalancer URL instead of specifying host/port of the ES service.
The text was updated successfully, but these errors were encountered:
We have a scenario, that consists of 2 Elasticsearch(ES) master nodes deployed on Kubernetes and exposed as 'NodePort' service. So, that we can access the ES service using both the node ip/port and can also use multiple node addresses for Logstash configuration as an example.
In such case, we should be able to use both node ip/port as publishHost and publishPort (as a failover mechanism).
I think it will be a required feature in Weblogic exporter unless there is already a way to do this.
Also, in cases, when the ES service is exposed via Loadbalancer, Weblogic exporter should also support the configuration of loadbalancer URL instead of specifying host/port of the ES service.
The text was updated successfully, but these errors were encountered: