service-discovery

问题 We have a consul cluster of 3 servers and registering agent services on any of them via Rest Api. In UI, registrations of a server are visible on other servers as well. For e.g. registration on server A is visible on server B's UI (accessible by http://serverb:8500/). However when hitting server B via Rest Api, it only shows its own registrations and do not show server A registration. Server are started as Server A consul -server -ui bootstrap-expect=1 -node=ServerA -data-dir=D:\data -bind=11

问题 Running several instances of application with embedded hazelcast on PCF. My goal is to chain hazelcast members into cluster. For purpose of member discovery I am using hazelcast-eureka plugin . I am able to achieve member discovery using simple Eureka Server app, passing eureka URL to hazelcast-eureka plugin , using this example. Now I want to use PCF Registry Service instead of Eureka Server app. For that purpose I am using EurekaOneDiscoveryStrategyFactory with EurekaClient autowired which

问题 Running several instances of application with embedded hazelcast on PCF. My goal is to chain hazelcast members into cluster. For purpose of member discovery I am using hazelcast-eureka plugin . I am able to achieve member discovery using simple Eureka Server app, passing eureka URL to hazelcast-eureka plugin , using this example. Now I want to use PCF Registry Service instead of Eureka Server app. For that purpose I am using EurekaOneDiscoveryStrategyFactory with EurekaClient autowired which

问题 Running several instances of application with embedded hazelcast on PCF. My goal is to chain hazelcast members into cluster. For purpose of member discovery I am using hazelcast-eureka plugin . I am able to achieve member discovery using simple Eureka Server app, passing eureka URL to hazelcast-eureka plugin , using this example. Now I want to use PCF Registry Service instead of Eureka Server app. For that purpose I am using EurekaOneDiscoveryStrategyFactory with EurekaClient autowired which

问题 Running several instances of application with embedded hazelcast on PCF. My goal is to chain hazelcast members into cluster. For purpose of member discovery I am using hazelcast-eureka plugin . I am able to achieve member discovery using simple Eureka Server app, passing eureka URL to hazelcast-eureka plugin , using this example. Now I want to use PCF Registry Service instead of Eureka Server app. For that purpose I am using EurekaOneDiscoveryStrategyFactory with EurekaClient autowired which

问题 I'm currently having an issue with ECS Service Discovery and Route53 Auto Naming. I have added the Service Registry to the service and all the Hosted Zones records are being populated automatically. But I cannot seem to work out how to resolve the DNS SRV records with NGINX + ngx_upstream_resolveMK. # DNS RESOLVER resolver ns-x.awsdns-xx.com valid=10s; # UPSTREAMS upstream kibana { resolveMK servicediscovery.ecs service=kibana; } # HOST - kibana.example.com server { server_name kibana.example

问题 I'm currently having an issue with ECS Service Discovery and Route53 Auto Naming. I have added the Service Registry to the service and all the Hosted Zones records are being populated automatically. But I cannot seem to work out how to resolve the DNS SRV records with NGINX + ngx_upstream_resolveMK. # DNS RESOLVER resolver ns-x.awsdns-xx.com valid=10s; # UPSTREAMS upstream kibana { resolveMK servicediscovery.ecs service=kibana; } # HOST - kibana.example.com server { server_name kibana.example

问题 Prometheus allows me to dynamically load targets with file_sd_config from a .json file like this #prometheus.yaml - job_name: 'kube-metrics' file_sd_configs: - files: - 'targets.json' [ { "labels": { "job": "kube-metrics" }, "targets": [ "http://node1:8080", "http://node2:8080" ] } ] However my targets differ in the metrics_path and not the host (I want to scrape metrics for every kubernetes node on <kube-api-server>/api/v1/nodes/<node-name>/proxy/metrics/cadvisor ) but I can only set the

问题 Prometheus allows me to dynamically load targets with file_sd_config from a .json file like this #prometheus.yaml - job_name: 'kube-metrics' file_sd_configs: - files: - 'targets.json' [ { "labels": { "job": "kube-metrics" }, "targets": [ "http://node1:8080", "http://node2:8080" ] } ] However my targets differ in the metrics_path and not the host (I want to scrape metrics for every kubernetes node on <kube-api-server>/api/v1/nodes/<node-name>/proxy/metrics/cadvisor ) but I can only set the

问题 I want to connect clients to a server using ZeroMQ (java bindings, jzmq), but I need the TCP information badly, for example the TCP/IP address of a client request! The problem is, for being able to announce a service in the network I need to grab the TCP address of a request to be able to redirect clients to that service. The broker is a central "service registry" in that case. However, having ZeroMQ services on both sides, I do not see an option to retrieve that information. What I do now,