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

Changes in documentation #1084

Merged
merged 4 commits into from
Nov 12, 2020
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion deploy/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ The diagram below illustrates the components of the Kubernetes collection soluti
* **Controller Manager.** Makes Controller Manager metrics available on an HTTP metrics port.
* **node-exporter.** The `node_exporter` add-on exposes node metrics, including CPU, memory, disk, and network utilization.
* **kube-state-metrics.** Listens to the Kubernetes API server; generates metrics about the state of the deployments, nodes, and pods in the cluster; and exports the metrics as plaintext on an HTTP endpoint listen port.
* **Prometheus deployment.** Scrapes the metrics exposed by the `node-exporter` add-on for Kubernetes and the `kube-state-metric`s component; writes metrics to a port on the Fluentd deployment.
* **Prometheus deployment.** Scrapes the metrics exposed by the `node-exporter` add-on for Kubernetes and the `kube-state-metrics` component; writes metrics to a port on the Fluentd deployment.
* **Fluentd deployment.** Forwards logs and metrics to HTTP sources on a hosted collector. Includes multiple Fluentd plugins that parse and format the metrics and enrich them with metadata.
* **Events Fluentd deployment.** Forwards events to an HTTP source on a hosted collector.

Expand Down
40 changes: 38 additions & 2 deletions vagrant/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,18 +30,32 @@ After successfull installation you can ssh to the virtual machine with:
vagrant ssh
```

NOTICE: The directory with sumo-kubernetes-collection repository on the host is synced with `/sumologic/` directory on the virtual machine.

## Build

To perform docker image build and to run tests please use `build` target:
On the virtual machine, to perform docker image build and to run tests please use `build` target:

```bash
sumo-make build
```

or

```
/sumologic/vagrant/Makefile build
```

## Collector

To install or upgrade collector please type:

```bash
sumo-make upgrade
```

or

```bash
/sumologic/vagrant/Makefile upgrade
```
Expand All @@ -51,12 +65,34 @@ and after that it will install/upgrade collector in the vagrant environment.

To remove collector please use:

```bash
sumo-make clean
```

or

```bash
/sumologic/vagrant/Makefile clean
```

List of other useful commands in the Makefile:
List of other useful targets:

- `expose-prometheus` - exposes prometheus on port 9090 of virtual machine
- `expose-grafana` - exposes grafana on port 8080 of virtual machine
- `apply-avalanche` - run one pod deployment of avalanche (metrics generator)

## Test

In order to quickly test whether sumo-kubernetes-collection works, one can use `receiver-mock` for that purpose.

To check receiver-mock logs please use:

```
kubectl logs $(kubectl get pod -l app=receiver-mock -o jsonpath="{.items[0].metadata.name}" -n receiver-mock) -n receiver-mock
```

To check metrics exposed by receiver-mock please use:

```
kubectl exec $(kubectl get pod -l app=receiver-mock -o jsonpath="{.items[0].metadata.name}" -n receiver-mock) -it -n receiver-mock -- curl http://localhost:3000/metrics
```
Copy link
Contributor

Choose a reason for hiding this comment

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

We could add those commands as new targets to the Makefile. Not necessary in this PR :)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We could add those commands as new targets to the Makefile. Not necessary in this PR :)

I'll add this in a new PR