add nugets

This commit is contained in:
master
2025-11-18 22:28:20 +02:00
parent 8355e2ff75
commit 77cee6a209
3645 changed files with 4373144 additions and 0 deletions

View File

@@ -0,0 +1,5 @@
{
"version": 2,
"contentHash": "Xt0qldi+iE2szGrM3jAqzEMEJd48YBtqI6mge0+ArXTZg3aTpRmyhL6CKKl3bLioaFSSVbBpEbPin8u6Z46Yrw==",
"source": "https://api.nuget.org/v3/index.json"
}

Binary file not shown.

View File

@@ -0,0 +1,201 @@
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

View File

@@ -0,0 +1,35 @@
<?xml version="1.0" encoding="utf-8"?>
<package xmlns="http://schemas.microsoft.com/packaging/2013/05/nuspec.xsd">
<metadata>
<id>OpenTelemetry.Api</id>
<version>1.12.0</version>
<authors>OpenTelemetry Authors</authors>
<requireLicenseAcceptance>true</requireLicenseAcceptance>
<license type="expression">Apache-2.0</license>
<licenseUrl>https://licenses.nuget.org/Apache-2.0</licenseUrl>
<icon>opentelemetry-icon-color.png</icon>
<readme>README.md</readme>
<projectUrl>https://opentelemetry.io/</projectUrl>
<description>OpenTelemetry .NET API</description>
<releaseNotes>For highlights and announcements see: https://github.com/open-telemetry/opentelemetry-dotnet/blob/core-1.12.0/RELEASENOTES.md.
For detailed changes see: https://github.com/open-telemetry/opentelemetry-dotnet/blob/core-1.12.0/src/OpenTelemetry.Api/CHANGELOG.md.</releaseNotes>
<copyright>Copyright The OpenTelemetry Authors</copyright>
<tags>Observability OpenTelemetry Monitoring Telemetry Tracing Metrics Logging</tags>
<repository type="git" url="https://github.com/open-telemetry/opentelemetry-dotnet" commit="a67acd87d5e4d437c5398664f75faa19494beb9c" />
<dependencies>
<group targetFramework=".NETFramework4.6.2">
<dependency id="System.Diagnostics.DiagnosticSource" version="9.0.0" exclude="Build,Analyzers" />
</group>
<group targetFramework="net8.0">
<dependency id="System.Diagnostics.DiagnosticSource" version="9.0.0" exclude="Build,Analyzers" />
</group>
<group targetFramework="net9.0">
<dependency id="System.Diagnostics.DiagnosticSource" version="9.0.0" exclude="Build,Analyzers" />
</group>
<group targetFramework=".NETStandard2.0">
<dependency id="System.Diagnostics.DiagnosticSource" version="9.0.0" exclude="Build,Analyzers" />
</group>
</dependencies>
</metadata>
</package>

View File

@@ -0,0 +1,555 @@
# OpenTelemetry .NET API
[![NuGet](https://img.shields.io/nuget/v/OpenTelemetry.Api.svg)](https://www.nuget.org/packages/OpenTelemetry.Api)
[![NuGet](https://img.shields.io/nuget/dt/OpenTelemetry.Api.svg)](https://www.nuget.org/packages/OpenTelemetry.Api)
* [Installation](#installation)
* [Introduction](#introduction)
* [Tracing API](#tracing-api)
* [Logging API](#logging-api)
* [Metrics API](#metrics-api)
* [Baggage API](#baggage-api)
* [Introduction to OpenTelemetry .NET Tracing
API](#introduction-to-opentelemetry-net-tracing-api)
* [Instrumenting a library/application with .NET Activity
API](#instrumenting-a-libraryapplication-with-net-activity-api)
* [Basic usage](#basic-usage)
* [Activity creation options](#activity-creation-options)
* [Adding Events](#adding-events)
* [Setting Status](#setting-status)
* [Instrumenting a library/application with OpenTelemetry.API
Shim](#instrumenting-using-opentelemetryapi-shim)
* [Troubleshooting](#troubleshooting)
* [References](#references)
## Installation
```shell
dotnet add package OpenTelemetry.Api
```
## Introduction
Application developers and library authors use OpenTelemetry API to instrument
their application/library. The API only surfaces necessary abstractions to
instrument an application/library. It does not address concerns like how
telemetry is exported to a specific telemetry backend, how to sample the
telemetry, etc. The API consists of [Tracing
API](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md),
[Logging
API](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/README.md),
[Metrics
API](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/api.md),
[Context and Propagation
API](https://github.com/open-telemetry/opentelemetry-specification/tree/main/specification/context),
and a set of [semantic
conventions](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/general/trace.md).
### Tracing API
[Tracing
API](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md)
allows users to generate
[Spans](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#span),
which represent a single operation within a trace. Spans can be nested to form a
trace tree. Each trace contains a root span, which typically describes the
entire operation and, optionally one or more child-spans for its
child-operations.
### Logging API
OpenTelemetry .NET does not introduce its own API for logging. Instead it
provides an integration with the well known [Microsoft.Extensions.Logging
API](https://docs.microsoft.com/dotnet/core/extensions/logging).
### Metrics API
[Metrics
API](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/api.md)
allows users to capture measurements about the execution of a computer program
at runtime. The Metrics API is designed to process raw measurements, generally
with the intent to produce continuous summaries of those measurements.
### Baggage API
[Baggage
API](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/baggage/api.md)
allows users to add context to metric, traces, and logs. Baggage can be
propagated out of proc using
[Propagators](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/context/api-propagators.md).
OpenTelemetry SDK ships a BaggagePropagator and enables it by default.
It is important to note that `Baggage` is not automatically attached to any
telemetry. User *can* explicitly read `Baggage` and use it to enrich metrics,
logs and traces. An example of doing this for traces is shown
[here](https://github.com/open-telemetry/opentelemetry-dotnet/blob/core-1.12.0/src/OpenTelemetry.Api/../../docs/trace/extending-the-sdk/README.md#processor).
```csharp
// Use GetBaggage to get all the key/value pairs present in Baggage
foreach (var item in Baggage.GetBaggage())
{
Console.WriteLine(item.Key);
Console.WriteLine(item.Value);
}
// Use SetBaggage method to add a key/value pair in Baggage
Baggage.SetBaggage("AppName", "MyApp");
Baggage.SetBaggage("Region", "West US");
// Use RemoveBaggage method to remove a key/value pair in Baggage
Baggage.RemoveBaggage("AppName");
// Use ClearBaggage method to remove all the key/value pairs in Baggage
Baggage.ClearBaggage();
```
The recommended way to add Baggage is to use the `Baggage.SetBaggage()` API.
OpenTelemetry users should not use the `Activity.AddBaggage` method.
## Introduction to OpenTelemetry .NET Tracing API
.NET runtime had `Activity` class for a long time, which was meant to be used
for tracing purposes and represents the equivalent of the OpenTelemetry
[Span](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#span).
OpenTelemetry .NET is reusing the existing `Activity` and associated classes to
represent the OpenTelemetry `Span`. This means, users can instrument their
applications/libraries to emit OpenTelemetry compatible traces by using just the
.NET Runtime.
The `Activity` and associated classes are shipped as part of
`System.Diagnostics.DiagnosticSource` nuget package. Version 5.0.0 of this
package contains improvements to `Activity` class which makes it more closely
aligned with OpenTelemetry [API
specification](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md).
Even though `Activity` enables all the scenarios OpenTelemetry supports, users
who are already familiar with OpenTelemetry terminology may find it easy to
operate with that terminology. For instance, `StartSpan` may be preferred over
`StartActivity`. To help with this transition, the OpenTelemetry.API package has
[shim](#instrumenting-using-opentelemetryapi-shim) classes to wrap around the
.NET `Activity` classes.
The shim exist only in the API. OpenTelemetry SDK for .NET will be operating
entirely with `Activity` only. Irrespective of whether shim classes or
`Activity` is used for instrumentation, the end result would be same. i.e
Processors/Exporters see the same data.
The recommended way of instrumenting is by using the [.NET Activity
API](#instrumenting-a-libraryapplication-with-net-activity-api). Users are
required to just take dependency on the
[DiagnosticSource](https://www.nuget.org/packages/System.Diagnostics.DiagnosticSource).
Adding dependency to
[OpenTelemetry.API](https://www.nuget.org/packages/opentelemetry.api) is
required only for the following scenarios:
1. You want to use terminology matching OpenTelemetry spec (Span vs Activity).
The [shim](#instrumenting-using-opentelemetryapi-shim) can be useful for such
users. Refer to the [comparison of Activity API and OpenTelemetry Tracing
API](https://github.com/open-telemetry/opentelemetry-dotnet/issues/947) if
you want to compare the differences.
2. Your library performs communication with other libraries/components, and want
to access
[Propagators](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/context/api-propagators.md),
to inject and extract context data. Some of the most common libraries
requiring this include
[HttpClient](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/tree/main/src/OpenTelemetry.Instrumentation.Http/README.md),
[ASP.NET Core](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/tree/main/src/OpenTelemetry.Instrumentation.AspNetCore/README.md).
This or contrib repository already provides instrumentation for these common
libraries. If your library is not built on top of these, and want to leverage
propagators, follow the [Context propagation](#context-propagation) section.
3. You want to leverage
[Baggage](#baggage-api)
API.
## Instrumenting a library/application with .NET Activity API
### Basic usage
As mentioned in the introduction, the instrumentation API for OpenTelemetry .NET
is the .NET `Activity` API. Guidance for instrumenting using this API is
documented fully in the TBD(dotnet activity user guide link), but is described
here as well.
1. Install the latest stable `System.Diagnostics.DiagnosticSource` to your
application or library.
```shell
dotnet add package System.Diagnostics.DiagnosticSource
```
2. Create an `ActivitySource`, providing the name and version of the
library/application doing the instrumentation. `ActivitySource` instance is
typically created once and is reused throughout the application/library.
```csharp
static ActivitySource activitySource = new ActivitySource(
"MyCompany.MyProduct.MyLibrary",
"1.0.0");
```
The above requires import of the `System.Diagnostics` namespace.
3. Use the `ActivitySource` instance from above to create `Activity` instances,
which represent a single operation within a trace. The parameter passed is
the `DisplayName` of the activity.
```csharp
var activity = activitySource.StartActivity("ActivityName");
```
If there are no listeners interested in this activity, the activity above
will be null. This happens when the final application does not enable
OpenTelemetry (or other `ActivityListener`s), or when OpenTelemetry samplers
chose not to sample this activity. Ensure that all subsequent calls using
this activity are protected with a null check.
4. Populate activity with tags following the [OpenTelemetry semantic
conventions](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/general/trace.md),
using the
[SetTag](https://learn.microsoft.com/dotnet/api/system.diagnostics.activity.settag)
API. It is highly recommended to check `activity.IsAllDataRequested`, before
populating any tags which are not readily available. `IsAllDataRequested` is
the same as
[Span.IsRecording](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#isrecording)
and will be false when samplers decide to not record the activity, and this
can be used to avoid any expensive operation to retrieve tags.
```csharp
activity?.SetTag("http.method", "GET");
if (activity != null && activity.IsAllDataRequested == true)
{
activity.SetTag("http.url", "http://www.mywebsite.com");
}
```
5. Perform application/library logic.
6. Stop the activity when done.
```csharp
activity?.Stop();
```
Alternately, as `Activity` implements `IDisposable`, it can be used with a
`using` block, which ensures activity gets stopped upon disposal. This is
shown below.
```csharp
using (var activity = activitySource.StartActivity("ActivityName")
{
activity?.SetTag("http.method", "GET");
} // Activity gets stopped automatically at end of this block during dispose.
```
The above showed the basic usage of instrumenting using `Activity`. The
following sections describes more features.
### Activity creation options
Basic usage example above showed how `StartActivity` method can be used to start
an `Activity`. The started activity will automatically becomes the `Current`
activity. It is important to note that the `StartActivity` returns `null`, if no
listeners are interested in the activity to be created. This happens when the
final application does not enable OpenTelemetry, or when OpenTelemetry samplers
chose not to sample this activity.
`StartActivity` has many overloads to control the activity creation.
1. `ActivityKind`
`Activity` has a property called `ActivityKind` which represents
OpenTelemetry
[SpanKind](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#spankind).
The default value will be `Internal`. `StartActivity` allows passing the
`ActivityKind` while starting an `Activity`.
```csharp
var activity = activitySource.StartActivity("ActivityName", ActivityKind.Server);
```
2. Parent using `ActivityContext`
`ActivityContext` represents the OpenTelemetry
[SpanContext](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#spancontext).
While starting a new `Activity`, the currently active `Activity` is
automatically taken as the parent of the new activity being created.
`StartActivity` allows passing explicit `ActivityContext` to override this
behavior.
```csharp
var parentContext = new ActivityContext(
ActivityTraceId.CreateFromString("0af7651916cd43dd8448eb211c80319c"),
ActivitySpanId.CreateFromString("b7ad6b7169203331"),
ActivityTraceFlags.None);
var activity = activitySource.StartActivity(
"ActivityName",
ActivityKind.Server,
parentContext);
```
As `ActivityContext` follows the [W3C
Trace-Context](https://w3c.github.io/trace-context), it is also possible to
provide the parent context as a single string matching the `traceparent`
header of the W3C Trace-Context. This is shown below.
```csharp
var activity = activitySource.StartActivity(
"ActivityName",
ActivityKind.Server,
"00-0af7651916cd43dd8448eb211c80319c-b7ad6b7169203331-01");
```
3. Initial Tags
`Tags` in `Activity` represents the OpenTelemetry [Span
Attributes](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#set-attributes).
Earlier sample showed the usage of `SetTag` method of `Activity` to add tags.
Refer to the
[specification](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/common/attribute-naming.md)
for best practices on naming tags. It is also possible to provide an initial
set of tags during activity creation, as shown below. It is recommended to
provide all available `Tags` during activity creation itself, as
[Samplers](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/sdk.md#sampler)
can only consider information present during activity creation time.
```csharp
var initialTags = new ActivityTagsCollection();
initialTags["com.mycompany.product.mytag1"] = "tagValue1";
initialTags["com.mycompany.product.mytag2"] = "tagValue2";
var activity = activitySource.StartActivity(
"ActivityName",
ActivityKind.Server,
"00-0af7651916cd43dd8448eb211c80319c-b7ad6b7169203331-01",
initialTags);
```
The above requires import of the `System.Collections.Generic` namespace.
4. Activity Links
In addition to parent-child relationships, activities can also be linked
using `ActivityLinks`, which represent
[Links](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/overview.md#links-between-spans)
in OpenTelemetry. Providing activity links during creation is recommended, as
this allows samplers to consider them when deciding whether to sample an
activity. However, starting with `System.Diagnostics.DiagnosticSource` 9.0.0,
links can also be added after an activity is created.
```csharp
var activityLinks = new List<ActivityLink>();
var linkedContext1 = new ActivityContext(
ActivityTraceId.CreateFromString("0af7651916cd43dd8448eb211c80319c"),
ActivitySpanId.CreateFromString("b7ad6b7169203331"),
ActivityTraceFlags.None);
var linkedContext2 = new ActivityContext(
ActivityTraceId.CreateFromString("4bf92f3577b34da6a3ce929d0e0e4736"),
ActivitySpanId.CreateFromString("00f067aa0ba902b7"),
ActivityTraceFlags.Recorded);
activityLinks.Add(new ActivityLink(linkedContext1));
activityLinks.Add(new ActivityLink(linkedContext2));
var activity = activitySource.StartActivity(
"ActivityWithLinks",
ActivityKind.Server,
default(ActivityContext),
initialTags,
activityLinks); // links provided at creation time.
// One may add links after activity is created too.
var linkedContext3 = new ActivityContext(
ActivityTraceId.CreateFromString("01260a70a81e1fa3ad5a8acfeaa0f711"),
ActivitySpanId.CreateFromString("34739aa9e2239da1"),
ActivityTraceFlags.None);
activity?.AddLink(linkedContext3);
```
Note that `Activity` above is created with `default(ActivityContext)`
parent, which makes it child of implicit `Activity.Current` or orphan if
there is no `Current`.
### Adding Events
It is possible to [add
events](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#add-events)
to `Activity` using the `AddEvent` method as shown below.
```csharp
activity?.AddEvent(new ActivityEvent("sample activity event."));
```
Apart from providing name, timestamp and attributes can be provided by using
corresponding overloads of `ActivityEvent`.
### Setting Status
OpenTelemetry defines a concept called
[Status](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#set-status)
to be associated with `Activity`. Starting with [DiagnosticSource
6.0](https://www.nuget.org/packages/System.Diagnostics.DiagnosticSource/6.0.0),
`SetStatus` API on `Activity` can be used to set the status and description as
shown below:
```csharp
activity?.SetStatus(ActivityStatusCode.Ok);
activity?.SetStatus(ActivityStatusCode.Error, "Error Description");
```
All the official
[Exporters](https://github.com/open-telemetry/opentelemetry-dotnet/blob/core-1.12.0/src/OpenTelemetry.Api/../../docs/trace/extending-the-sdk/README.md#exporter) shipped from
this repo support the above shown mechanism of setting status.
#### Setting Status - DiagnosticSource version older than 6.0
Prior to [DiagnosticSource
6.0](https://www.nuget.org/packages/System.Diagnostics.DiagnosticSource/6.0.0)
there was no `Status` field in `Activity`, and hence `Status` is set to an
`Activity` using the following special tags:
`otel.status_code` is the `Tag` name used to store the `StatusCode`, and
`otel.status_description` is the `Tag` name used to store the optional
`Description`.
Example:
```csharp
activity?.SetTag("otel.status_code", "ERROR");
activity?.SetTag("otel.status_description", "error status description");
```
Values for the StatusCode tag must be one of the strings "UNSET", "OK", or
"ERROR", which correspond respectively to the enums `Unset`, `Ok`, and `Error`
from [`StatusCode`](https://github.com/open-telemetry/opentelemetry-dotnet/blob/core-1.12.0/src/OpenTelemetry.Api/./Trace/StatusCode.cs).
If using OpenTelemetry API [shim](#instrumenting-using-opentelemetryapi-shim),
then you can leverage the `SetStatus` extension method on `Activity` as well.
## Instrumenting using OpenTelemetry.API Shim
As mentioned in the introduction section, using OpenTelemetry.API Shim is only
recommended if you want to use OpenTelemetry terminology like Tracer, Span
instead of ActivitySource, Activity.
Follow [this](https://github.com/open-telemetry/opentelemetry-dotnet/blob/core-1.12.0/src/OpenTelemetry.Api/../../examples/Console/TestOTelShimWithConsoleExporter.cs) code
for example usage of this shim.
## Context propagation
[OpenTelemetry.API](https://www.nuget.org/packages/opentelemetry.api) must be
used to access [Propagators
API](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/context/api-propagators.md)
which defines how to extract and inject context across process boundaries. This
is typically required if you are not using any of the .NET communication
libraries which has instrumentations already available which does the
propagation (eg: Asp.Net Core or HttpClient). In such cases, context extraction
and propagation is the responsibility of the library itself. An example would be
a producer-consumer pattern using some queuing library like RabbitMQ. Follow the
[messaging example](https://github.com/open-telemetry/opentelemetry-dotnet/blob/core-1.12.0/src/OpenTelemetry.Api/../../examples/MicroserviceExample/README.md) for examples
on how to
[inject](https://github.com/open-telemetry/opentelemetry-dotnet/blob/core-1.12.0/src/OpenTelemetry.Api/../../examples/MicroserviceExample/Utils/Messaging/MessageSender.cs)
and
[extract](https://github.com/open-telemetry/opentelemetry-dotnet/blob/core-1.12.0/src/OpenTelemetry.Api/../../examples/MicroserviceExample/Utils/Messaging/MessageReceiver.cs)
context.
> [!NOTE]
> If you are using the instrumentation libraries shipped from this repo [e.g.
[ASP.NET
Core](https://github.com/open-telemetry/opentelemetry-dotnet/tree/main/src/OpenTelemetry.Instrumentation.AspNetCore)
or
[HttpClient](https://github.com/open-telemetry/opentelemetry-dotnet/tree/main/src/OpenTelemetry.Instrumentation.Http)],
context propagation is done by using the
[default](https://github.com/open-telemetry/opentelemetry-dotnet/blob/d924663dc3d6bfdf737bc49ceaa1addcec90a2d6/src/OpenTelemetry/Sdk.cs#L34-L38)
propagator. The default can be updated by calling
`Sdk.SetDefaultTextMapPropagator` and passing the propagator of your choice.
Propagator Api used by the instrumentation libraries is different than
[DistributedContextPropagator](https://learn.microsoft.com/dotnet/api/system.diagnostics.distributedcontextpropagator)
available in `System.Diagnostics`. Implementing this will have no impact on the
propagation, if used alongside instrumentation libraries.
## Introduction to OpenTelemetry .NET Metrics API
Metrics in OpenTelemetry .NET are a somewhat unique implementation of the
OpenTelemetry project, as the Metrics API is incorporated directly into the .NET
runtime itself, as part of the
[`System.Diagnostics.DiagnosticSource`](https://www.nuget.org/packages/System.Diagnostics.DiagnosticSource)
package. This means, users can instrument their applications/libraries to emit
metrics by simply using the `System.Diagnostics.DiagnosticSource` package. This
package can be used in applications targeting any of the officially supported
versions of [.NET](https://dotnet.microsoft.com/download/dotnet) and [.NET
Framework](https://dotnet.microsoft.com/download/dotnet-framework) (an older
Windows-based .NET implementation).
## Instrumenting a library/application with .NET Metrics API
### Basic metric usage
1. Install the latest stable version of `System.Diagnostics.DiagnosticSource` to
your application or library.
```shell
dotnet add package System.Diagnostics.DiagnosticSource
```
2. Create a `Meter`, providing the name and version of the library/application
doing the instrumentation. The `Meter` instance is typically created once and
is reused throughout the application/library.
```csharp
static Meter meter = new Meter(
"companyname.product.instrumentationlibrary",
"1.0.0");
```
The above requires import of the `System.Diagnostics.Metrics` namespace.
> [!NOTE]
> It is important to note that `Meter` instances are created by
using its constructor, and *not* by calling a `GetMeter` method on the
`MeterProvider`. This is an important distinction from the [OpenTelemetry
specification](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/api.md#get-a-meter),
where `Meter`s are obtained from `MeterProvider`.
3. Use the `Meter` instance from above to create instruments, which can be used
to report measurements. Just like meter instances, the instrument instances
are to be created once and reused throughout the application/library.
```csharp
static Counter<long> MyFruitCounter = meter.CreateCounter<long>("MyFruitCounter");
```
4. Use the instruments to report measurements, along with the attributes.
```csharp
MyFruitCounter.Add(1, new("name", "apple"), new("color", "red"));
```
The above showed the usage of a `Counter` instrument. The following sections
describes more kinds of instruments.
### Instrument types
See [this](https://github.com/open-telemetry/opentelemetry-dotnet/blob/core-1.12.0/src/OpenTelemetry.Api/../../docs/metrics/learning-more-instruments/README.md).
## Troubleshooting
This component uses an
[EventSource](https://docs.microsoft.com/dotnet/api/system.diagnostics.tracing.eventsource)
with the name "OpenTelemetry-Api" for its internal logging. Please refer to [SDK
troubleshooting](https://github.com/open-telemetry/opentelemetry-dotnet/blob/core-1.12.0/src/OpenTelemetry.Api/../OpenTelemetry/README.md#troubleshooting) for instructions on
seeing these internal logs.
## References
* [OpenTelemetry Baggage API specification](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/baggage/api.md)
* [OpenTelemetry Logs Bridge API specification](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/bridge-api.md)
* [OpenTelemetry Metrics API specification](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/api.md)
* [OpenTelemetry Propagators API specification](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/context/api-propagators.md)
* [OpenTelemetry Tracing API specification](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md)

View File

@@ -0,0 +1,48 @@
OpenTelemetry .NET uses third-party libraries or other resources that may be
distributed under licenses different than the OpenTelemetry .NET software.
The attached notices are provided for information only.
License notice for .NET
-------------------------------
The MIT License (MIT)
Copyright (c) .NET Foundation and Contributors
All rights reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
License notice for gRPC for .NET (https://github.com/grpc/grpc-dotnet)
----------------------------------------------------------------------------------------------
Copyright 2019 The gRPC Authors
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

View File

@@ -0,0 +1 @@
LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUhlVENDQnY2Z0F3SUJBZ0lVVmtHcS8yY2JOWVRhWUN6aXhFSmRyZkowME40d0NnWUlLb1pJemowRUF3TXcKTnpFVk1CTUdBMVVFQ2hNTWMybG5jM1J2Y21VdVpHVjJNUjR3SEFZRFZRUURFeFZ6YVdkemRHOXlaUzFwYm5SbApjbTFsWkdsaGRHVXdIaGNOTWpVd05ESTVNakExTURRNVdoY05NalV3TkRJNU1qRXdNRFE1V2pBQU1Ga3dFd1lICktvWkl6ajBDQVFZSUtvWkl6ajBEQVFjRFFnQUVWTDFJb09FRllMQlRrckRBRTdnMkc0R0MxNE1hYW9LYUl6ZUEKMjFoZjZQejljTE40YUFoN2QwejhORkoybXJndlBjekdheVJ0cjVTM2ovcUxvWldvZXFPQ0JoMHdnZ1laTUE0RwpBMVVkRHdFQi93UUVBd0lIZ0RBVEJnTlZIU1VFRERBS0JnZ3JCZ0VGQlFjREF6QWRCZ05WSFE0RUZnUVUvc2Z2CmVzOVk0V3I4eVJkZ2luQkpmRlJHcUh3d0h3WURWUjBqQkJnd0ZvQVUzOVBwejFZa0VaYjVxTmpwS0ZXaXhpNFkKWkQ4d2dZVUdBMVVkRVFFQi93UjdNSG1HZDJoMGRIQnpPaTh2WjJsMGFIVmlMbU52YlM5dmNHVnVMWFJsYkdWdApaWFJ5ZVM5dmNHVnVkR1ZzWlcxbGRISjVMV1J2ZEc1bGRDOHVaMmwwYUhWaUwzZHZjbXRtYkc5M2N5OXdkV0pzCmFYTm9MWEJoWTJ0aFoyVnpMVEV1TUM1NWJXeEFjbVZtY3k5MFlXZHpMMk52Y21VdE1TNHhNaTR3TURrR0Npc0cKQVFRQmc3OHdBUUVFSzJoMGRIQnpPaTh2ZEc5clpXNHVZV04wYVc5dWN5NW5hWFJvZFdKMWMyVnlZMjl1ZEdWdQpkQzVqYjIwd0VnWUtLd1lCQkFHRHZ6QUJBZ1FFY0hWemFEQTJCZ29yQmdFRUFZTy9NQUVEQkNoaE5qZGhZMlE0Ck4yUTFaVFJrTkRNM1l6VXpPVGcyTmpSbU56Vm1ZV0V4T1RRNU5HSmxZamxqTUM4R0Npc0dBUVFCZzc4d0FRUUUKSVVKMWFXeGtMQ0J3WVdOckxDQmhibVFnY0hWaWJHbHphQ0IwYnlCTmVVZGxkREF4QmdvckJnRUVBWU8vTUFFRgpCQ052Y0dWdUxYUmxiR1Z0WlhSeWVTOXZjR1Z1ZEdWc1pXMWxkSEo1TFdSdmRHNWxkREFqQmdvckJnRUVBWU8vCk1BRUdCQlZ5WldaekwzUmhaM012WTI5eVpTMHhMakV5TGpBd093WUtLd1lCQkFHRHZ6QUJDQVF0REN0b2RIUncKY3pvdkwzUnZhMlZ1TG1GamRHbHZibk11WjJsMGFIVmlkWE5sY21OdmJuUmxiblF1WTI5dE1JR0hCZ29yQmdFRQpBWU8vTUFFSkJIa01kMmgwZEhCek9pOHZaMmwwYUhWaUxtTnZiUzl2Y0dWdUxYUmxiR1Z0WlhSeWVTOXZjR1Z1CmRHVnNaVzFsZEhKNUxXUnZkRzVsZEM4dVoybDBhSFZpTDNkdmNtdG1iRzkzY3k5d2RXSnNhWE5vTFhCaFkydGgKWjJWekxURXVNQzU1Yld4QWNtVm1jeTkwWVdkekwyTnZjbVV0TVM0eE1pNHdNRGdHQ2lzR0FRUUJnNzh3QVFvRQpLZ3dvWVRZM1lXTmtPRGRrTldVMFpEUXpOMk0xTXprNE5qWTBaamMxWm1GaE1UazBPVFJpWldJNVl6QWRCZ29yCkJnRUVBWU8vTUFFTEJBOE1EV2RwZEdoMVlpMW9iM04wWldRd1JnWUtLd1lCQkFHRHZ6QUJEQVE0RERab2RIUncKY3pvdkwyZHBkR2gxWWk1amIyMHZiM0JsYmkxMFpXeGxiV1YwY25rdmIzQmxiblJsYkdWdFpYUnllUzFrYjNSdQpaWFF3T0FZS0t3WUJCQUdEdnpBQkRRUXFEQ2hoTmpkaFkyUTROMlExWlRSa05ETTNZelV6T1RnMk5qUm1OelZtCllXRXhPVFE1TkdKbFlqbGpNQ1VHQ2lzR0FRUUJnNzh3QVE0RUZ3d1ZjbVZtY3k5MFlXZHpMMk52Y21VdE1TNHgKTWk0d01Ca0dDaXNHQVFRQmc3OHdBUThFQ3d3Sk1UZzFORGM0TURVNU1ERUdDaXNHQVFRQmc3OHdBUkFFSXd3aAphSFIwY0hNNkx5OW5hWFJvZFdJdVkyOXRMMjl3Wlc0dGRHVnNaVzFsZEhKNU1CZ0dDaXNHQVFRQmc3OHdBUkVFCkNnd0lORGs1T1Rnd01ESXdnWWNHQ2lzR0FRUUJnNzh3QVJJRWVReDNhSFIwY0hNNkx5OW5hWFJvZFdJdVkyOXQKTDI5d1pXNHRkR1ZzWlcxbGRISjVMMjl3Wlc1MFpXeGxiV1YwY25rdFpHOTBibVYwTHk1bmFYUm9kV0l2ZDI5eQphMlpzYjNkekwzQjFZbXhwYzJndGNHRmphMkZuWlhNdE1TNHdMbmx0YkVCeVpXWnpMM1JoWjNNdlkyOXlaUzB4CkxqRXlMakF3T0FZS0t3WUJCQUdEdnpBQkV3UXFEQ2hoTmpkaFkyUTROMlExWlRSa05ETTNZelV6T1RnMk5qUm0KTnpWbVlXRXhPVFE1TkdKbFlqbGpNQlFHQ2lzR0FRUUJnNzh3QVJRRUJnd0VjSFZ6YURCcUJnb3JCZ0VFQVlPLwpNQUVWQkZ3TVdtaDBkSEJ6T2k4dloybDBhSFZpTG1OdmJTOXZjR1Z1TFhSbGJHVnRaWFJ5ZVM5dmNHVnVkR1ZzClpXMWxkSEo1TFdSdmRHNWxkQzloWTNScGIyNXpMM0oxYm5Ndk1UUTNOREV3TWpVeU1UTXZZWFIwWlcxd2RITXYKTVRBV0Jnb3JCZ0VFQVlPL01BRVdCQWdNQm5CMVlteHBZekNCaWdZS0t3WUJCQUhXZVFJRUFnUjhCSG9BZUFCMgpBTjA5TUdyR3h4RXlZeGtlSEpsbk53S2lTbDY0M2p5dC80ZUtjb0F2S2U2T0FBQUJsb05SRGcwQUFBUURBRWN3ClJRSWdiVHVzQ2NQbFJtUjQvOTRZUFJmY2Q5SUdxK25BMnN0b1h5WUF6djZ4aVNjQ0lRRGgwNUNMSHFqbnR4TjgKQkRaZWR0d3pNNW5oYW9yeVRtN2dGak1JanNRbHFEQUtCZ2dxaGtqT1BRUURBd05wQURCbUFqRUE1aktKMTVIVQpJTXVHbW5FUWkzNGRPTHp0eFlySldGcUlLSkxnYkQ4NGRIWFkzMWpmZUxYN3JreElFWTM5VmYyTEFqRUFnak5wCkVjcGtYN2hNbktXeFZXd0F6cThkKzVHMjlGWGVpTlEwY0g5dDZHMUNMaVNTOC9lZnVpMEtMRUM3RzhnTwotLS0tLUVORCBDRVJUSUZJQ0FURS0tLS0tCg==

View File

@@ -0,0 +1 @@
MEYCIQCDnuycJS8GP0JIawCvZ1ss3SijLJCAYkE4QTzYPOLvRQIhANBXs+okU4f+pd0vcBaku/bBeps4Nn0HGkc9F+4OBlsm

File diff suppressed because it is too large Load Diff

View File

@@ -0,0 +1 @@
LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUhkekNDQnYyZ0F3SUJBZ0lVWHMzZU9ZemRSb2ZBZzhGeEd6czFJYUlUa3Awd0NnWUlLb1pJemowRUF3TXcKTnpFVk1CTUdBMVVFQ2hNTWMybG5jM1J2Y21VdVpHVjJNUjR3SEFZRFZRUURFeFZ6YVdkemRHOXlaUzFwYm5SbApjbTFsWkdsaGRHVXdIaGNOTWpVd05ESTVNakExTURVd1doY05NalV3TkRJNU1qRXdNRFV3V2pBQU1Ga3dFd1lICktvWkl6ajBDQVFZSUtvWkl6ajBEQVFjRFFnQUU1c21COWJXR1NNNjRtZFVrSUV5bEM1NURtU0RrbFdndUNtWU4KVWhhbXY0MWN2VTg1a2FYbmsyclhMZko1SkJXTld0OHhERlVPWHhjNElxM2JidWtSYTZPQ0Jod3dnZ1lZTUE0RwpBMVVkRHdFQi93UUVBd0lIZ0RBVEJnTlZIU1VFRERBS0JnZ3JCZ0VGQlFjREF6QWRCZ05WSFE0RUZnUVVSWDhkCk5UVTRRT1BFMlgwdjRPZm94aDF6cVFrd0h3WURWUjBqQkJnd0ZvQVUzOVBwejFZa0VaYjVxTmpwS0ZXaXhpNFkKWkQ4d2dZVUdBMVVkRVFFQi93UjdNSG1HZDJoMGRIQnpPaTh2WjJsMGFIVmlMbU52YlM5dmNHVnVMWFJsYkdWdApaWFJ5ZVM5dmNHVnVkR1ZzWlcxbGRISjVMV1J2ZEc1bGRDOHVaMmwwYUhWaUwzZHZjbXRtYkc5M2N5OXdkV0pzCmFYTm9MWEJoWTJ0aFoyVnpMVEV1TUM1NWJXeEFjbVZtY3k5MFlXZHpMMk52Y21VdE1TNHhNaTR3TURrR0Npc0cKQVFRQmc3OHdBUUVFSzJoMGRIQnpPaTh2ZEc5clpXNHVZV04wYVc5dWN5NW5hWFJvZFdKMWMyVnlZMjl1ZEdWdQpkQzVqYjIwd0VnWUtLd1lCQkFHRHZ6QUJBZ1FFY0hWemFEQTJCZ29yQmdFRUFZTy9NQUVEQkNoaE5qZGhZMlE0Ck4yUTFaVFJrTkRNM1l6VXpPVGcyTmpSbU56Vm1ZV0V4T1RRNU5HSmxZamxqTUM4R0Npc0dBUVFCZzc4d0FRUUUKSVVKMWFXeGtMQ0J3WVdOckxDQmhibVFnY0hWaWJHbHphQ0IwYnlCTmVVZGxkREF4QmdvckJnRUVBWU8vTUFFRgpCQ052Y0dWdUxYUmxiR1Z0WlhSeWVTOXZjR1Z1ZEdWc1pXMWxkSEo1TFdSdmRHNWxkREFqQmdvckJnRUVBWU8vCk1BRUdCQlZ5WldaekwzUmhaM012WTI5eVpTMHhMakV5TGpBd093WUtLd1lCQkFHRHZ6QUJDQVF0REN0b2RIUncKY3pvdkwzUnZhMlZ1TG1GamRHbHZibk11WjJsMGFIVmlkWE5sY21OdmJuUmxiblF1WTI5dE1JR0hCZ29yQmdFRQpBWU8vTUFFSkJIa01kMmgwZEhCek9pOHZaMmwwYUhWaUxtTnZiUzl2Y0dWdUxYUmxiR1Z0WlhSeWVTOXZjR1Z1CmRHVnNaVzFsZEhKNUxXUnZkRzVsZEM4dVoybDBhSFZpTDNkdmNtdG1iRzkzY3k5d2RXSnNhWE5vTFhCaFkydGgKWjJWekxURXVNQzU1Yld4QWNtVm1jeTkwWVdkekwyTnZjbVV0TVM0eE1pNHdNRGdHQ2lzR0FRUUJnNzh3QVFvRQpLZ3dvWVRZM1lXTmtPRGRrTldVMFpEUXpOMk0xTXprNE5qWTBaamMxWm1GaE1UazBPVFJpWldJNVl6QWRCZ29yCkJnRUVBWU8vTUFFTEJBOE1EV2RwZEdoMVlpMW9iM04wWldRd1JnWUtLd1lCQkFHRHZ6QUJEQVE0RERab2RIUncKY3pvdkwyZHBkR2gxWWk1amIyMHZiM0JsYmkxMFpXeGxiV1YwY25rdmIzQmxiblJsYkdWdFpYUnllUzFrYjNSdQpaWFF3T0FZS0t3WUJCQUdEdnpBQkRRUXFEQ2hoTmpkaFkyUTROMlExWlRSa05ETTNZelV6T1RnMk5qUm1OelZtCllXRXhPVFE1TkdKbFlqbGpNQ1VHQ2lzR0FRUUJnNzh3QVE0RUZ3d1ZjbVZtY3k5MFlXZHpMMk52Y21VdE1TNHgKTWk0d01Ca0dDaXNHQVFRQmc3OHdBUThFQ3d3Sk1UZzFORGM0TURVNU1ERUdDaXNHQVFRQmc3OHdBUkFFSXd3aAphSFIwY0hNNkx5OW5hWFJvZFdJdVkyOXRMMjl3Wlc0dGRHVnNaVzFsZEhKNU1CZ0dDaXNHQVFRQmc3OHdBUkVFCkNnd0lORGs1T1Rnd01ESXdnWWNHQ2lzR0FRUUJnNzh3QVJJRWVReDNhSFIwY0hNNkx5OW5hWFJvZFdJdVkyOXQKTDI5d1pXNHRkR1ZzWlcxbGRISjVMMjl3Wlc1MFpXeGxiV1YwY25rdFpHOTBibVYwTHk1bmFYUm9kV0l2ZDI5eQphMlpzYjNkekwzQjFZbXhwYzJndGNHRmphMkZuWlhNdE1TNHdMbmx0YkVCeVpXWnpMM1JoWjNNdlkyOXlaUzB4CkxqRXlMakF3T0FZS0t3WUJCQUdEdnpBQkV3UXFEQ2hoTmpkaFkyUTROMlExWlRSa05ETTNZelV6T1RnMk5qUm0KTnpWbVlXRXhPVFE1TkdKbFlqbGpNQlFHQ2lzR0FRUUJnNzh3QVJRRUJnd0VjSFZ6YURCcUJnb3JCZ0VFQVlPLwpNQUVWQkZ3TVdtaDBkSEJ6T2k4dloybDBhSFZpTG1OdmJTOXZjR1Z1TFhSbGJHVnRaWFJ5ZVM5dmNHVnVkR1ZzClpXMWxkSEo1TFdSdmRHNWxkQzloWTNScGIyNXpMM0oxYm5Ndk1UUTNOREV3TWpVeU1UTXZZWFIwWlcxd2RITXYKTVRBV0Jnb3JCZ0VFQVlPL01BRVdCQWdNQm5CMVlteHBZekNCaVFZS0t3WUJCQUhXZVFJRUFnUjdCSGtBZHdCMQpBTjA5TUdyR3h4RXlZeGtlSEpsbk53S2lTbDY0M2p5dC80ZUtjb0F2S2U2T0FBQUJsb05SRUdZQUFBUURBRVl3ClJBSWdGQVgvbDhnbVlJWTB2akN1NVNvNmY1M0Jua0QwZ3h2TG5NT05RUGtma0VNQ0lGNTRBd0JTbmE0OVRSWUsKTFY5R2I5djlpTlVTWWgzS2dWSnVmN1g3NGRscU1Bb0dDQ3FHU000OUJBTURBMmdBTUdVQ01RRExaWm5FQVpSaQpNOVpMclZwcWcvcUF3WXNFbGx1YXI1cTlrUjg3VEIxTUhyMnc3THZIMzJNRDM3OHpSMjFTeGE0Q01Ea3FGMmN4ClFBS2c2Zk5nd2Y2UnZ0bE43ZWFNaDNzWDAxUFpKNjh6UXVVRG0zZnM2bGpocnQ3SWZUUTZhYnpEc1E9PQotLS0tLUVORCBDRVJUSUZJQ0FURS0tLS0tCg==

View File

@@ -0,0 +1 @@
MEQCIGLjZF1YIOXT0bu/3Vc5/E4nJ6I4Gh0p7Hj8oyAwyJJEAiA9A1lxW6mUHp0iwmiC3DtJ4S4fsPBMq5k1eQ0M/u5Jjg==

File diff suppressed because it is too large Load Diff

View File

@@ -0,0 +1 @@
LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUhkekNDQnY2Z0F3SUJBZ0lVZWNvS2tnbElnOEFlNDluNnV0dTk3L0Y0Y1ZFd0NnWUlLb1pJemowRUF3TXcKTnpFVk1CTUdBMVVFQ2hNTWMybG5jM1J2Y21VdVpHVjJNUjR3SEFZRFZRUURFeFZ6YVdkemRHOXlaUzFwYm5SbApjbTFsWkdsaGRHVXdIaGNOTWpVd05ESTVNakExTURVd1doY05NalV3TkRJNU1qRXdNRFV3V2pBQU1Ga3dFd1lICktvWkl6ajBDQVFZSUtvWkl6ajBEQVFjRFFnQUVQYzU3MFpMK0svaXdlVTY4YzFWL2Z4cXNoRFY1VDI1Z09CRXIKMk1HYkpkd0VvcGM3UHh3cWk4VWpNMUlOYklMa096ems0amx0VjB6UVNUKzdETU42dTZPQ0JoMHdnZ1laTUE0RwpBMVVkRHdFQi93UUVBd0lIZ0RBVEJnTlZIU1VFRERBS0JnZ3JCZ0VGQlFjREF6QWRCZ05WSFE0RUZnUVVEU1JFClFXUkNLSlJiaWhIWDZJUUFmMzJOYjM0d0h3WURWUjBqQkJnd0ZvQVUzOVBwejFZa0VaYjVxTmpwS0ZXaXhpNFkKWkQ4d2dZVUdBMVVkRVFFQi93UjdNSG1HZDJoMGRIQnpPaTh2WjJsMGFIVmlMbU52YlM5dmNHVnVMWFJsYkdWdApaWFJ5ZVM5dmNHVnVkR1ZzWlcxbGRISjVMV1J2ZEc1bGRDOHVaMmwwYUhWaUwzZHZjbXRtYkc5M2N5OXdkV0pzCmFYTm9MWEJoWTJ0aFoyVnpMVEV1TUM1NWJXeEFjbVZtY3k5MFlXZHpMMk52Y21VdE1TNHhNaTR3TURrR0Npc0cKQVFRQmc3OHdBUUVFSzJoMGRIQnpPaTh2ZEc5clpXNHVZV04wYVc5dWN5NW5hWFJvZFdKMWMyVnlZMjl1ZEdWdQpkQzVqYjIwd0VnWUtLd1lCQkFHRHZ6QUJBZ1FFY0hWemFEQTJCZ29yQmdFRUFZTy9NQUVEQkNoaE5qZGhZMlE0Ck4yUTFaVFJrTkRNM1l6VXpPVGcyTmpSbU56Vm1ZV0V4T1RRNU5HSmxZamxqTUM4R0Npc0dBUVFCZzc4d0FRUUUKSVVKMWFXeGtMQ0J3WVdOckxDQmhibVFnY0hWaWJHbHphQ0IwYnlCTmVVZGxkREF4QmdvckJnRUVBWU8vTUFFRgpCQ052Y0dWdUxYUmxiR1Z0WlhSeWVTOXZjR1Z1ZEdWc1pXMWxkSEo1TFdSdmRHNWxkREFqQmdvckJnRUVBWU8vCk1BRUdCQlZ5WldaekwzUmhaM012WTI5eVpTMHhMakV5TGpBd093WUtLd1lCQkFHRHZ6QUJDQVF0REN0b2RIUncKY3pvdkwzUnZhMlZ1TG1GamRHbHZibk11WjJsMGFIVmlkWE5sY21OdmJuUmxiblF1WTI5dE1JR0hCZ29yQmdFRQpBWU8vTUFFSkJIa01kMmgwZEhCek9pOHZaMmwwYUhWaUxtTnZiUzl2Y0dWdUxYUmxiR1Z0WlhSeWVTOXZjR1Z1CmRHVnNaVzFsZEhKNUxXUnZkRzVsZEM4dVoybDBhSFZpTDNkdmNtdG1iRzkzY3k5d2RXSnNhWE5vTFhCaFkydGgKWjJWekxURXVNQzU1Yld4QWNtVm1jeTkwWVdkekwyTnZjbVV0TVM0eE1pNHdNRGdHQ2lzR0FRUUJnNzh3QVFvRQpLZ3dvWVRZM1lXTmtPRGRrTldVMFpEUXpOMk0xTXprNE5qWTBaamMxWm1GaE1UazBPVFJpWldJNVl6QWRCZ29yCkJnRUVBWU8vTUFFTEJBOE1EV2RwZEdoMVlpMW9iM04wWldRd1JnWUtLd1lCQkFHRHZ6QUJEQVE0RERab2RIUncKY3pvdkwyZHBkR2gxWWk1amIyMHZiM0JsYmkxMFpXeGxiV1YwY25rdmIzQmxiblJsYkdWdFpYUnllUzFrYjNSdQpaWFF3T0FZS0t3WUJCQUdEdnpBQkRRUXFEQ2hoTmpkaFkyUTROMlExWlRSa05ETTNZelV6T1RnMk5qUm1OelZtCllXRXhPVFE1TkdKbFlqbGpNQ1VHQ2lzR0FRUUJnNzh3QVE0RUZ3d1ZjbVZtY3k5MFlXZHpMMk52Y21VdE1TNHgKTWk0d01Ca0dDaXNHQVFRQmc3OHdBUThFQ3d3Sk1UZzFORGM0TURVNU1ERUdDaXNHQVFRQmc3OHdBUkFFSXd3aAphSFIwY0hNNkx5OW5hWFJvZFdJdVkyOXRMMjl3Wlc0dGRHVnNaVzFsZEhKNU1CZ0dDaXNHQVFRQmc3OHdBUkVFCkNnd0lORGs1T1Rnd01ESXdnWWNHQ2lzR0FRUUJnNzh3QVJJRWVReDNhSFIwY0hNNkx5OW5hWFJvZFdJdVkyOXQKTDI5d1pXNHRkR1ZzWlcxbGRISjVMMjl3Wlc1MFpXeGxiV1YwY25rdFpHOTBibVYwTHk1bmFYUm9kV0l2ZDI5eQphMlpzYjNkekwzQjFZbXhwYzJndGNHRmphMkZuWlhNdE1TNHdMbmx0YkVCeVpXWnpMM1JoWjNNdlkyOXlaUzB4CkxqRXlMakF3T0FZS0t3WUJCQUdEdnpBQkV3UXFEQ2hoTmpkaFkyUTROMlExWlRSa05ETTNZelV6T1RnMk5qUm0KTnpWbVlXRXhPVFE1TkdKbFlqbGpNQlFHQ2lzR0FRUUJnNzh3QVJRRUJnd0VjSFZ6YURCcUJnb3JCZ0VFQVlPLwpNQUVWQkZ3TVdtaDBkSEJ6T2k4dloybDBhSFZpTG1OdmJTOXZjR1Z1TFhSbGJHVnRaWFJ5ZVM5dmNHVnVkR1ZzClpXMWxkSEo1TFdSdmRHNWxkQzloWTNScGIyNXpMM0oxYm5Ndk1UUTNOREV3TWpVeU1UTXZZWFIwWlcxd2RITXYKTVRBV0Jnb3JCZ0VFQVlPL01BRVdCQWdNQm5CMVlteHBZekNCaWdZS0t3WUJCQUhXZVFJRUFnUjhCSG9BZUFCMgpBTjA5TUdyR3h4RXlZeGtlSEpsbk53S2lTbDY0M2p5dC80ZUtjb0F2S2U2T0FBQUJsb05SRTBJQUFBUURBRWN3ClJRSWhBT3REZFRNSWl4b3ErK0RYQ3FZeGQzemRBUTZnQVpRZWZMb3NVRzBDZ2hkTUFpQW1RdjNtcTVWcERNWk8KOXdvZ3U5STMxd09EYUw2TVdPSnVVYUljQWhGNmZ6QUtCZ2dxaGtqT1BRUURBd05uQURCa0FqQnhZK05DaVEwagpEOXRoOXBRK3phZDhOUXc1WFJaTGtJanIyQVg0N2pYWkV6QVg0OVhzWXp6eCttZFhzMTQ4eXF3Q01BOFo0V0U3CkJ4UXEzS0RFVUVJMitjdnA2Tk1nNVhpOG1iemFXaFNwRnQwNFFoT1NKSmkyQ0c3VEdZWFJpU0tCWUE9PQotLS0tLUVORCBDRVJUSUZJQ0FURS0tLS0tCg==

View File

@@ -0,0 +1 @@
MEQCIHP3sBA05nj+Ak+xhC2OX874oT6uRcALthkArl5vH8LEAiAaoSgwdG8KhWq9cJyik5hLDcNW0DGenKmKMfVUjGprSg==

File diff suppressed because it is too large Load Diff

View File

@@ -0,0 +1 @@
LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUhlRENDQnY2Z0F3SUJBZ0lVV3lLdVVzSFFTSjRhQngweUxtb3ZFaDVLeEpBd0NnWUlLb1pJemowRUF3TXcKTnpFVk1CTUdBMVVFQ2hNTWMybG5jM1J2Y21VdVpHVjJNUjR3SEFZRFZRUURFeFZ6YVdkemRHOXlaUzFwYm5SbApjbTFsWkdsaGRHVXdIaGNOTWpVd05ESTVNakExTURVeFdoY05NalV3TkRJNU1qRXdNRFV4V2pBQU1Ga3dFd1lICktvWkl6ajBDQVFZSUtvWkl6ajBEQVFjRFFnQUUvdldqekhad2MxeE05VUhQVjRmaDNHTERsMGY0Uk4yN055NEwKSnE1N2txb0hCcytmOExob3dFTXRCNkU4YmxqaEI1ZlZ4UEgyYkxldytMVnZQMmRjZjZPQ0JoMHdnZ1laTUE0RwpBMVVkRHdFQi93UUVBd0lIZ0RBVEJnTlZIU1VFRERBS0JnZ3JCZ0VGQlFjREF6QWRCZ05WSFE0RUZnUVVURDNkClNqYUNicmt5ZmNFNlA1UXdUT2lOUUFzd0h3WURWUjBqQkJnd0ZvQVUzOVBwejFZa0VaYjVxTmpwS0ZXaXhpNFkKWkQ4d2dZVUdBMVVkRVFFQi93UjdNSG1HZDJoMGRIQnpPaTh2WjJsMGFIVmlMbU52YlM5dmNHVnVMWFJsYkdWdApaWFJ5ZVM5dmNHVnVkR1ZzWlcxbGRISjVMV1J2ZEc1bGRDOHVaMmwwYUhWaUwzZHZjbXRtYkc5M2N5OXdkV0pzCmFYTm9MWEJoWTJ0aFoyVnpMVEV1TUM1NWJXeEFjbVZtY3k5MFlXZHpMMk52Y21VdE1TNHhNaTR3TURrR0Npc0cKQVFRQmc3OHdBUUVFSzJoMGRIQnpPaTh2ZEc5clpXNHVZV04wYVc5dWN5NW5hWFJvZFdKMWMyVnlZMjl1ZEdWdQpkQzVqYjIwd0VnWUtLd1lCQkFHRHZ6QUJBZ1FFY0hWemFEQTJCZ29yQmdFRUFZTy9NQUVEQkNoaE5qZGhZMlE0Ck4yUTFaVFJrTkRNM1l6VXpPVGcyTmpSbU56Vm1ZV0V4T1RRNU5HSmxZamxqTUM4R0Npc0dBUVFCZzc4d0FRUUUKSVVKMWFXeGtMQ0J3WVdOckxDQmhibVFnY0hWaWJHbHphQ0IwYnlCTmVVZGxkREF4QmdvckJnRUVBWU8vTUFFRgpCQ052Y0dWdUxYUmxiR1Z0WlhSeWVTOXZjR1Z1ZEdWc1pXMWxkSEo1TFdSdmRHNWxkREFqQmdvckJnRUVBWU8vCk1BRUdCQlZ5WldaekwzUmhaM012WTI5eVpTMHhMakV5TGpBd093WUtLd1lCQkFHRHZ6QUJDQVF0REN0b2RIUncKY3pvdkwzUnZhMlZ1TG1GamRHbHZibk11WjJsMGFIVmlkWE5sY21OdmJuUmxiblF1WTI5dE1JR0hCZ29yQmdFRQpBWU8vTUFFSkJIa01kMmgwZEhCek9pOHZaMmwwYUhWaUxtTnZiUzl2Y0dWdUxYUmxiR1Z0WlhSeWVTOXZjR1Z1CmRHVnNaVzFsZEhKNUxXUnZkRzVsZEM4dVoybDBhSFZpTDNkdmNtdG1iRzkzY3k5d2RXSnNhWE5vTFhCaFkydGgKWjJWekxURXVNQzU1Yld4QWNtVm1jeTkwWVdkekwyTnZjbVV0TVM0eE1pNHdNRGdHQ2lzR0FRUUJnNzh3QVFvRQpLZ3dvWVRZM1lXTmtPRGRrTldVMFpEUXpOMk0xTXprNE5qWTBaamMxWm1GaE1UazBPVFJpWldJNVl6QWRCZ29yCkJnRUVBWU8vTUFFTEJBOE1EV2RwZEdoMVlpMW9iM04wWldRd1JnWUtLd1lCQkFHRHZ6QUJEQVE0RERab2RIUncKY3pvdkwyZHBkR2gxWWk1amIyMHZiM0JsYmkxMFpXeGxiV1YwY25rdmIzQmxiblJsYkdWdFpYUnllUzFrYjNSdQpaWFF3T0FZS0t3WUJCQUdEdnpBQkRRUXFEQ2hoTmpkaFkyUTROMlExWlRSa05ETTNZelV6T1RnMk5qUm1OelZtCllXRXhPVFE1TkdKbFlqbGpNQ1VHQ2lzR0FRUUJnNzh3QVE0RUZ3d1ZjbVZtY3k5MFlXZHpMMk52Y21VdE1TNHgKTWk0d01Ca0dDaXNHQVFRQmc3OHdBUThFQ3d3Sk1UZzFORGM0TURVNU1ERUdDaXNHQVFRQmc3OHdBUkFFSXd3aAphSFIwY0hNNkx5OW5hWFJvZFdJdVkyOXRMMjl3Wlc0dGRHVnNaVzFsZEhKNU1CZ0dDaXNHQVFRQmc3OHdBUkVFCkNnd0lORGs1T1Rnd01ESXdnWWNHQ2lzR0FRUUJnNzh3QVJJRWVReDNhSFIwY0hNNkx5OW5hWFJvZFdJdVkyOXQKTDI5d1pXNHRkR1ZzWlcxbGRISjVMMjl3Wlc1MFpXeGxiV1YwY25rdFpHOTBibVYwTHk1bmFYUm9kV0l2ZDI5eQphMlpzYjNkekwzQjFZbXhwYzJndGNHRmphMkZuWlhNdE1TNHdMbmx0YkVCeVpXWnpMM1JoWjNNdlkyOXlaUzB4CkxqRXlMakF3T0FZS0t3WUJCQUdEdnpBQkV3UXFEQ2hoTmpkaFkyUTROMlExWlRSa05ETTNZelV6T1RnMk5qUm0KTnpWbVlXRXhPVFE1TkdKbFlqbGpNQlFHQ2lzR0FRUUJnNzh3QVJRRUJnd0VjSFZ6YURCcUJnb3JCZ0VFQVlPLwpNQUVWQkZ3TVdtaDBkSEJ6T2k4dloybDBhSFZpTG1OdmJTOXZjR1Z1TFhSbGJHVnRaWFJ5ZVM5dmNHVnVkR1ZzClpXMWxkSEo1TFdSdmRHNWxkQzloWTNScGIyNXpMM0oxYm5Ndk1UUTNOREV3TWpVeU1UTXZZWFIwWlcxd2RITXYKTVRBV0Jnb3JCZ0VFQVlPL01BRVdCQWdNQm5CMVlteHBZekNCaWdZS0t3WUJCQUhXZVFJRUFnUjhCSG9BZUFCMgpBTjA5TUdyR3h4RXlZeGtlSEpsbk53S2lTbDY0M2p5dC80ZUtjb0F2S2U2T0FBQUJsb05SRmRzQUFBUURBRWN3ClJRSWhBSzBCQjFwb3VDNFNxZnorV0IyMGFxei85cXdmZVJDeHpldlJtd1Q1dGFTRUFpQmNObjJxakxvSFJWL3MKUW1hOU1DOWw0UW4xOTNUSHRFL2Z4WlIxcWZIVUNUQUtCZ2dxaGtqT1BRUURBd05vQURCbEFqQkI5NlVESnp0eQozemtVcVlnRFRnSXliV2Z2bXo4SlRBbEJlWEZDNmR4bFhtS1hBaityQVVYbTFmZWJMK3BkeTRzQ01RRFFrUEhyCkJSTTJoVXZRS0tUb3M1aDdQdTBPOTY4c09zUEFGY3J1b2hSQm0xNlhQNU1TcndiMVZqc0lyM0xxR0lzPQotLS0tLUVORCBDRVJUSUZJQ0FURS0tLS0tCg==

View File

@@ -0,0 +1 @@
MEYCIQD95noiaOH9h8a9aHVbRpsFjx7u4MAjb5M770NNsl0glwIhAJFnq4ANDYidZVdsDOLX28PJ7LiqZqQgYhyTOh8GlTiI

File diff suppressed because it is too large Load Diff

Binary file not shown.

After

Width:  |  Height:  |  Size: 2.1 KiB

View File

@@ -0,0 +1 @@
2NE8fiYrGaukHCQ/QeDatRSv8Z96sD8WDnrtpKcncOieBmWG4/7coBwuENjQJ7jicGkbIh/Mtli3l0Hh5Vs07g==