Skip to content
Snippets Groups Projects
Select Git revision
  • f752c172f1d1c457b4edb6f08e8705ee81a05851
  • main default protected
  • release-0.15
  • automated-updates-main
  • release-0.13
  • automated-updates-release-0.13
  • release-0.14
  • release-0.10
  • release-0.11
  • release-0.12
  • fix-versions-action
  • versions-fix
  • release-0.9
  • release-0.8
  • release-0.7
  • release-0.6
  • release-0.5
  • release-0.4
  • release-0.3
  • release-0.1
  • release-0.2
  • v0.15.0
  • v0.14.0
  • v0.13.0
  • v0.12.0
  • v0.11.0
  • v0.10.0
  • v0.9.0
  • v0.8.0
  • v0.7.0
  • v0.6.0
  • v0.5.0
  • v0.4.0
  • v0.3.0
  • v0.2.0
  • v0.1.0
36 results

access-ui.md

Blame
  • user avatar
    Paweł Krupa (paulfantom) authored
    Signed-off-by: default avatarPaweł Krupa (paulfantom) <pawel@krupa.net.pl>
    545d9ed0
    History

    Access UIs

    Prometheus, Grafana, and Alertmanager dashboards can be accessed quickly using kubectl port-forward after running the quickstart via the commands below. Kubernetes 1.10 or later is required.

    Note: There are instructions on how to route to these pods behind an ingress controller in the Exposing Prometheus/Alermanager/Grafana via Ingress section.

    Prometheus

    $ kubectl --namespace monitoring port-forward svc/prometheus-k8s 9090

    Then access via http://localhost:9090

    Grafana

    $ kubectl --namespace monitoring port-forward svc/grafana 3000

    Then access via http://localhost:3000 and use the default grafana user:password of admin:admin.

    Alert Manager

    $ kubectl --namespace monitoring port-forward svc/alertmanager-main 9093

    Then access via http://localhost:9093