Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

VZ-5852: Updates for Prometheus Operator #534

Merged
merged 2 commits into from
Jul 1, 2022
Merged

VZ-5852: Updates for Prometheus Operator #534

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9c8e297
Updates for Prometheus Operator
fredtibbitts Jul 1, 2022
6c2ac9a
Updates based on review comments
fredtibbitts Jul 1, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 12 additions & 3 deletions content/en/docs/guides/app-deployment/application-deployment-guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -311,18 +311,27 @@ and enabled for Istio.
vmi-system-grafana-799d79648d-wsdp4 2/2 Running 0 47m
vmi-system-kiali-574c6dd94d-f49jv 2/2 Running 0 51m
vmi-system-kibana-77f8d998f4-zzvqr 2/2 Running 0 47m
vmi-system-prometheus-0-7f89d54fbf-brg6x 3/3 Running 0 45m
```

These pods in the `verrazzano-system` namespace constitute a
```
$ kubectl get pods -n verrazzano-monitoring

# Sample output
NAME READY STATUS RESTARTS AGE
prometheus-node-exporter-fstc7 1/1 Running 0 14h
prometheus-operator-kube-p-operator-857fb66b74-szv4h 1/1 Running 0 14h
prometheus-prometheus-operator-kube-p-prometheus-0 3/3 Running 0 14h
```

These pods in the `verrazzano-system` and `verrazzano-monitoring` namespaces constitute a
monitoring stack created by Verrazzano for the deployed applications.

The monitoring infrastructure comprises several components:
* `vmi-system-es` - OpenSearch for log collection
* `vmi-system-grafana` - Grafana for metric visualization
* `vms-system-kiali` - Kiali for management console of `istio` service mesh
* `vmi-system-kibana` - OpenSearch Dashboards for log visualization
* `vmi-system-prometheus` - Prometheus for metric collection
* `prometheus-prometheus-operator-kube-p-prometheus` - Prometheus for metric collection
<p/>

1. Diagnose failures.
Expand Down
26 changes: 26 additions & 0 deletions content/en/docs/troubleshooting/troubleshooting-prometheus.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
---
title: "Prometheus"
linkTitle: "Prometheus"
description: "Troubleshoot Prometheus issues"
weight: 1
draft: false
---

### Kubernetes cluster monitors are in a "DOWN" state
When viewing targets in the Prometheus console some Kubernetes cluster monitors may be down (`kube-etcd`, `kube-proxy`, and such). This is likely caused by the configuration of the Kubernetes cluster
itself. Depending on the type of cluster, certain metrics may be disabled by default. Enabling metrics is cluster dependent; for details, refer to the documentation for your cluster type.

For example, to enable `kube-proxy` metrics on Kind clusters, edit the `kube-proxy` ConfigMap:
```
$ kubectl edit cm/kube-proxy -n kube-system
```
Replace the `metricsBindAddress` value with the following and save the ConfigMap:
```
metricsBindAddress: 0.0.0.0:10249
```
Then, restart the `kube-proxy` pods:
```
$ kubectl delete pod -l k8s-app=kube-proxy -n kube-system
```

For more information, see this GitHub [issue](https://github.com/prometheus-community/helm-charts/issues/204).