Grafana link not working about jmeter-operator HOT 7 CLOSED

Hi,
Any update on the same? I re tried the entire process but seems like the grafana peice is not working. Any ideas to troubleshoot would help. Thanks!!

from jmeter-operator.

Hi,

1.) You can't access the grafana via the jmeter-service, they are separate things. Grafana has it's own service, the default service type for the Grafana is NodePort, so you should be able to connect to it using the minikube VM physical IP but I noticed you are using a Load balancer service type, minikube has a special way of accessing your application within a kubernetes cluster, I suggest that you check the minikube documentation minikube_service_doc on how to properly expose your service. Alternatively you should be able to use kubectl forwarding or proxy.

2.) The jmeter-operator can be deployed on any public cloud, with this you will be able to use a globally available load balancer to access your application. Don't forget to secure your services when you expose them to the internet. You can make use of an ingress controller with SSL certificates and authentication, but this is beyond the scope of this project (exposing services can be done several ways, this is left to the end user).

3.) Having multiple teams to carry out tests requires some planning. Note that you can't carry out simultaneous tests. I suggest that each team should create their jmeter deployment in a separate namespace or they do tests in turns. This is entirely up to you.

from jmeter-operator.

HI,
Thank you for your response. So i did check the minikube doc and followed the steps but the grafana dashboard is still not working for me. I think i am missing a step here. Below is the output for the same. I tried accessing via the browser both the nodeport IP and minkube ip but dont see it working. Meanwhile i am trying the kubectl port forward and hoping that works.

Kapishs-MacBook-Air:jmeter-operator kapishjoshi$ kubectl get services
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
hello-minikube NodePort 10.105.193.221 8080:31995/TCP 25m
kubernetes ClusterIP 10.96.0.1 443/TCP 40m
Kapishs-MacBook-Air:jmeter-operator kapishjoshi$ minikube ip
192.168.99.105
s-MacBook-Air:jmeter-operator kapishjoshi$ kubectl expose deployment hello-minikube --type=LoadBalancer --port=8080
Error from server (AlreadyExists): services "hello-minikube" already exists
s-MacBook-Air:jmeter-operator kapishjoshi$ minikube service hello-minikube
🎉 Opening kubernetes service default/hello-minikube in default browser...
-MacBook-Air:jmeter-operator kapishjoshi$ kubectl version
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.2", GitCommit:"66049e3b21efe110454d67df4fa62b08ea79a19b", GitTreeState:"clean", BuildDate:"2019-05-16T16:23:09Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.2", GitCommit:"66049e3b21efe110454d67df4fa62b08ea79a19b", GitTreeState:"clean", BuildDate:"2019-05-16T16:14:56Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}

from jmeter-operator.

HI,
I was able to fix the problem and was able to see the dashboard. Hope this helps folks who face a similar issue. Thanks @infinitydon for your help on this.

Solution:
After the above setup is done and all your pods are up and running do the following:
minikube addons list (check if heapster is enabled) if not then run below
minikube addons enable heapster
minikube service list (you should see heapster enabled in this list now)
Access the grafana dashabord via the minikube ip (http://{MINIKUBE-IP}:30002) - this will be showed when you run minikube service list

from jmeter-operator.

FYI -- I will also like you to note that minikube has some specific ways of administering a kubernetes cluster which is not applicable to a normal kubernetes deployment, just keep that in mind :)

from jmeter-operator.

ok thanks i will keep that in mind. The jmeter-operator folder is the only thing that needs to be deployed on the public cloud with the test script right? no need to clone the repo for each user correct?

from jmeter-operator.

Yes.. No need to clone the repo for each user, the test script is just a way to test that your jmeter installation works.

Each user/department should create it's own separate namespace and use that namespace (just like tqa) to create their own set of jmeter instance like below:

apiVersion: loadtest.jmeter.com/v1alpha1
kind: Jmeter
metadata:
  name: tqa-loadtest
  namespace: tqa
spec:
  # Add fields here
  slave_size: 2
  jmeter_master_image: kubernautslabs/jmeter_master:latest
  jmeter_slave_image: kubernautslabs/jmeter_slave:latest
  grafana_server_root: /
  grafana_service_type: LoadBalancer
  grafana_image: grafana/grafana:5.2.0
  influxdb_image: influxdb
  grafana_install: "true"
  grafana_reporter_install: "false"
  grafana_reporter_image: kubernautslabs/jmeter-reporter:latest
  influxdb_install: "true"

from jmeter-operator.