"stat_prefix": "inbound_0.0.0.0_9080",
                        "route_config": {
                          "name": "inbound-vip|9080|http|details.default.svc.cluster.local",
                          "virtual_hosts": [
                            {
                              "name": "inbound|http|9080",
                              "domains": [

                        "stat_prefix": "inbound_0.0.0.0_9999",
                        "route_config": {
                          "name": "inbound-vip|9080|http|details.default.svc.cluster.local",
                          "virtual_hosts": [
                            {
                              "name": "inbound|http|9080",
                              "domains": [

                        "stat_prefix": "inbound_0.0.0.0_8000",
                        "route_config": {
                          "name": "inbound-vip|8000|http|httpbin.default.svc.cluster.local",
                          "virtual_hosts": [
                            {
                              "name": "inbound|http|8000",
                              "domains": [

	filter := istio_envoy_configdump.ClusterFilter{
		FQDN: host.Name(svcHost),
		Port: int(port),
		// Although we want inbound traffic, ask for outbound traffic, as the DR is
		// not associated with the inbound traffic.
		Direction: model.TrafficDirectionOutbound,
	}

	dump, err := cd.GetClusterConfigDump()
	if err != nil {
		return "", err
	}

                "type": "prometheus",
                "uid": "${datasource}"
              },
              "expr": "pilot_conflict_inbound_listener{app=\"istiod\"}",
              "format": "time_series",
              "hide": false,
              "intervalFactor": 1,
              "legendFormat": "Inbound Listeners",
              "refId": "B"
            },
            {
              "datasource": {

_2019-09-10_

 *  Fix: Don't lose HTTP/2 flow control bytes when incoming data races with a stream close. If this
    happened enough then eventually the connection would stall.

 *  Fix: Acknowledge and apply inbound HTTP/2 settings atomically. Previously we had a race where we
    could use new flow control capacity before acknowledging it, causing strict HTTP/2 servers to
    fail the call.

                },
                {
                    "endpoint_config": {
                        "@type": "type.googleapis.com/envoy.config.endpoint.v3.ClusterLoadAssignment",
                        "cluster_name": "inbound|9080||",
                        "policy": {
                            "overprovisioning_factor": 140
                        }
                    }
                },
                {