Thanks for the reply.
I have tried the Istio setup in 2 ways by helm and by auto istio-demo.yml none worked for metrics for cutom zuul gateway.
I think the problem might be I am calling the custom gateway by public IP may be the requests are not flowing through istio-proxy(sidecar) and even service to service communications may not be going through proxy after that.
Even when I call through istio-gateway I am getting metrics till next downstream service call but the call to the dependent service metrics are not getting reflected this says I am not calling the istio-proxy(sidecar) corretly but I am getting responses from service may be the requests are not going through proxy.
Below are the answers to questions u asked
*Yes, I have custom gateway as zuul, I am using kube DNS service name like ‘product:{port}’ or name like ‘product.default.svc.cluster.local:{port}’ as base url. Does this mean I am communicating to sidecar?
*Injection of the sidecar in 2 ways one by ‘istioctl kube-inject -f samples/sleep/sleep.yaml | kubectl apply -f -’ while doing istio-demo.yml istio setup and the other by ‘istio-ingestion=enabled’ for default namespace while using helm.
*I have tried 2 types of setup too one is by crds and Istio-demo.yaml to install istio and the version is 1.0.5 refferred ‘https://istio.io/docs/setup/kubernetes/quick-start/’ and other by helm by enabling gatling, service graph, tracing using "–set for helm template command.
My config:
kind: Deployment
apiVersion: extensions/v1beta1
metadata:
name: rc-sample
namespace: default
labels:
app: rc-sample
annotations:
deployment.kubernetes.io/revision: '1'
spec:
replicas: 1
selector:
matchLabels:
app: rc-sample
template:
metadata:
name: rc-sample
labels:
app: rc-sample
version: v1
spec:
containers:
- name: rc-sample
image: gcr.io/cognitive-genie-63754/mesh_rc_sample:latest
env:
- name: eureka_instance_hostname
value: 'rc-sample'
envFrom:
- configMapRef:
name: mesh-config
resources: {}
imagePullPolicy: Always
securityContext:
privileged: false
ports:
- containerPort: 3333
restartPolicy: Always
terminationGracePeriodSeconds: 30
dnsPolicy: ClusterFirst
securityContext: {}
imagePullSecrets:
- name: acr-mesh
schedulerName: default-scheduler
strategy:
type: Recreate
---
apiVersion: autoscaling/v1
kind: HorizontalPodAutoscaler
metadata:
name: rc-sample
namespace: default
spec:
scaleTargetRef:
apiVersion: apps/v1beta1
kind: Deployment
name: rc-sample
minReplicas: 1
maxReplicas: 1
targetCPUUtilizationPercentage: 80
---
kind: Service
apiVersion: v1
metadata:
name: rc-sample
namespace: default
labels:
app: rc-sample
spec:
ports:
- name: tcp-6050-6050-rc-sample
protocol: TCP
port: 6050
targetPort: 6050
selector:
app: rc-sample
type: ClusterIP
sessionAffinity: None
---
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
name: config-gateway
spec:
selector:
istio: ingressgateway
servers:
- port:
number: 80
name: http
protocol: HTTP
hosts:
- "*"
---
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
name: rcsampleroute
spec:
hosts:
- "*"
gateways:
- config-gateway
http:
- match:
- uri:
prefix: /sample-service
route:
- destination:
host: rc-sample
port:
number: 6050
---
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
name: rc-sample
spec:
hosts:
- rc-sample
http:
- route:
- destination:
host: rc-sample
- I tried “Missing Metrics” everything looks fine. I am able to generate new metrics but response and request attributes are not reflecting when service gets called through zuul gateway. Below is the error which i get when i add custom metric.
“[libprotobuf ERROR src/istio/mixerclient/report_batch.cc:83] Mixer Report failed with: UNKNOWN:2 errors occurred:%0A%0A* evaluation failed at [newlog.logentry.istio-system]‘Timestamp’: ‘lookup failed: ‘request.time’’%0A* failed to report all values: 1 error occurred:%0A%0A* could not find metric info from adapter config for doublerequestcount.metric.default”
*How can i validate this or implement this " You should see automatic metric generation for any istio-proxy sidecar properly configured to point to istio-telemetry . In your case, this should be in front of your services."
- How can I validate traffic hitting sidecar since I am not able to see any log changes in istio-proxy even when metrics are reflected when calls are made through istio-ingess gateway?
There is one more problem which I observed in both the setup is servicegraph is not coming up. it just says starting at 8088 in logs that is it.