You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/imt/docs/monitoring-as-code/terraform.md
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,21 +22,21 @@ Full documentation for the Splunk Terraform Provider is available [here](https:/
22
22
Remaining in your AWS/EC2 instance, change into the `o11y-cloud-jumpstart` directory
23
23
24
24
{{< tabpane >}}
25
-
{{< tab header="Change directory" lang="bash" >}}
25
+
{{< tab header="Change directory" lang="sh" >}}
26
26
cd observability-content-contrib/integration-examples/terraform-jumpstart
27
27
{{</tab >}}
28
28
{{< /tabpane >}}
29
29
30
30
The environment variables needed should already be set from [Installation using Helm](../../../otel/k3s/#2-installation-using-helm). If not, create the following environment variables to use in the Terraform steps below
@@ -104,10 +104,10 @@ The `terraform plan` command creates an execution plan. By default, creating a p
104
104
The plan command alone will not actually carry out the proposed changes, and so you can use this command to check whether the proposed changes match what you expected before you apply the changes
105
105
106
106
{{< tabpane >}}
107
-
{{< tab header="Execution Plan" lang="bash" >}}
107
+
{{< tab header="Execution Plan" lang="sh" >}}
108
108
terraform plan -var="access_token=$ACCESS_TOKEN" -var="realm=$REALM" -var="o11y_prefix=[$(hostname)]"
109
109
{{</tab >}}
110
-
{{< tab header="Execution Plan Output" lang="bash" >}}
110
+
{{< tab header="Execution Plan Output" lang="text" >}}
111
111
Plan: 146 to add, 0 to change, 0 to destroy.
112
112
{{</tab >}}
113
113
{{< /tabpane >}}
@@ -125,18 +125,18 @@ The most straightforward way to use `terraform apply` is to run it without any a
125
125
Due to this being a workshop it is required that the prefix is to be unique so you need to run the `terraform apply` below.
Once the apply has completed, validate that the detectors were created, under the **Alerts & Detectors** and click on the **Detectors** tab. They will be prefixed by the hostname of your instance. To check the prefix value run:
137
137
138
138
{{< tabpane >}}
139
-
{{< tab header="Echo Hostname" lang="bash" >}}
139
+
{{< tab header="Echo Hostname" lang="sh" >}}
140
140
echo $(hostname)
141
141
{{</tab >}}
142
142
{{< /tabpane >}}
@@ -154,10 +154,10 @@ While you will typically not want to destroy long-lived objects in a production
154
154
Now go and destroy all the Detectors and Dashboards that were previously applied!
0 commit comments