Would like to use Hystrix with many independent deployments that have the same ApplicationContext.id, but this breaks the HystrixDashboard

In a nutshell, using Docker, for example, where our name, profile(s), and port are the same, when we try to use Hystrix & aggregate data through Turbine to display it to a Hystrix Dashboard, we get bad results due to the code in org.springframework.cloud.netflix.hystrix.stream.HystrixStreamTask

private void addServiceData(JsonGenerator json, ServiceInstance localService)
        throws IOException {
    json.writeObjectFieldStart("origin");
    json.writeStringField("host", localService.getHost());
    json.writeNumberField("port", localService.getPort());
    json.writeStringField("serviceId", localService.getServiceId());
    if (this.properties.isSendId()) {
        json.writeStringField("id", this.context.getId());
    }
    json.writeEndObject();
}

The ‘id’ field here ends up being the same for all deployments, yet it carries differing information payloads, and that messes up the aggration along the bus into Turbine & the Hystrix Dashboard.

Might I suggest making that a combination of the other three fields?

localService.serviceId:localService.Host:localService.Port?

Or, perhaps have a property that could be dropped in?

[spencergibb]

Sorry, the property name changed when we moved to spring-cloud-stream. hystrix.stream.queue.send-id=false.

[TabberGit]

Perfect. Thank you.

Yes, close away.