|
| 1 | +## QuickStart |
| 2 | + |
| 3 | +This tutorial guides you through running the simplest setup of the observability stack using example configuration files and Docker Compose. |
| 4 | + |
| 5 | +After completing these steps, you will have a full observability stack running locally, showing the availability of web pages you want to target |
| 6 | + |
| 7 | +### Requirements |
| 8 | + |
| 9 | +- Docker installed ([install Docker](https://docs.docker.com/get-docker/)) |
| 10 | +- Docker Compose installed ([install Docker Compose](https://docs.docker.com/compose/install/)) |
| 11 | +- A terminal with network access |
| 12 | + |
| 13 | +### Step 1: Run the Quickstart script |
| 14 | + |
| 15 | +Run this quickstart script to setup the project |
| 16 | +```bash |
| 17 | +curl https://raw.githubusercontent.com/CogStack/cogstack-platform-toolkit/main/observability/examples/simple/quickstart.sh | bash |
| 18 | +``` |
| 19 | +Now go to "http://localhost/grafana" to see the dashboards |
| 20 | + |
| 21 | +Thats everything. The stack is running and you can see the availability. |
| 22 | + |
| 23 | + |
| 24 | +### Optional Step: Probe your own web page |
| 25 | +Now you can look at getting monitoring of your own page |
| 26 | + |
| 27 | +In your current folder, edit the file `prometheus/scrape-configs/probers/probe-simple.yml` that you downloaded from git. |
| 28 | + |
| 29 | +Add the following yml to the bottom of the file: |
| 30 | + |
| 31 | +```yaml |
| 32 | +- targets: |
| 33 | + - https://google.com |
| 34 | + labels: |
| 35 | + name: google |
| 36 | + job: probe-my-own-site |
| 37 | +``` |
| 38 | +
|
| 39 | +
|
| 40 | +The change should get applied automatically, but if you dont want to wait then run |
| 41 | +``` |
| 42 | +docker compose restart |
| 43 | +``` |
| 44 | + |
| 45 | +Now refresh the grafana dashboard, and you can see the availability of google.com, it's probably 100%! |
| 46 | + |
| 47 | + |
| 48 | +## Next steps |
| 49 | +This is the end of this quickstart tutorial, that enables probing availability of endpoints. |
| 50 | + |
| 51 | +For the next steps we can: |
| 52 | +- Productionise our deployment to enable further features |
| 53 | +- Enable *Telemetry* like VM memory usage, and Elasticsearch index size, by running Exporters |
| 54 | +- Enable *Alerting* based on our availability and a defined Service Level Objective (SLO) |
| 55 | +- Look further into the available dashboards |
| 56 | +- Fully customize the stack with our own dashboards, recording rules and metrics |
| 57 | + |
| 58 | + |
| 59 | + |
| 60 | + |
| 61 | + |
0 commit comments