You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2022/08/08 08:18:43 UTC

[GitHub] [apisix-ingress-controller] sanhofman opened a new issue, #1232: APISIX EKS Prometheus Grafana

sanhofman opened a new issue, #1232:
URL: https://github.com/apache/apisix-ingress-controller/issues/1232

   ### Issue description
   
   While deploying APISIX on AWS using apisix-ingress-controller like described here: https://github.com/apache/apisix-ingress-controller/blob/master/docs/en/latest/deployments/aws.md.
   
   We get following services up and running:
   
   ```
   NAME                        TYPE           CLUSTER-IP       EXTERNAL-IP                                                                  PORT(S)             AGE
   apisix-admin                ClusterIP      10.100.219.157   <none>                                                                       9180/TCP            5d23h
   apisix-dashboard            ClusterIP      10.100.108.89    <none>                                                                       80/TCP              5d18h
   apisix-etcd                 ClusterIP      10.100.177.65    <none>                                                                       2379/TCP,2380/TCP   5d23h
   apisix-etcd-headless        ClusterIP      None             <none>                                                                       2379/TCP,2380/TCP   5d23h
   apisix-gateway              LoadBalancer   10.100.214.106   aaa8a45985ee54ef1ac414944f615d20-1510783123.eu-central-1.elb.amazonaws.com   80:30114/TCP        5d23h
   apisix-ingress-controller   ClusterIP      10.100.160.139   <none>                                                                       80/TCP              5d23h
   prometheus-operated         ClusterIP      None             <none>                                                                       9090/TCP            5d17h
   ```
   
   Prometheus seems up and running while accessing through port-forward (http://localhost:8090/metrics). But how do we get the URL which can be used by Grafana to read out Prometheus metrics? It seems not exposed so no external IP/URL? 
   
   ### Environment
   
   - your apisix-ingress-controller version (output of apisix-ingress-controller version --long): 1.4.1
   - your Kubernetes cluster version (output of kubectl version): v1.22.10


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [apisix-ingress-controller] github-actions[bot] commented on issue #1232: APISIX EKS Prometheus Grafana

Posted by GitBox <gi...@apache.org>.
github-actions[bot] commented on issue #1232:
URL: https://github.com/apache/apisix-ingress-controller/issues/1232#issuecomment-1347617421

   This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [apisix-ingress-controller] github-actions[bot] commented on issue #1232: APISIX EKS Prometheus Grafana

Posted by GitBox <gi...@apache.org>.
github-actions[bot] commented on issue #1232:
URL: https://github.com/apache/apisix-ingress-controller/issues/1232#issuecomment-1312302365

   This issue has been marked as stale due to 90 days of inactivity. It will be closed in 30 days if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the dev@apisix.apache.org list. Thank you for your contributions.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [apisix-ingress-controller] sanhofman commented on issue #1232: APISIX EKS Prometheus Grafana

Posted by GitBox <gi...@apache.org>.
sanhofman commented on issue #1232:
URL: https://github.com/apache/apisix-ingress-controller/issues/1232#issuecomment-1211628891

   Ok I'm clear with that but nevertheless I'm unable to access Prometheus from Grafana.
   
   Available AWS services:
   
   ```
   NAME                        TYPE           CLUSTER-IP       EXTERNAL-IP                                                                  PORT(S)             
   apisix-admin                ClusterIP      10.100.219.157   <none>                                                                       9180/TCP            
   apisix-dashboard            ClusterIP      10.100.108.89    <none>                                                                       80/TCP              
   apisix-etcd                 ClusterIP      10.100.177.65    <none>                                                                       2379/TCP,2380/TCP   
   apisix-etcd-headless        ClusterIP      None             <none>                                                                       2379/TCP,2380/TCP   
   apisix-gateway              LoadBalancer   10.100.214.106   ...eu-central-1.elb.amazonaws.com   80:30114/TCP        
   apisix-ingress-controller   ClusterIP      10.100.160.139   <none>                                                                       80/TCP              
   grafana                     LoadBalancer   10.100.255.145   ...eu-central-1.elb.amazonaws.com   80:31666/TCP        
   prometheus-operated         ClusterIP      None             <none>                                                                       9090/TCP            
   ```
   
   While configuring Prometheus as Datasource:
   
   ![prometheus-datasource-grafana](https://user-images.githubusercontent.com/17701731/184081466-915140e6-8773-40f5-a36e-7a064ce5861c.png)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [apisix-ingress-controller] github-actions[bot] closed issue #1232: APISIX EKS Prometheus Grafana

Posted by GitBox <gi...@apache.org>.
github-actions[bot] closed issue #1232: APISIX EKS Prometheus Grafana
URL: https://github.com/apache/apisix-ingress-controller/issues/1232


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [apisix-ingress-controller] tao12345666333 commented on issue #1232: APISIX EKS Prometheus Grafana

Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #1232:
URL: https://github.com/apache/apisix-ingress-controller/issues/1232#issuecomment-1211067670

   no, you should use Prometheus to fetch `/apisix/prometheus/metrics` 
   
   And add Prometheus as DataSource in Grafana.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [apisix-ingress-controller] tao12345666333 commented on issue #1232: APISIX EKS Prometheus Grafana

Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #1232:
URL: https://github.com/apache/apisix-ingress-controller/issues/1232#issuecomment-1208456415

   you can refer to this one https://github.com/apache/apisix-ingress-controller/blob/master/docs/en/latest/tutorials/how-to-access-Apache-APISIX-Prometheus-Metrics-on-k8s.md 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [apisix-ingress-controller] sanhofman commented on issue #1232: APISIX EKS Prometheus Grafana

Posted by GitBox <gi...@apache.org>.
sanhofman commented on issue #1232:
URL: https://github.com/apache/apisix-ingress-controller/issues/1232#issuecomment-1209042593

   Hi @tao12345666333,
   
   Thanks for your response.
   
   I'm able to call the `/apisix/prometheus/metrics` only from within the apisix POD, but how do we make this available to Grafana dashboards?
   
   ![grafana](https://user-images.githubusercontent.com/17701731/183595703-7733dc06-d68e-4bf5-8282-f2f676e81b00.png)
   
   Here we retrieve the following connection refused, both for GET and POST:
   
   `Error reading Prometheus: Post "http://localhost:9091/apisix/prometheus/metrics/api/v1/query": dial tcp 127.0.0.1:9091: connect: connection refused`
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org