docs: add links to KillerCoda tutorial environments (#84831)

pull/84841/head
Marie Cruz 1 year ago committed by GitHub
parent 0df7c9201a
commit 821d9a5565
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
  1. 29
      docs/sources/tutorials/grafana-fundamentals/index.md

@ -41,7 +41,12 @@ Alternatively, you can also watch our Grafana for Beginners series where we disc
- [Docker](https://docs.docker.com/install/) - [Docker](https://docs.docker.com/install/)
- [Docker Compose](https://docs.docker.com/compose/) (included in Docker for Desktop for macOS and Windows) - [Docker Compose](https://docs.docker.com/compose/) (included in Docker for Desktop for macOS and Windows)
- [Git](https://git-scm.com/) - [Git](https://git-scm.com/)
{{% /class %}}
### KillerCoda sandbox environment (Alternative)
If you would prefer to follow along with this tutorial without needing to set up a local environment, you can use the [KillerCoda sandbox environment](https://killercoda.com/grafana-labs/course/full-stack/tutorial-enviroment).
{{% /class %}}
## Set up the sample application ## Set up the sample application
@ -281,7 +286,7 @@ The most basic alert consists of two parts:
- Email - Email
- [Webhooks](#create-a-contact-point-for-grafana-managed-alerts) - [Webhooks](#create-a-contact-point-for-grafana-managed-alerts)
- [Telegram](https://grafana.com/blog/2023/12/28/how-to-integrate-grafana-alerting-and-telegram/) - [Telegram](https://grafana.com/blog/2023/12/28/how-to-integrate-grafana-alerting-and-telegram/)
- Slack - [Slack](/docs/grafana/<GRAFANA_VERSION>/alerting/alerting-rules/manage-contact-points/integrations/configure-slack/)
- PagerDuty - PagerDuty
1. An _Alert rule_ - An Alert rule defines one or more _conditions_ that Grafana regularly evaluates. When these evaluations meet the rule's criteria, the alert is triggered. 1. An _Alert rule_ - An Alert rule defines one or more _conditions_ that Grafana regularly evaluates. When these evaluations meet the rule's criteria, the alert is triggered.
@ -328,12 +333,12 @@ Now that Grafana knows how to notify us, it's time to set up an alert rule:
``` ```
1. Press **Preview**. You should see some data returned. 1. Press **Preview**. You should see some data returned.
1. Keep expressions “B” and "C" as they are. These expressions (Reduce and Threshold, respectively) come by default when creating a new rule. Expression "B", selects the last value of our query “A”, while the Threshold expression "C" will check if the last value from expression "B" is above a specific value. In addition, the Threshold expression is the alert condition by default. Enter `0.2` as threshold value. [You can read more about queries and conditions here](https://grafana.com/docs/grafana/latest/alerting/fundamentals/alert-rules/queries-conditions/#expression-queries). 1. Keep expressions “B” and "C" as they are. These expressions (Reduce and Threshold, respectively) come by default when creating a new rule. Expression "B", selects the last value of our query “A”, while the Threshold expression "C" will check if the last value from expression "B" is above a specific value. In addition, the Threshold expression is the alert condition by default. Enter `0.2` as threshold value. [You can read more about queries and conditions here](/docs/grafana/<GRAFANA_VERSION>/alerting/fundamentals/alert-rules/queries-conditions/#expression-queries).
1. In **Section 3**, in Folder, create a new folder, by clicking `New folder` and typing a name for the folder. This folder will contain our alerts. For example: `fundamentals`. Then, click `create`. 1. In **Section 3**, in Folder, create a new folder, by clicking `New folder` and typing a name for the folder. This folder will contain our alerts. For example: `fundamentals`. Then, click `create`.
1. In the Evaluation group, repeat the above step to create a new one. We will name it `fundamentals` too. 1. In the Evaluation group, repeat the above step to create a new one. We will name it `fundamentals` too.
1. Choose an Evaluation interval (how often the alert will be evaluated). For example, every `10s` (10 seconds). 1. Choose an Evaluation interval (how often the alert will be evaluated). For example, every `10s` (10 seconds).
1. Set the pending period. This is the time that a condition has to be met until the alert enters in Firing state and a notification is sent. Enter `0s`. For the purposes of this tutorial, the evaluation interval is intentionally short. This makes it easier to test. This setting makes Grafana wait until an alert has fired for a given time before Grafana sends the notification. 1. Set the pending period. This is the time that a condition has to be met until the alert enters in Firing state and a notification is sent. Enter `0s`. For the purposes of this tutorial, the evaluation interval is intentionally short. This makes it easier to test. This setting makes Grafana wait until an alert has fired for a given time before Grafana sends the notification.
1. In **Section 4**, you can optionally add some sample text to your summary message. [Read more about message templating here](/docs/grafana/latest/alerting/unified-alerting/message-templating/). 1. In **Section 4**, you can optionally add some sample text to your summary message. [Read more about message templating here](/docs/grafana/<GRAFANA_VERSION>/alerting/unified-alerting/message-templating/).
1. Click **Save rule and exit** at the top of the page. 1. Click **Save rule and exit** at the top of the page.
1. In Grafana's sidebar, navigate to **Notification policies**. 1. In Grafana's sidebar, navigate to **Notification policies**.
1. Under **Default policy**, select **...** &rsaquo; **Edit** and change the **Default contact point** from **grafana-default-email** to **RequestBin**. 1. Under **Default policy**, select **...** &rsaquo; **Edit** and change the **Default contact point** from **grafana-default-email** to **RequestBin**.
@ -380,13 +385,17 @@ In this tutorial you learned about fundamental features of Grafana. To do so, we
docker-compose down -v docker-compose down -v
``` ```
### KillerCoda sandbox environment (completed tutorial)
Do you want to see the finished result? Check out our [completed KillerCoda sandbox environment](https://killercoda.com/grafana-labs/course/full-stack/tutorial-enviroment-completed) containing the entire demo with dashboards, checks, and data sources configured.
### Learn more ### Learn more
Check out the links below to continue your learning journey with Grafana's LGTM stack. Check out the links below to continue your learning journey with Grafana's LGTM stack.
- [Prometheus](/docs/grafana/latest/features/datasources/prometheus/) - [Prometheus](/docs/grafana/<GRAFANA_VERSION>/features/datasources/prometheus/)
- [Loki](/docs/grafana/latest/features/datasources/loki/) - [Loki](/docs/grafana/<GRAFANA_VERSION>/features/datasources/loki/)
- [Explore](/docs/grafana/latest/features/explore/) - [Explore](/docs/grafana/<GRAFANA_VERSION>/features/explore/)
- [Alerting Overview](/docs/grafana/latest/alerting/) - [Alerting Overview](/docs/grafana/<GRAFANA_VERSION>/alerting/)
- [Alert rules](/docs/grafana/latest/alerting/create-alerts/) - [Alert rules](/docs/grafana/<GRAFANA_VERSION>/alerting/create-alerts/)
- [Contact Points](/docs/grafana/latest/alerting/notifications/) - [Contact Points](/docs/grafana/<GRAFANA_VERSION>/alerting/notifications/)

Loading…
Cancel
Save