Skip to content

Commit 9fbbc23

Browse files
chalinchalin
authored
Add ecosystem section (#2185)
1 parent 38e37c4 commit 9fbbc23

File tree

18 files changed

+59
-68
lines changed

18 files changed

+59
-68
lines changed

‎.github/CODEOWNERS

+1-1
Original file line numberDiff line numberDiff line change
@@ -30,5 +30,5 @@ content/en/docs/instrumentation/rust/ @open-telemetry/docs-approvers @open-tele
3030
content/en/docs/instrumentation/swift/ @open-telemetry/docs-approvers @open-telemetry/swift-maintainers @open-telemetry/swift-approvers
3131
content/en/docs/k8s-operator @open-telemetry/operator-approvers @open-telemetry/operator-maintainers
3232
content/en/blog/ @open-telemetry/docs-approvers @open-telemetry/blog-approvers
33-
content/en/community/demo/ @open-telemetry/demo-approvers @open-telemetry/demo-maintainers
3433
content/en/community/end-user/ @open-telemetry/end-user-wg
34+
content/en/ecosystem/demo/ @open-telemetry/demo-approvers @open-telemetry/demo-maintainers

‎content/en/_index.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ developer_note:
1414
<div class="l-primary-buttons mt-5">
1515

1616
- [Learn more](/docs/concepts/)
17-
- [Try the demo](/community/demo/)
17+
- [Try the demo](/ecosystem/demo/)
1818

1919
</div>
2020

@@ -57,10 +57,10 @@ Installation and integration can be as simple as a few lines of code.
5757

5858
{{% /blocks/feature %}}
5959

60-
{{% blocks/feature icon="fab fa-github" title="Open Source, Vendor Neutral" url="https://github.com/open-telemetry"%}}
60+
{{% blocks/feature icon="fab fa-github" title="Open Source, Vendor Neutral" %}}
6161

6262
100% Free and Open Source, OpenTelemetry is adopted and supported by
63-
[industry leaders](/vendors) in the observability space.
63+
[industry leaders](/ecosystem/vendors/) in the observability space.
6464

6565
{{% /blocks/feature %}}
6666

‎content/en/blog/2022/troubleshooting-nodejs.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -364,7 +364,7 @@ distributions can save you time and effort:
364364
- Up to date with latest OpenTelemetry versions
365365
- Implementing best practices and avoiding the pitfalls mentioned above
366366

367-
For a list of OpenTelemetry vendors, see [Vendors](/vendors/).
367+
For a list of OpenTelemetry vendors, see [Vendors](/ecosystem/vendors/).
368368

369369
_A version of this article was [originally posted][] on the Aspecto blog._
370370

‎content/en/community/_index.md

+3-4
Original file line numberDiff line numberDiff line change
@@ -20,8 +20,7 @@ improve our workflow and more easily manage a community project. [Read
2020
more](https://github.com/open-telemetry/community#special-interest-groups) from
2121
our [community repo](https://github.com/open-telemetry/community).
2222

23-
## Open Source Collaboration
23+
## Ecosystem
2424

25-
OpenTelemetry collaborates and integrates with other open source projects
26-
including Fluent Bit, Jaeger, Kubernetes, Prometheus, OpenMetrics, and W3C.
27-
[Read more](/integrations/).
25+
Looking for components, examples, integrations and more? See
26+
[Ecosystem](/ecosystem).

‎content/en/docs/_index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ for instrumenting, generating, collecting, and exporting telemetry data such as
1010
[traces](concepts/observability-primer/#distributed-traces),
1111
[metrics](concepts/observability-primer/#reliability--metrics),
1212
[logs](concepts/observability-primer/#logs). As an industry-standard it is
13-
[natively supported by a number of vendors](/vendors).
13+
[natively supported by a number of vendors](/ecosystem/vendors/).
1414

1515
![OpenTelemetry Reference Architecture](/img/otel_diagram.png)
1616

‎content/en/docs/concepts/distributions.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -39,16 +39,16 @@ Distributions would broadly fall into the following categories:
3939
instrumentation libraries or vendor exporters not upstreamed to the
4040
OpenTelemetry project.
4141
- **"Minus":** These distributions provide a reduced set of functionality from
42-
upstream. Examples of this would include the removal of
42+
upstream. Examples of this would include the removal of
4343
instrumentation libraries or receivers/processors/exporters/extensions found
4444
in the OpenTelemetry Collector project. These distributions may be provided to
4545
increase supportability and security considerations.
4646

4747
## Who would create a distribution?
4848

49-
Anyone could create a distribution. Today, several [vendors](../../../vendors)
49+
Anyone could create a distribution. Today, several [vendors](/ecosystem/vendors/)
5050
offer distributions. In addition, end-users may consider creating a distribution
51-
if they wish to use components in the [Registry](../../../registry) that are not
51+
if they wish to use components in the [Registry](/registry) that are not
5252
upstreamed to the OpenTelemetry project.
5353

5454
## Contribution or distribution?

‎content/en/docs/concepts/instrumenting.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -113,9 +113,9 @@ as a proxy or sidecar to your service instances or run on a separate host. The
113113
Collector can then be configured to forward and export this data to your choice
114114
of analysis tools.
115115

116-
In addition to open source tools such as Jaeger or Prometheus, a growing list of
117-
companies support ingesting telemetry data from OpenTelemetry. Please see
118-
[this page](/vendors) for more details.
116+
In addition to open-source tools such as Jaeger or Prometheus, a growing list of
117+
companies support ingesting telemetry data from OpenTelemetry. For details, see
118+
[Vendors](/ecosystem/vendors/).
119119

120120
[automatic instrumentation]:
121121
/docs/reference/specification/glossary/#automatic-instrumentation

‎content/en/docs/concepts/what-is-opentelemetry.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ Observability back-end (i.e. open source or commercial vendor).
7070
## What can OpenTelemetry do for me?
7171

7272
OTel has broad industry support and adoption from cloud providers,
73-
[vendors](/vendors) and end users. It provides you with:
73+
[vendors](/ecosystem/vendors/) and end users. It provides you with:
7474

7575
- A single, vendor-agnostic instrumentation library
7676
[per language](/docs/instrumentation) with support for both automatic and

‎content/en/docs/getting-started/_index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,6 @@ OpenTelemetry looks like.
1111

1212
If none of the roles below are applicable to you, [let us know][]!
1313

14-
[opentelemetry demo]: /community/demo
14+
[opentelemetry demo]: /ecosystem/demo/
1515
[let us know]:
1616
https://github.com/open-telemetry/opentelemetry.io/issues/new?title=Add%20a%20new%20persona:%20My%20Persona&body=Provide%20a%20description%20of%20your%20role%20and%20responsibilities%20and%20what%20your%20observability%20goals%20are

‎content/en/docs/getting-started/demo.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Demo
3-
manualLink: /community/demo/
3+
manualLink: /ecosystem/demo/
44
_build: { render: link }
55
weight: 5
66
---

‎content/en/docs/getting-started/ops.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -19,5 +19,5 @@ learn the following:
1919

2020
If you are looking for a set of applications to try things out, you will find
2121
our official
22-
[OpenTelemetry Demo](/community/demo)
22+
[OpenTelemetry Demo](/ecosystem/demo/)
2323
useful!

‎content/en/docs/instrumentation/python/automatic/agent-config.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -30,8 +30,8 @@ Here's an explanation of what each configuration does:
3030
* `traces_exporter` specifies which trace exporter to use. In this case, traces are being exported to `console` (stdout) and to `otlp`. The `otlp` option tells `opentelemetry-instrument` to send it to an endpoint that accepts OTLP via gRPC. The full list of available options for traces_exporter can be found [here](https://github.com/open-telemetry/opentelemetry-python-contrib/tree/main/opentelemetry-instrumentation).
3131
* `otlp` used above for `traces_exporter` is the equivalent of using `otlp_proto_grpc`. To send traces via HTTP instead of gRPC, replace `otlp_proto_grpc` (or `otlp`) with `otlp_proto_http`.
3232
* `metrics_exporter` specifies which metrics exporter to use. In this case, metrics are being exported to `console` (stdout). It is currently required for your to specify a metrics exporter. If you aren't exporting metrics, specify `none` as the value instead.
33-
* `service_name` sets the name of the service associated to the trace, and is sent to your [Observability back-end](/vendors).
34-
* `exporter_otlp_endpoint` tells `opentelemetry-instrument` to send the traces to the given [Observability back-end's](/vendors) endpiont via gRPC, or directly to the [OpenTelemetry Collector](/docs/collector/).
33+
* `service_name` sets the name of the service associated to the trace, and is sent to your [Observability back-end](/ecosystem/vendors/).
34+
* `exporter_otlp_endpoint` tells `opentelemetry-instrument` to send the traces to the given [Observability back-end's](/ecosystem/vendors/) endpiont via gRPC, or directly to the [OpenTelemetry Collector](/docs/collector/).
3535
* `exporter_otlp_headers` is required depending on your chosen Observability back-end. More info exporter OTLP headers be found [here](/docs/concepts/sdk-configuration/otlp-exporter-configuration/#otel_exporter_otlp_headers).
3636
* If `exporter_otlp_endpoint` is omitted, the agent assumes that you are using the default Collector gRPC endpoint, `0.0.0.0:4317`. The above command is the equivalent of saying:
3737

@@ -49,7 +49,7 @@ Here's an explanation of what each configuration does:
4949

5050
### Environment Variables
5151

52-
In some cases, configuring via [Environment Variables](/docs/concepts/sdk-configuration/) is more preferred. Any setting configurable with a configuration property can also be configured with an Environment Variable.
52+
In some cases, configuring via [Environment Variables](/docs/concepts/sdk-configuration/) is more preferred. Any setting configurable with a configuration property can also be configured with an Environment Variable.
5353

5454
You can apply the following steps to determine the correct name mapping of the desired configuration property:
5555

‎content/en/ecosystem/_index.md

+9
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
---
2+
title: OpenTelemetry Ecosystem
3+
linkTitle: Ecosystem
4+
description: >-
5+
OpenTelemetry's thriving ecosystem of components, examples, integrations and
6+
vendors
7+
cascade: { type: docs }
8+
menu: { main: { weight: 20 } }
9+
---

‎content/en/community/demo.md renamed to ‎content/en/ecosystem/demo.md

+2
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,11 @@ linkTitle: Demo
44
description:
55
The OpenTelemetry Demo is a microservice-based distributed system intended to illustrate the implementation of OpenTelemetry in a near real-world environment.
66
aliases:
7+
- /community/demo
78
- /docs/demo
89
- /docs/getting-started/demo
910
- /docs/opentelemetry-demo
11+
weight: 10
1012
---
1113

1214
The [OpenTelemetry Demo](https://github.com/open-telemetry/opentelemetry-demo)

‎content/en/integrations.md renamed to ‎content/en/ecosystem/integrations.md

+12-28
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,16 @@
11
---
22
title: Integrations
3+
description: OpenTelemetry integrations with other open-source projects
4+
aliases: [/integrations]
35
---
46

5-
{{% blocks/lead color="primary" %}}
6-
# {{% param title %}}
7-
87
OpenTelemetry integrates with or is integrated into various open source projects.
9-
{{% /blocks/lead %}}
10-
11-
{{< row >}}
12-
{{< column >}}
13-
{{% blocks/section type="section" color="white" %}}
148

159
## Within OpenTelemetry
1610

1711
OpenTelemetry provides integration with the following open source projects.
18-
<br/>
1912

20-
| External Project | OpenTelemetry Supported Components |
13+
| External Project* | OpenTelemetry Supported Components |
2114
| ---------------- | ---------------------------------- |
2215
| [Apache Kafka](https://kafka.apache.org/) | Collector |
2316
| [Elasticsearch](https://github.com/elastic/elasticsearch) | Collector, C++, Java, Python |
@@ -26,32 +19,23 @@ OpenTelemetry provides integration with the following open source projects.
2619
| [Jaeger](https://www.jaegertracing.io/) | Collector, DotNet, Go, Java, JS, PHP, Python, Ruby, Rust |
2720
| [OpenCensus](https://opencensus.io/) | Collector, Python |
2821
| [OpenTracing](https://opentracing.io/) | DotNet, Go, Java, JS, Python, Ruby
29-
| [OpenMetrics](https://openmetrics.io/)\* | Collector |
30-
| [Prometheus](https://prometheus.io/)\* | Collector, C++, Go, Java, JS, Rust |
22+
| [OpenMetrics](https://openmetrics.io/) [^partial-support] | Collector |
23+
| [Prometheus](https://prometheus.io/) [^partial-support] | Collector, C++, Go, Java, JS, Rust |
3124
| [Zipkin](https://zipkin.io/) | Collector, DotNet, Go, Java, JS, PHP, Python, Rust |
3225
| [W3C trace-context](https://www.w3.org/TR/trace-context/) | DotNet, Go, Java, JS, Python, Ruby |
3326

34-
\* Projects only partially supported at this time. Full support coming soon!
35-
3627
_Projects are listed alphabetically_
37-
{{% /blocks/section %}}
38-
{{< /column >}}
39-
{{< column >}}
40-
{{% blocks/section type="section" color="white" %}}
4128

4229
## Outside OpenTelemetry
4330

4431
The following open source projects use OpenTelemetry components.
45-
<br/>
4632

47-
| External Project | Applicable OpenTelemetry Components |
48-
| ---------------- | ----------------------------------- |
49-
| [Jaeger](https://www.jaegertracing.io/docs/1.21/opentelemetry/)\* | Collector |
50-
| [Spring Sleuth](https://github.com/spring-cloud-incubator/spring-cloud-sleuth-otel/)\* | Java |
33+
| External Project | Applicable OpenTelemetry Components |
34+
| ---------------- | ----------------------------------- |
35+
| [Jaeger](https://www.jaegertracing.io/docs/1.21/opentelemetry/) [^not-ga] | Collector |
36+
| [Spring Sleuth](https://github.com/spring-cloud-incubator/spring-cloud-sleuth-otel/) [^not-ga] | Java |
5137

52-
\* Projects offering experimental or beta support. GA support coming soon!
5338

54-
_Projects are listed alphabetically_
55-
{{% /blocks/section %}}
56-
{{< /column >}}
57-
{{< /row >}}
39+
\* _Projects are listed alphabetically_.
40+
[^partial-support]: Projects only partially supported at this time. Full support coming soon!
41+
[^not-ga]: Projects offering experimental or beta support. GA support coming soon!

‎content/en/ecosystem/registry.md

+6
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
---
2+
title: Registry
3+
manualLink: /registry/
4+
_build: { render: link }
5+
weight: 20
6+
---

‎content/en/vendors.md renamed to ‎content/en/ecosystem/vendors.md

+8-16
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,17 @@
11
---
2-
title: Vendor support
2+
title: Vendors
3+
description: Vendors who natively support OpenTelemetry
4+
aliases: [/vendors]
35
spelling:
46
cSpell:ignore appdynamics aria aspecto bution datadoghq distri dynatrace grafana
57
cSpell:ignore Instana lightstep logz logicmonitor lumigo promscale
68
cSpell:ignore sentrysoftware signoz solarwinds splunk sumologic uptrace vmware wavefront
79
---
810

9-
{{% blocks/lead color="primary" %}}
10-
11-
# {{% param title %}}
12-
1311
[Distributions](/docs/concepts/distributions/) and vendors who natively support
1412
OpenTelemetry in their commercial products.
1513

16-
{{% /blocks/lead %}}
17-
18-
{{% blocks/section type="section" color="white" %}}
19-
20-
| Company | Distri&shy;bution | Native OTLP | Learn more |
14+
| Company* | Distri&shy;bution | Native OTLP | Learn more |
2115
| -------------------------- | ----------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
2216
| AppDynamics (Cisco) | Yes | Yes | [docs.appdynamics.com/...](https://docs.appdynamics.com/latest/en/application-monitoring/appdynamics-for-opentelemetry) |
2317
| Aria by VMware (Wavefront) | No | Yes | [docs.wavefront.com/...](https://docs.wavefront.com/opentelemetry_tracing.html) |
@@ -34,8 +28,8 @@ OpenTelemetry in their commercial products.
3428
| Grafana Labs | No | Yes | [grafana.com/...](https://grafana.com/oss/opentelemetry/)
3529
| Helios | Yes | Yes | [gethelios.dev](https://gethelios.dev/)
3630
| Honeycomb | Yes | Yes | [docs.honeycomb.io/...](https://docs.honeycomb.io/getting-data-in/) |
37-
| Instana | No | Yes | [ibm.com/docs/...](https://www.ibm.com/docs/en/obi/current?topic=apis-opentelemetry) |
38-
| KloudFuse | No | Yes | [kloudfuse.com](https://kloudfuse.atlassian.net/wiki/spaces/EX/pages/753860609/APM#Sending-traces-to-Kloudfuse-data-plane%3A) |
31+
| Instana | No | Yes | [ibm.com/docs/...](https://www.ibm.com/docs/en/obi/current?topic=apis-opentelemetry) |
32+
| KloudFuse | No | Yes | [kloudfuse.com](https://kloudfuse.atlassian.net/wiki/spaces/EX/pages/753860609/APM#Sending-traces-to-Kloudfuse-data-plane%3A) |
3933
| Lightstep | Yes | Yes | [github.com/lightstep](https://github.com/lightstep?q=launcher) |
4034
| LogicMonitor | Yes | Yes | [logicmonitor.com/...](https://www.logicmonitor.com/support/tracing/getting-started-with-tracing) |
4135
| Logz.io | Yes | No | [docs.logz.io/...](https://docs.logz.io/shipping/tracing-sources/opentelemetry.html#overview) |
@@ -48,9 +42,7 @@ OpenTelemetry in their commercial products.
4842
| SolarWinds | Yes | Yes | [documentation.solarwinds.com/...](https://documentation.solarwinds.com/en/success_center/observability/default.htm#cshid=third-otel-integration) |
4943
| Splunk | Yes | Yes | [splunk.com/blog/...](https://www.splunk.com/en_us/blog/conf-splunklive/announcing-native-opentelemetry-support-in-splunk-apm.html) |
5044
| Sumo Logic | Yes | Yes | [help.sumologic.com/](https://help.sumologic.com/docs/apm/traces/quickstart/) |
51-
| Uptrace | Yes | Yes | [uptrace.dev](https://uptrace.dev)
45+
| Uptrace | Yes | Yes | [uptrace.dev](https://uptrace.dev)
5246
|
5347

54-
_Vendors are listed alphabetically_
55-
56-
{{% /blocks/section %}}
48+
\* _Vendors are listed alphabetically_.

‎content/en/registry/_index.md

-1
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
---
22
title: Registry
33
outputs: [html, json]
4-
menu: { main: { weight: 20 } }
54
---
65

76
{{% blocks/lead color="primary" %}}

0 commit comments

Comments
 (0)