This example illustrates how to use the slo-native
module using SLO YAML
definitions as input. Keeping a folder with your SLO definitions helps with
maintaining an SLO repository and simplifies writing new SLOs.
The example will create the following resources:
- A set of SLO defined in the templates/ folder.
To run this example, you'll need:
- a GCP project (see an example definition here.
- the IAM role
roles/owner
on the project for the service account running the Terraform. - An App Engine application running
Name | Description | Type | Default | Required |
---|---|---|---|---|
app_engine_project_id | App Engine project id | any |
n/a | yes |
project_id | Project id | any |
n/a | yes |
Name | Description |
---|---|
slo-cass-latency5ms-window | n/a |
slo-gae-latency500ms | n/a |
slo-gcp-latency400ms | n/a |
slo-gcp-latency500ms-window | n/a |
slo-uptime-latency500ms | n/a |
slo-uptime-pass | n/a |
To provision this example, run the following from within this directory:
terraform init
to get the pluginsterraform plan
to see the infrastructure planterraform apply -target module.slos
to apply the infrastructure buildterraform destroy
to destroy the built infrastructure