Skip to content

Commit 710ce1b

Browse files
heidi04aldidiheidi04aldidi
committed
replaced {{<...>}} with {{%...%}}
1 parent fe3598a commit 710ce1b

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

59 files changed

+310
-310
lines changed

‎content/en/_index.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ show_banner: true
1616

1717
<div class="d-none"><a rel="me" href="https://fosstodon.org/@opentelemetry"></a></div>
1818

19-
{{< blocks/cover image_anchor="top" height="max" color="primary" >}}
19+
{{% blocks/cover image_anchor="top" height="max" color="primary" %}}
2020

2121
<!-- prettier-ignore -->
2222
![OpenTelemetry](/img/logos/opentelemetry-horizontal-color.svg)
@@ -42,7 +42,7 @@ show_banner: true
4242
- [Ops](docs/getting-started/ops/)
4343

4444
</div>
45-
{{< /blocks/cover >}}
45+
{{% /blocks/cover %}}
4646

4747
{{% blocks/lead color="white" %}}
4848

‎content/en/blog/2023/cloud-foundry.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ author: >-
88
cSpell:ignore: Kocher unscalable
99
---
1010

11-
{{< blog/integration-badge >}}
11+
{{% blog/integration-badge %}}
1212

1313
[Cloud Foundry](https://www.cloudfoundry.org/) recently integrated the
1414
[OpenTelemetry Collector](/docs/collector/) for metrics egress and we learned a

‎content/en/blog/2023/euwg-future-of-observability-panel.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ Observability practices, in this panel hosted by the
2525
centered around their journey with OpenTelemetry and how it has shaped their
2626
Observability practices. Watch the full recording:
2727

28-
{{<youtube zSeKL2-_sVg>}}
28+
{{%youtube zSeKL2-_sVg%}}
2929

3030
<br/>For a quick summary, check out some of the key discussion takeaways below.
3131

‎content/en/blog/2023/humans-of-otel.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ Special thanks to [Reese Lee](https://github.com/reese-lee) for the camera work!
4141

4242
You can watch the full recording here:
4343

44-
{{<youtube coPrhP_7lVU>}}
44+
{{%youtube coPrhP_7lVU%}}
4545

4646
<br/>Thanks to everyone who has contributed to OpenTelemetry to date, and we
4747
look forward to your contributions in 2024! 🎉

‎content/en/blog/2023/integrations.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ linkTitle: Integrations Welcome!
44
date: 2023-11-06
55
---
66

7-
{{< blog/integration-badge >}}
7+
{{% blog/integration-badge %}}
88

99
Embracing OpenTelemetry's [vision], we are committed to enabling high-quality
1010
telemetry throughout the entire software stack!

‎content/en/blog/2023/otterize-otel/index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ author: >-
88
cSpell:ignore: brainer Otterize Shoshan
99
---
1010

11-
{{< blog/integration-badge >}}
11+
{{% blog/integration-badge %}}
1212

1313
## A no-brainer integration: Adding OpenTelemetry support to the Otterize network mapper
1414

‎content/en/blog/2023/tyk-api-gateway/index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: >-
66
[Sonja Chevre](https://github.com/SonjaChevre) (Tyk Technologies)
77
---
88

9-
{{< blog/integration-badge >}}
9+
{{% blog/integration-badge %}}
1010

1111
We're excited to announce that
1212
[Tyk API Gateway](https://github.com/TykTechnologies/tyk) has first-class

‎content/en/blog/2024/collecting-otel-compliant-java-logs-from-files/index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -205,7 +205,7 @@ OTLP/JSON format, with a JSON object per line. The log records are nested in the
205205

206206
## Configure the Collector to ingest the OTLP/JSON logs
207207

208-
{{< figure class="figure" src="otel-collector-otlpjson-pipeline.png" attr="View OTel Collector pipeline with OTelBin" attrlink=`https://www.otelbin.io/s/69739d790cf279c203fc8efc86ad1a876a2fc01a` >}}
208+
{{% figure class="figure" src="otel-collector-otlpjson-pipeline.png" attr="View OTel Collector pipeline with OTelBin" attrlink=`https://www.otelbin.io/s/69739d790cf279c203fc8efc86ad1a876a2fc01a` %}}
209209

210210
```yaml
211211
# tested with otelcol-contrib v0.112.0

‎content/en/blog/2024/humans-of-otel-eu-2024.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ Also, special thanks to:
3636

3737
You can watch the full recording here:
3838

39-
{{<youtube bsfMECwmsm0>}}
39+
{{%youtube bsfMECwmsm0%}}
4040

4141
<br/>Thanks to everyone who has contributed to OpenTelemetry to date, and we
4242
look forward to your continued contributions in 2024 and beyond! 🎉

‎content/en/blog/2024/humans-of-otel-na-2024.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ Also, special thanks to:
3838

3939
You can watch the full recording here:
4040

41-
{{<youtube TIMgKXCeiyQ>}}
41+
{{%youtube TIMgKXCeiyQ%}}
4242

4343
<br/>Thanks to everyone who has contributed to OpenTelemetry to date, and we
4444
look forward to your continued contributions in 2025 and beyond! 🎉

‎content/en/blog/2025/observing-lambdas/index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ Lambda to return, even if not all data has been sent. At the next invocation (or
5757
on shutdown) the Collector continues exporting the data while your function does
5858
its thing.
5959

60-
{{< figure src="diagram-execution-timing.svg" caption="Diagram showcasing how execution timing differs with and without a Collector">}}
60+
{{% figure src="diagram-execution-timing.svg" caption="Diagram showcasing how execution timing differs with and without a Collector"%}}
6161

6262
## How can I use it?
6363

‎content/en/blog/2025/otel-cicd-sig/index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -163,7 +163,7 @@ that closely align with the [SLSA](https://slsa.dev/spec/v1.0/about) model. This
163163
is really the first time a direct connection is being made between observability
164164
and software supply chain security. Consider the following
165165
[supply chain threat model](https://slsa.dev/spec/v1.0/threats) defined by SLSA:
166-
{{< figure class="figure" src="SLSA-supply-chain-model.png" attr="SLSA Community Specification License 1.0" attrlink=`https://github.com/slsa-framework/slsa?tab=License-1-ov-file` >}}
166+
{{% figure class="figure" src="SLSA-supply-chain-model.png" attr="SLSA Community Specification License 1.0" attrlink=`https://github.com/slsa-framework/slsa?tab=License-1-ov-file` %}}
167167

168168
These new attributes for artifacts and attestations help observe the sequence of
169169
events modeled in the above diagram in real time. Really, the conventions that

‎content/en/docs/collector/custom-collector.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ Collector [releases with `cmd/builder` tags][tags]. You will find a list of
3131
assets named based on OS and chipset, so download the one that fits your
3232
configuration:
3333

34-
{{< tabpane text=true >}}
34+
{{% tabpane text=true %}}
3535

3636
{{% tab "Linux (AMD 64)" %}}
3737

@@ -80,7 +80,7 @@ Invoke-WebRequest -Uri "https://github.com/open-telemetry/opentelemetry-collecto
8080
Unblock-File -Path "ocb.exe"
8181
```
8282

83-
{{% /tab %}} {{< /tabpane >}}
83+
{{% /tab %}} {{% /tabpane %}}
8484

8585
To make sure the `ocb` is ready to be used, go to your terminal and type
8686
`./ocb help`, and once you hit enter you should have the output of the `help`

‎content/en/docs/collector/deployment/agent.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ export OTEL_EXPORTER_OTLP_ENDPOINT=http://collector.example.com:4318
3636
The collector serving at `collector.example.com:4318` would then be configured
3737
like so:
3838

39-
{{< tabpane text=true >}} {{% tab Traces %}}
39+
{{% tabpane text=true %}} {{% tab Traces %}}
4040

4141
```yaml
4242
receivers:
@@ -109,7 +109,7 @@ service:
109109
exporters: [file]
110110
```
111111
112-
{{% /tab %}} {{< /tabpane >}}
112+
{{% /tab %}} {{% /tabpane %}}
113113
114114
If you want to try it out for yourself, you can have a look at the end-to-end
115115
[Java][java-otlp-example] or [Python][py-otlp-example] examples.

‎content/en/docs/collector/deployment/gateway/index.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -111,7 +111,7 @@ configuration fields:
111111
The first-tier collector servicing the OTLP endpoint would be configured as
112112
shown below:
113113

114-
{{< tabpane text=true >}} {{% tab Static %}}
114+
{{% tabpane text=true %}} {{% tab Static %}}
115115

116116
```yaml
117117
receivers:
@@ -194,7 +194,7 @@ service:
194194
exporters: [loadbalancing]
195195
```
196196
197-
{{% /tab %}} {{< /tabpane >}}
197+
{{% /tab %}} {{% /tabpane %}}
198198
199199
The load-balancing exporter emits metrics including
200200
`otelcol_loadbalancer_num_backends` and `otelcol_loadbalancer_backend_latency`

‎content/en/docs/collector/installation.md

+12-12
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ and [Deployment Methods][] page.
1717
The following commands pull a Docker image and run the Collector in a container.
1818
Replace `{{% param vers %}}` with the version of the Collector you want to run.
1919

20-
{{< tabpane text=true >}} {{% tab DockerHub %}}
20+
{{% tabpane text=true %}} {{% tab DockerHub %}}
2121

2222
```sh
2323
docker pull otel/opentelemetry-collector-contrib:{{% param vers %}}
@@ -31,12 +31,12 @@ docker pull ghcr.io/open-telemetry/opentelemetry-collector-releases/opentelemetr
3131
docker run ghcr.io/open-telemetry/opentelemetry-collector-releases/opentelemetry-collector-contrib:{{% param vers %}}
3232
```
3333

34-
{{% /tab %}} {{< /tabpane >}}
34+
{{% /tab %}} {{% /tabpane %}}
3535

3636
To load a custom configuration file from your working directory, mount that file
3737
as a volume:
3838

39-
{{< tabpane text=true >}} {{% tab DockerHub %}}
39+
{{% tabpane text=true %}} {{% tab DockerHub %}}
4040

4141
```sh
4242
docker run -v $(pwd)/config.yaml:/etc/otelcol-contrib/config.yaml otel/opentelemetry-collector-contrib:{{% param vers %}}
@@ -48,7 +48,7 @@ docker run -v $(pwd)/config.yaml:/etc/otelcol-contrib/config.yaml otel/opentelem
4848
docker run -v $(pwd)/config.yaml:/etc/otelcol-contrib/config.yaml ghcr.io/open-telemetry/opentelemetry-collector-releases/opentelemetry-collector-contrib:{{% param vers %}}
4949
```
5050

51-
{{% /tab %}} {{< /tabpane >}}
51+
{{% /tab %}} {{% /tabpane %}}
5252

5353
## Docker Compose
5454

@@ -108,7 +108,7 @@ amd64/arm64/i386 systems. You can find the default configuration in
108108

109109
To get started on Debian systems run the following commands:
110110

111-
{{< tabpane text=true >}} {{% tab AMD64 %}}
111+
{{% tabpane text=true %}} {{% tab AMD64 %}}
112112

113113
```sh
114114
sudo apt-get update
@@ -135,13 +135,13 @@ wget https://github.com/open-telemetry/opentelemetry-collector-releases/releases
135135
sudo dpkg -i otelcol_{{% param vers %}}_linux_386.deb
136136
```
137137

138-
{{% /tab %}} {{< /tabpane >}}
138+
{{% /tab %}} {{% /tabpane %}}
139139

140140
### RPM Installation
141141

142142
To get started on Red Hat systems run the following commands:
143143

144-
{{< tabpane text=true >}} {{% tab AMD64 %}}
144+
{{% tabpane text=true %}} {{% tab AMD64 %}}
145145

146146
```sh
147147
sudo yum update
@@ -168,14 +168,14 @@ wget https://github.com/open-telemetry/opentelemetry-collector-releases/releases
168168
sudo rpm -ivh otelcol_{{% param vers %}}_linux_386.rpm
169169
```
170170

171-
{{% /tab %}} {{< /tabpane >}}
171+
{{% /tab %}} {{% /tabpane %}}
172172

173173
### Manual Linux installation
174174

175175
Linux [releases][] are available for various architectures. You can download the
176176
file containing the binary and install it on your machine manually:
177177

178-
{{< tabpane text=true >}} {{% tab AMD64 %}}
178+
{{% tabpane text=true %}} {{% tab AMD64 %}}
179179

180180
```sh
181181
curl --proto '=https' --tlsv1.2 -fOL https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/v{{% param vers %}}/otelcol_{{% param vers %}}_linux_amd64.tar.gz
@@ -203,7 +203,7 @@ curl --proto '=https' --tlsv1.2 -fOL https://github.com/open-telemetry/opentelem
203203
tar -xvf otelcol_{{% param vers %}}_linux_ppc64le.tar.gz
204204
```
205205

206-
{{% /tab %}} {{< /tabpane >}}
206+
{{% /tab %}} {{% /tabpane %}}
207207

208208
### Automatic service configuration
209209

@@ -235,7 +235,7 @@ macOS [releases][] are available for Intel and ARM systems. The releases are
235235
packaged as gzipped tarballs (`.tar.gz`). To unpack them, run the following
236236
commands:
237237

238-
{{< tabpane text=true >}} {{% tab Intel %}}
238+
{{% tabpane text=true %}} {{% tab Intel %}}
239239

240240
```sh
241241
curl --proto '=https' --tlsv1.2 -fOL https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/v{{% param vers %}}/otelcol_{{% param vers %}}_darwin_amd64.tar.gz
@@ -249,7 +249,7 @@ curl --proto '=https' --tlsv1.2 -fOL https://github.com/open-telemetry/opentelem
249249
tar -xvf otelcol_{{% param vers %}}_darwin_arm64.tar.gz
250250
```
251251

252-
{{% /tab %}} {{< /tabpane >}}
252+
{{% /tab %}} {{% /tabpane %}}
253253

254254
Every Collector release includes an `otelcol` executable that you can run after
255255
unpacking.

‎content/en/docs/collector/internal-telemetry.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -118,7 +118,7 @@ are:
118118
You can also see logs for the Collector on a Linux systemd system using
119119
`journalctl`:
120120

121-
{{< tabpane text=true >}} {{% tab "All logs" %}}
121+
{{% tabpane text=true %}} {{% tab "All logs" %}}
122122

123123
```sh
124124
journalctl | grep otelcol
@@ -130,7 +130,7 @@ journalctl | grep otelcol
130130
journalctl | grep otelcol | grep Error
131131
```
132132

133-
{{% /tab %}} {{< /tabpane >}}
133+
{{% /tab %}} {{% /tabpane %}}
134134

135135
The following configuration can be used to emit internal logs from the Collector
136136
to an OTLP/HTTP backend:
@@ -221,7 +221,7 @@ Prometheus exporter, regardless of their origin, are prefixed with `otelcol_`.
221221
This includes metrics from both Collector components and instrumentation
222222
libraries. {{% /alert %}}
223223

224-
{{< comment >}}
224+
{{% comment %}}
225225

226226
To compile this list, configure a Collector instance to emit its own metrics to
227227
the localhost:8888/metrics endpoint. Select a metric and grep for it in the
@@ -234,7 +234,7 @@ the .go file that contains the list of metrics. In the case of
234234
Note that the Collector's internal metrics are defined in several different
235235
files in the repository.
236236

237-
{{< /comment >}}
237+
{{% /comment %}}
238238

239239
#### `basic`-level metrics
240240

‎content/en/docs/demo/docker-deployment.md

+6-6
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ cSpell:ignore: otlphttp spanmetrics tracetest tracetesting
3030

3131
3. Start the demo[^1]:
3232

33-
{{< tabpane text=true >}} {{% tab Make %}}
33+
{{% tabpane text=true %}} {{% tab Make %}}
3434

3535
```shell
3636
make start
@@ -42,11 +42,11 @@ make start
4242
docker compose up --force-recreate --remove-orphans --detach
4343
```
4444

45-
{{% /tab %}} {{< /tabpane >}}
45+
{{% /tab %}} {{% /tabpane %}}
4646

4747
4. (Optional) Enable API observability-driven testing[^1]:
4848

49-
{{< tabpane text=true >}} {{% tab Make %}}
49+
{{% tabpane text=true %}} {{% tab Make %}}
5050

5151
```shell
5252
make run-tracetesting
@@ -58,7 +58,7 @@ make run-tracetesting
5858
docker compose -f docker-compose-tests.yml run traceBasedTests
5959
```
6060

61-
{{% /tab %}} {{< /tabpane >}}
61+
{{% /tab %}} {{% /tabpane %}}
6262

6363
## Verify the web store and Telemetry
6464

@@ -80,7 +80,7 @@ variable before starting the demo.
8080

8181
- For example, to use port 8081[^1]:
8282

83-
{{< tabpane text=true >}} {{% tab Make %}}
83+
{{% tabpane text=true %}} {{% tab Make %}}
8484

8585
```shell
8686
ENVOY_PORT=8081 make start
@@ -92,7 +92,7 @@ ENVOY_PORT=8081 make start
9292
ENVOY_PORT=8081 docker compose up --force-recreate --remove-orphans --detach
9393
```
9494

95-
{{% /tab %}} {{< /tabpane >}}
95+
{{% /tab %}} {{% /tabpane %}}
9696

9797
## Bring your own backend
9898

‎content/en/docs/languages/cpp/exporters.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ Make sure that you have set the right cmake build variables while
2828

2929
Next, configure the exporter to point at an OTLP endpoint in your code.
3030

31-
{{< tabpane text=true >}} {{% tab "HTTP/Proto" %}}
31+
{{% tabpane text=true %}} {{% tab "HTTP/Proto" %}}
3232

3333
```cpp
3434
#include "opentelemetry/exporters/otlp/otlp_http_exporter_factory.h"
@@ -195,7 +195,7 @@ void InitLogger()
195195
}
196196
```
197197

198-
{{% /tab %}} {{< /tabpane >}}
198+
{{% /tab %}} {{% /tabpane %}}
199199

200200
### Console
201201

@@ -355,7 +355,7 @@ void InitTracer()
355355
356356
{{% docs/languages/exporters/outro python `https://opentelemetry-cpp.readthedocs.io/en/latest/otel_docs/classopentelemetry_1_1sdk_1_1trace_1_1SpanExporter.html` %}}
357357
358-
{{< tabpane text=true >}} {{% tab Batch %}}
358+
{{% tabpane text=true %}} {{% tab Batch %}}
359359
360360
```cpp
361361
#include "opentelemetry/exporters/otlp/otlp_http_exporter_factory.h"
@@ -382,6 +382,6 @@ auto exporter = opentelemetry::exporter::otlp::OtlpHttpExporterFactory::Create(
382382
auto processor = opentelemetry::sdk::trace::SimpleSpanProcessorFactory::Create(std::move(exporter));
383383
```
384384

385-
{{< /tab >}} {{< /tabpane>}}
385+
{{% /tab %}} {{% /tabpane%}}
386386

387387
{{% /docs/languages/exporters/outro %}}

0 commit comments

Comments
 (0)