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.

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

VZ-5852: Updates for Prometheus Operator #534

Merged
merged 2 commits into from
Jul 1, 2022
Merged

Conversation

fredtibbitts
Copy link
Contributor

Update the Prometheus info on the Application Deployment guide page and add a Prometheus troubleshooting page.

Copy link
Contributor

@rosemarymarano rosemarymarano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Few minor edits

---

### 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`, etc.) This is likely caused by the configuration of the Kubernetes cluster
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(kube-etcd, kube-proxy, etc.) -> (kube-etcd, kube-proxy, and such). (period)


### 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`, etc.) 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 so refer to the documentation for your cluster type for details.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

type of cluster -> type of cluster, (comma)
is cluster dependent -> is cluster dependent; (semi-colon)
so refer to the documentation for your cluster type for details -> for details, refer to the documentation for your cluster type.

When viewing targets in the Prometheus console some Kubernetes cluster monitors may be down (`kube-etcd`, `kube-proxy`, etc.) 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 so refer to the documentation for your cluster type for details.

For example, to enable `kube-proxy` metrics on KinD clusters, edit the `kube-proxy` configmap:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

KinD -> Kind (Oracle Style Guide decision for how to write this product name)
configmap -> ConfigMap (to be consistent with the VZ documentation)

```
$ kubectl edit cm/kube-proxy -n kube-system
```
Replace the `metricsBindAddress` value with the following and save the configmap:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

configmap -> ConfigMap

$ kubectl delete pod -l k8s-app=kube-proxy -n kube-system
```

See this GitHub [issue](https://github.com/prometheus-community/helm-charts/issues/204) for additional information.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

re-write -> For more information, see this GitHub issue.

```
metricsBindAddress: 0.0.0.0:10249
```
Then restart the `kube-proxy` pods:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Then -> Then, (comma)

@fredtibbitts fredtibbitts merged commit f07a783 into master Jul 1, 2022
@fredtibbitts fredtibbitts deleted the ftibbitts/VZ-5852 branch July 1, 2022 15:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants