Skip to content

Commit 35f60b5

Browse files
committed
Support for EC2 and multipass instances
1 parent bed46c3 commit 35f60b5

File tree

1 file changed

+20
-3
lines changed
  • content/en/other/pet-clinic/docs

1 file changed

+20
-3
lines changed

content/en/other/pet-clinic/docs/imt.md

Lines changed: 20 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,9 @@ Splunk Observability Cloud offers wizards to walk you through the setup of the C
1717

1818
## 2. Configure environment variables
1919

20-
If you have already completed the **Splunk IM** workshop you can take advantage of the existing environment variables. Otherwise, create the `ACCESS_TOKEN` and `REALM` environment variables to use in the proceeding OpenTelemetry Collector install command. For instance, if your realm is `us1`, you would type `export REALM=us1` and for `eu0` type `export REALM=eu0` etc.
20+
If you have already completed the **Splunk IM** workshop you can take advantage of the existing environment variables. Otherwise, create the `ACCESS_TOKEN` and `REALM` environment variables to use in the proceeding OpenTelemetry Collector install command.
21+
22+
For instance, if your realm is `us1`, you would type `export REALM=us1` and for `eu0` type `export REALM=eu0` etc.
2123

2224
{{< tabs >}}
2325
{{% tab name="Export ACCESS TOKEN" %}}
@@ -57,6 +59,21 @@ curl -sSL https://dl.signalfx.com/splunk-otel-collector.sh > /tmp/splunk-otel-co
5759
sudo sh /tmp/splunk-otel-collector.sh --with-instrumentation --deployment-environment $(hostname)-petclinic --realm $REALM -- $ACCESS_TOKEN
5860
```
5961

60-
This command will download and setup the OpenTelemetry Collector. Once the install is completed, you can navigate to the Infrastructure page to see the data from your host, **Infrastructure → My Data Center → Hosts**.
62+
{{% notice style="info" title="AWS/EC2 instances" %}}
63+
If you are attempting this workshop on an AWS/EC2 instance you will have to patch the collector to expose the hostname of the instance:
64+
65+
``` bash
66+
sudo sed -i 's/gcp, ecs, ec2, azure, system/system, gcp, ecs, ec2, azure/g' /etc/otel/collector/agent_config.yaml
67+
```
68+
69+
Once the `agent_config.yaml` has been patched, you will need to restart the collector:
70+
71+
``` bash
72+
sudo systemctl restart splunk-otel-collector
73+
```
74+
75+
{{% /notice %}}
76+
77+
Once the install is completed, you can navigate to the **Hosts with agent installed** dashboard to see the data from your host, **Dashboards → Hosts with agent installed**.
6178

62-
Click {{% button style="default" %}}Add Filter{{% /button %}} select `host.name` and type or select the hostname of your virtual machine. Once you see data flowing for your host, we are then ready to get started with the APM component.
79+
Use the dashboard filter and select `host.name` and type or select the hostname of your virtual machine. Once you see data flowing for your host, we are then ready to get started with the APM component.

0 commit comments

Comments
 (0)