Mention logs as an option for OTLP exporter (#2488)
* Mention logs as an option for OTLP exporter Logs exporter recently landed here: https://github.com/open-telemetry/opentelemetry-dotnet/pull/1964 * Mention logs support, requiring separate package * Relative link within repo * Create README.md * Fix relative path and line length * Fix relative path * NuGet badges Co-authored-by: Alan West <3676547+alanwest@users.noreply.github.com> * Use a file name to fix path warning * Prereq is implicit already w/NuGet dependency Co-authored-by: Cijo Thomas <cithomas@microsoft.com> Co-authored-by: Alan West <3676547+alanwest@users.noreply.github.com>
This commit is contained in:
parent
c7a27dca06
commit
f8f201863a
|
|
@ -0,0 +1,11 @@
|
|||
# OTLP Logs Exporter for OpenTelemetry .NET
|
||||
|
||||
[](https://www.nuget.org/packages/OpenTelemetry.Exporter.OpenTelemetryProtocol.Logs)
|
||||
[](https://www.nuget.org/packages/OpenTelemetry.Exporter.OpenTelemetryProtocol.Logs)
|
||||
|
||||
[The OTLP (OpenTelemetry Protocol) exporter](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/protocol/exporter.md)
|
||||
implementation for logs.
|
||||
|
||||
## Prerequisite
|
||||
|
||||
* [Get OpenTelemetry Collector](https://opentelemetry.io/docs/collector/)
|
||||
|
|
@ -54,6 +54,16 @@ values of the `OtlpExporterOptions`
|
|||
| `OTEL_EXPORTER_OTLP_TIMEOUT` | `TimeoutMilliseconds` |
|
||||
| `OTEL_EXPORTER_OTLP_PROTOCOL` | `Protocol` (grpc or http/protobuf)|
|
||||
|
||||
## OTLP Logs
|
||||
|
||||
This package currently only supports exporting traces and metrics. Once the
|
||||
[OTLP log data model](https://github.com/open-telemetry/opentelemetry-proto#maturity-level)
|
||||
is deemed stable, the OTLP log exporter will be folded into this package.
|
||||
|
||||
In the meantime, support for exporting logs is provided by installing the
|
||||
[`OpenTelemetry.Exporter.OpenTelemetryProtocol.Logs`](../OpenTelemetry.Exporter.OpenTelemetryProtocol.Logs/README.md)
|
||||
package.
|
||||
|
||||
## Special case when using insecure channel
|
||||
|
||||
If your application is targeting .NET Core 3.1, and you are using an insecure
|
||||
|
|
|
|||
Loading…
Reference in New Issue