Muhammad Salman Shaikh

``` ubuntu@kube-master-1:~/jaeger-kubernetes$ kubectl logs jaeger-query-676d6658d6-cdqs9 -f {"level":"info","ts":1548655820.6596537,"caller":"healthcheck/handler.go:99","msg":"Health Check server started","http-port":16687,"status":"unavailable"} {"level":"info","ts":1548655820.7135236,"caller":"query/main.go:184","msg":"Archive storage not created","reason":"Archive storage not supported"} {"level":"info","ts":1548655821.1784363,"caller":"query/main.go:132","msg":"Registering metrics handler with HTTP server","route":"/metrics"} {"level":"info","ts":1548655821.1785743,"caller":"healthcheck/handler.go:133","msg":"Health Check state change","status":"ready"} {"level":"info","ts":1548655821.1786165,"caller":"query/main.go:141","msg":"Starting HTTP server","port":16686}...

I don't have agent running along with query. Are you suggesting to setup agent along with query. I do have jaeger-agent setup along with application sending trace to agent which...

Configmap for jaeger to connect to elasticsearch running on separate VM as: ``` apiVersion: v1 kind: ConfigMap metadata: name: jaeger-configuration labels: app: jaeger jaeger-infra: configuration data: span-storage-type: elasticsearch collector: |...

Deployed hotrod with sidecar as jaeger-agent ``` apiVersion: v1 kind: Service metadata: name: example-hotrod spec: ports: - name: ui port: 8080 targetPort: 8080 - name: interface1 port: 8081 targetPort: 8081...

As long as the agent with specific IP/Port is reachable from the Pod then yes you can configure it.

Which ENV_VAR? Can you please clarify and elaborate a bit more?

We would like to generate the Port Probe Alerts for some testing and needs a way to be able to generate them as and when we want to run our...