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

Remove Jaeger Exporter - part 1: remove references in docs (#4777)

This commit is contained in:
xiang17 2023-08-18 11:17:37 -07:00 committed by GitHub
parent f6a1c04e81
commit d9d0e24412
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
5 changed files with 25 additions and 32 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
README.md
View File

@ -69,7 +69,6 @@ libraries](https://github.com/open-telemetry/opentelemetry-specification/blob/ma
* [Console](./src/OpenTelemetry.Exporter.Console/README.md)
* [In-memory](./src/OpenTelemetry.Exporter.InMemory/README.md)
* [Jaeger](./src/OpenTelemetry.Exporter.Jaeger/README.md)
* [OTLP](./src/OpenTelemetry.Exporter.OpenTelemetryProtocol/README.md)
(OpenTelemetry Protocol)
* [Prometheus AspNetCore](./src/OpenTelemetry.Exporter.Prometheus.AspNetCore/README.md)

2
VERSIONING.md
View File

@ -28,7 +28,7 @@ versions [1.1.0, 2.0.0).
Core components refer to the set of components which are required as per the
spec. This includes API, SDK, and exporters which are required by the
specification. These exporters are OTLP, Jaeger, Zipkin, Console and InMemory.
specification. These exporters are OTLP, Zipkin, Console and InMemory.
The core components are always versioned and released together. For example, if
Zipkin exporter has a bug fix and is released as 1.0.1, then all other core

51
docs/trace/customizing-the-sdk/README.md
View File

@ -268,15 +268,15 @@ var tracerProvider = Sdk.CreateTracerProviderBuilder()
It is also common for exporters to provide their own extensions to simplify
registration. The snippet below shows how to add the
[JaegerExporter](../../../src/OpenTelemetry.Exporter.Jaeger/README.md) to the
provider before it is built.
[OtlpExporter](../../../src/OpenTelemetry.Exporter.OpenTelemetryProtocol/README.md)
to the provider before it is built.
```csharp
using OpenTelemetry;
using OpenTelemetry.Trace;
var tracerProvider = Sdk.CreateTracerProviderBuilder()
.AddJaegerExporter()
.AddOtlpExporter()
.Build();
```
@ -620,7 +620,7 @@ components.
Options classes can always be configured through code but users typically want to
control key settings through configuration.
The following example shows how to configure `JaegerExporterOptions` by binding
The following example shows how to configure `OtlpExporterOptions` by binding
to an `IConfiguration` section.
Json config file (usually appsettings.json):
@ -628,13 +628,8 @@ Json config file (usually appsettings.json):
```json
{
"OpenTelemetry": {
"Jaeger": {
"Protocol": "UdpCompactThrift"
"AgentHost": "localhost",
"AgentPort": 6831,
"BatchExportProcessorOptions": {
"ScheduledDelayMilliseconds": 5000
}
"Otlp": {
"Endpoint": "http://localhost:4317"
}
}
}
@ -645,11 +640,11 @@ Code:
```csharp
var appBuilder = WebApplication.CreateBuilder(args);
appBuilder.Services.Configure<JaegerExporterOptions>(
appBuilder.Configuration.GetSection("OpenTelemetry:Jaeger"));
appBuilder.Services.Configure<OtlpExporterOptions>(
appBuilder.Configuration.GetSection("OpenTelemetry:Otlp"));
appBuilder.Services.AddOpenTelemetry()
.WithTracing(builder => builder.AddJaegerExporter());
.WithTracing(builder => builder.AddOtlpExporter());
```
The OpenTelemetry .NET SDK supports running multiple `TracerProvider`s inside
@ -659,7 +654,7 @@ users to target configuration at specific components a "name" parameter is
typically supported on configuration extensions to control the options instance
used for the component being registered.
The below example shows how to configure two `JaegerExporter` instances inside a
The below example shows how to configure two `OtlpExporter` instances inside a
single `TracerProvider` sending to different ports.
Json config file (usually appsettings.json):
@ -667,12 +662,12 @@ Json config file (usually appsettings.json):
```json
{
"OpenTelemetry": {
"JaegerPrimary": {
"AgentPort": 1818
"OtlpPrimary": {
"Endpoint": "http://localhost:4317"
},
"OtlpSecondary": {
"Endpoint": "http://localhost:4327"
},
"JaegerSecondary": {
"AgentPort": 8818
}
}
}
```
@ -682,16 +677,16 @@ Code:
```csharp
var appBuilder = WebApplication.CreateBuilder(args);
appBuilder.Services.Configure<JaegerExporterOptions>(
"JaegerPrimary",
appBuilder.Configuration.GetSection("OpenTelemetry:JaegerPrimary"));
appBuilder.Services.Configure<OtlpExporterOptions>(
"OtlpPrimary",
appBuilder.Configuration.GetSection("OpenTelemetry:OtlpPrimary"));
appBuilder.Services.Configure<JaegerExporterOptions>(
"JaegerSecondary",
appBuilder.Configuration.GetSection("OpenTelemetry:JaegerSecondary"));
appBuilder.Services.Configure<OtlpExporterOptions>(
"OtlpSecondary",
appBuilder.Configuration.GetSection("OpenTelemetry:OtlpSecondary"));
appBuilder.Services.AddOpenTelemetry()
.WithTracing(builder => builder
.AddJaegerExporter(name: "JaegerPrimary", configure: null)
.AddJaegerExporter(name: "JaegerSecondary", configure: null));
.AddOtlpExporter(name: "OtlpPrimary", configure: null)
.AddOtlpExporter(name: "OtlpSecondary", configure: null));
```

1
docs/trace/extending-the-sdk/README.md
View File

@ -16,7 +16,6 @@ OpenTelemetry .NET SDK has provided the following built-in trace exporters:
* [Console](../../../src/OpenTelemetry.Exporter.Console/README.md)
* [InMemory](../../../src/OpenTelemetry.Exporter.InMemory/README.md)
* [Jaeger](../../../src/OpenTelemetry.Exporter.Jaeger/README.md)
* [OpenTelemetryProtocol](../../../src/OpenTelemetry.Exporter.OpenTelemetryProtocol/README.md)
* [Zipkin](../../../src/OpenTelemetry.Exporter.Zipkin/README.md)

2
docs/trace/getting-started-jaeger/README.md
View File

@ -142,7 +142,7 @@ Jaeger -->|http://localhost:16686/| JaegerUI["Browser<br/>(Jaeger UI)"]
## Final cleanup
In the end, remove the Console Exporter so we only have Jaeger Exporter in the
In the end, remove the Console Exporter so we only have OTLP Exporter in the
final application:
```csharp