open-telemetry
/
opentelemetry.io
mirror of https://github.com/open-telemetry/opentelemetry.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

fix broken links (#2105)

This commit is contained in:
Alex Boten 2022-12-15 10:41:21 -08:00 committed by GitHub
parent 3640ea938a
commit 27026bf419
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
14 changed files with 21 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/en/docs/collector/_index.md
View File

@ -6,7 +6,7 @@ spelling: cSpell:ignore Otel
aliases: [/docs/collector/about]
---
![OpenTelemetry Collector diagram with Jaeger, OTLP and Prometheus integration](https://raw.github.com/open-telemetry/opentelemetry.io/main/iconography/Otel_Collector.svg)
![OpenTelemetry Collector diagram with Jaeger, OTLP and Prometheus integration](https://raw.githubusercontent.com/open-telemetry/opentelemetry.io/main/iconography/Otel_Collector.svg)
## Introduction

12
content/en/docs/collector/configuration.md
View File

@ -13,11 +13,11 @@ Please be sure to review the following documentation:
The Collector consists of three components that access telemetry data:
- <img width="32" src="https://raw.github.com/open-telemetry/opentelemetry.io/main/iconography/32x32/Receivers.svg"></img>
- <img width="32" src="https://raw.githubusercontent.com/open-telemetry/opentelemetry.io/main/iconography/32x32/Receivers.svg"></img>
[Receivers](#receivers)
- <img width="32" src="https://raw.github.com/open-telemetry/opentelemetry.io/main/iconography/32x32/Processors.svg"></img>
- <img width="32" src="https://raw.githubusercontent.com/open-telemetry/opentelemetry.io/main/iconography/32x32/Processors.svg"></img>
[Processors](#processors)
- <img width="32" src="https://raw.github.com/open-telemetry/opentelemetry.io/main/iconography/32x32/Exporters.svg"></img>
- <img width="32" src="https://raw.githubusercontent.com/open-telemetry/opentelemetry.io/main/iconography/32x32/Exporters.svg"></img>
[Exporters](#exporters)
These components once configured must be enabled via pipelines within the
@ -120,7 +120,7 @@ service:
## Receivers
<img width="35" src="https://raw.github.com/open-telemetry/opentelemetry.io/main/iconography/32x32/Receivers.svg"></img>
<img width="35" src="https://raw.githubusercontent.com/open-telemetry/opentelemetry.io/main/iconography/32x32/Receivers.svg"></img>
A receiver, which can be push or pull based, is how data gets into the
Collector. Receivers may support one or more [data sources](../../concepts/signals).
@ -196,7 +196,7 @@ receivers:
## Processors
<img width="35" src="https://raw.github.com/open-telemetry/opentelemetry.io/main/iconography/32x32/Processors.svg"></img>
<img width="35" src="https://raw.githubusercontent.com/open-telemetry/opentelemetry.io/main/iconography/32x32/Processors.svg"></img>
Processors are run on data between being received and being exported.
Processors are optional though
@ -277,7 +277,7 @@ processors:
## Exporters
<img width="35" src="https://raw.github.com/open-telemetry/opentelemetry.io/main/iconography/32x32/Exporters.svg"></img>
<img width="35" src="https://raw.githubusercontent.com/open-telemetry/opentelemetry.io/main/iconography/32x32/Exporters.svg"></img>
An exporter, which can be push or pull based, is how you send data to one or
more backends/destinations. Exporters may support one or more

6
content/en/docs/concepts/data-collection.md
View File

@ -33,12 +33,12 @@ For information on how to use the Collector see the
The Collector is made up of the following components:
- <img width="32" src="https://raw.github.com/open-telemetry/opentelemetry.io/main/iconography/32x32/Receivers.svg"></img>
- <img width="32" src="https://raw.githubusercontent.com/open-telemetry/opentelemetry.io/main/iconography/32x32/Receivers.svg"></img>
`receivers`: How to get data into the Collector; these can be push or pull
based
- <img width="32" src="https://raw.github.com/open-telemetry/opentelemetry.io/main/iconography/32x32/Processors.svg"></img>
- <img width="32" src="https://raw.githubusercontent.com/open-telemetry/opentelemetry.io/main/iconography/32x32/Processors.svg"></img>
`processors`: What to do with received data
- <img width="32" src="https://raw.github.com/open-telemetry/opentelemetry.io/main/iconography/32x32/Exporters.svg"></img>
- <img width="32" src="https://raw.githubusercontent.com/open-telemetry/opentelemetry.io/main/iconography/32x32/Exporters.svg"></img>
`exporters`: Where to send received data; these can be push or pull based
These components are enabled through `pipelines`. Multiple instances of

2
content/en/docs/concepts/instrumenting-library.md
View File

@ -124,7 +124,7 @@ issues.
## What to instrument
![Nested database and HTTP spans in Jaeger UI](https://raw.github.com/open-telemetry/opentelemetry.io/main/iconography/Instrumenting_Library_nested_spans.svg)
![Nested database and HTTP spans in Jaeger UI](https://raw.githubusercontent.com/open-telemetry/opentelemetry.io/main/iconography/Instrumenting_Library_nested_spans.svg)
### Public APIs

2
content/en/docs/instrumentation/cpp/_index.md
View File

@ -3,7 +3,7 @@ title: C++
weight: 11
description: >
<img width="35"
src="https://raw.github.com/open-telemetry/opentelemetry.io/main/iconography/32x32/C++_SDK.svg"
src="https://raw.githubusercontent.com/open-telemetry/opentelemetry.io/main/iconography/32x32/C++_SDK.svg"
alt="C++"></img> A language-specific implementation of OpenTelemetry in C++.
---

2
content/en/docs/instrumentation/erlang/_index.md
View File

@ -3,7 +3,7 @@ title: Erlang/Elixir
weight: 14
description: >
<img width="35"
src="https://raw.github.com/open-telemetry/opentelemetry.io/main/iconography/32x32/Erlang_SDK.svg"
src="https://raw.githubusercontent.com/open-telemetry/opentelemetry.io/main/iconography/32x32/Erlang_SDK.svg"
alt="Erlang/Elixir"></img>
A language-specific implementation of OpenTelemetry in Erlang/Elixir.
---

2
content/en/docs/instrumentation/java/_index.md
View File

@ -2,7 +2,7 @@
title: Java
description: >-
<img width="35"
src="https://raw.github.com/open-telemetry/opentelemetry.io/main/iconography/32x32/Java_SDK.svg"
src="https://raw.githubusercontent.com/open-telemetry/opentelemetry.io/main/iconography/32x32/Java_SDK.svg"
alt="Java"></img>
A language-specific implementation of OpenTelemetry in Java.
aliases: [/java, /java/metrics, /java/tracing]

2
content/en/docs/instrumentation/js/_index.md
View File

@ -2,7 +2,7 @@
title: JavaScript
description: >-
<img width="35"
src="https://raw.github.com/open-telemetry/opentelemetry.io/main/iconography/32x32/JS_SDK.svg"
src="https://raw.githubusercontent.com/open-telemetry/opentelemetry.io/main/iconography/32x32/JS_SDK.svg"
alt="JavaScript"></img>
A language-specific implementation of OpenTelemetry in JavaScript (for Node.js & the browser).
aliases: [/js, /js/metrics, /js/tracing]

2
content/en/docs/instrumentation/net/_index.md
View File

@ -2,7 +2,7 @@
title: .NET
description: >
<img width="35"
src="https://raw.github.com/open-telemetry/opentelemetry.io/main/iconography/32x32/.NET.svg"
src="https://raw.githubusercontent.com/open-telemetry/opentelemetry.io/main/iconography/32x32/.NET.svg"
alt=".NET"></img>
A language-specific implementation of OpenTelemetry in .NET.
aliases: [/csharp, /csharp/metrics, /csharp/tracing]

2
content/en/docs/instrumentation/php/_index.md
View File

@ -2,7 +2,7 @@
title: PHP
description: >-
<img width="35"
src="https://raw.github.com/open-telemetry/opentelemetry.io/main/iconography/32x32/PHP.svg"
src="https://raw.githubusercontent.com/open-telemetry/opentelemetry.io/main/iconography/32x32/PHP.svg"
alt="PHP"></img>
A language-specific implementation of OpenTelemetry in PHP.
weight: 21

2
content/en/docs/instrumentation/python/_index.md
View File

@ -2,7 +2,7 @@
title: Python
description: >-
<img width="35"
src="https://raw.github.com/open-telemetry/opentelemetry.io/main/iconography/32x32/Python_SDK.svg"
src="https://raw.githubusercontent.com/open-telemetry/opentelemetry.io/main/iconography/32x32/Python_SDK.svg"
alt="Python"></img>
A language-specific implementation of OpenTelemetry in Python.
aliases: [/python, /python/metrics, /python/tracing]

2
content/en/docs/instrumentation/ruby/_index.md
View File

@ -1,7 +1,7 @@
---
title: Ruby
description: >
<img width="35" src="https://raw.github.com/open-telemetry/opentelemetry.io/main/iconography/32x32/Ruby_SDK.svg" alt="Ruby"></img>
<img width="35" src="https://raw.githubusercontent.com/open-telemetry/opentelemetry.io/main/iconography/32x32/Ruby_SDK.svg" alt="Ruby"></img>
A language-specific implementation of OpenTelemetry in Ruby.
aliases: [/ruby, /ruby/metrics, /ruby/tracing]
weight: 24

2
content/en/docs/instrumentation/rust/_index.md
View File

@ -2,7 +2,7 @@
title: Rust
description: >-
<img width="35"
src="https://raw.github.com/open-telemetry/opentelemetry.io/main/iconography/32x32/Rust.svg"
src="https://raw.githubusercontent.com/open-telemetry/opentelemetry.io/main/iconography/32x32/Rust.svg"
alt="Rust"></img>
A language-specific implementation of OpenTelemetry in Rust.
weight: 26

2
content/en/docs/instrumentation/swift/_index.md
View File

@ -3,7 +3,7 @@ title: Swift
weight: 28
description: >-
<img width="35"
src="https://raw.github.com/open-telemetry/opentelemetry.io/main/iconography/32x32/Swift.svg"
src="https://raw.githubusercontent.com/open-telemetry/opentelemetry.io/main/iconography/32x32/Swift.svg"
alt="Swift"></img>
A language-specific implementation of OpenTelemetry in Swift.
---