Dolittle.SDK.Diagnostics.OpenTelemetry
23.5.0
See the version list below for details.
dotnet add package Dolittle.SDK.Diagnostics.OpenTelemetry --version 23.5.0
NuGet\Install-Package Dolittle.SDK.Diagnostics.OpenTelemetry -Version 23.5.0
<PackageReference Include="Dolittle.SDK.Diagnostics.OpenTelemetry" Version="23.5.0" />
paket add Dolittle.SDK.Diagnostics.OpenTelemetry --version 23.5.0
#r "nuget: Dolittle.SDK.Diagnostics.OpenTelemetry, 23.5.0"
// Install Dolittle.SDK.Diagnostics.OpenTelemetry as a Cake Addin #addin nuget:?package=Dolittle.SDK.Diagnostics.OpenTelemetry&version=23.5.0 // Install Dolittle.SDK.Diagnostics.OpenTelemetry as a Cake Tool #tool nuget:?package=Dolittle.SDK.Diagnostics.OpenTelemetry&version=23.5.0
Dolittle is a decentralized, distributed, event-driven microservice platform built to harness the power of events.
This is our C# SDK, install it with:
dotnet add package Dolittle.SDK
Get Started
- Try our getting started tutorial
- Check out our documentation
Want to try another language?
- Check out the JavaScript and TypeScript SDK
Issues and Contributing
Issues and contributions are always welcome!
To learn how to contribute, please read our contributing guide.
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net6.0 is compatible. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 is compatible. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. |
-
net6.0
- Dolittle.SDK.Diagnostics (>= 23.5.0)
- Microsoft.Extensions.Hosting.Abstractions (>= 8.0.1)
- Microsoft.Extensions.Logging (>= 8.0.1)
- MongoDB.Driver.Core.Extensions.DiagnosticSources (>= 1.5.0)
- OpenTelemetry.Exporter.OpenTelemetryProtocol (>= 1.9.0)
- OpenTelemetry.Extensions.Hosting (>= 1.9.0)
- OpenTelemetry.Instrumentation.AspNetCore (>= 1.9.0)
- OpenTelemetry.Instrumentation.Runtime (>= 1.9.0)
- Proto.OpenTelemetry (>= 1.7.1-alpha.0.1)
- System.Text.Json (>= 8.0.5)
-
net7.0
- Dolittle.SDK.Diagnostics (>= 23.5.0)
- Microsoft.Extensions.Hosting.Abstractions (>= 8.0.1)
- Microsoft.Extensions.Logging (>= 8.0.1)
- MongoDB.Driver.Core.Extensions.DiagnosticSources (>= 1.5.0)
- OpenTelemetry.Exporter.OpenTelemetryProtocol (>= 1.9.0)
- OpenTelemetry.Extensions.Hosting (>= 1.9.0)
- OpenTelemetry.Instrumentation.AspNetCore (>= 1.9.0)
- OpenTelemetry.Instrumentation.Runtime (>= 1.9.0)
- Proto.OpenTelemetry (>= 1.7.1-alpha.0.1)
- System.Text.Json (>= 8.0.5)
-
net8.0
- Dolittle.SDK.Diagnostics (>= 23.5.0)
- Microsoft.Extensions.Hosting.Abstractions (>= 8.0.1)
- Microsoft.Extensions.Logging (>= 8.0.1)
- MongoDB.Driver.Core.Extensions.DiagnosticSources (>= 1.5.0)
- OpenTelemetry.Exporter.OpenTelemetryProtocol (>= 1.9.0)
- OpenTelemetry.Extensions.Hosting (>= 1.9.0)
- OpenTelemetry.Instrumentation.AspNetCore (>= 1.9.0)
- OpenTelemetry.Instrumentation.Runtime (>= 1.9.0)
- Proto.OpenTelemetry (>= 1.7.1-alpha.0.1)
- System.Text.Json (>= 8.0.5)
NuGet packages (1)
Showing the top 1 NuGet packages that depend on Dolittle.SDK.Diagnostics.OpenTelemetry:
Package | Downloads |
---|---|
Dolittle.SDK
Dolittle is a decentralized, distributed, event-driven microservice platform built to harness the power of events. |
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last updated |
---|---|---|
24.0.0 | 65 | 11/13/2024 |
23.5.2 | 87 | 11/13/2024 |
23.5.1 | 97 | 11/7/2024 |
23.5.0 | 324 | 10/23/2024 |
23.4.0 | 351 | 10/2/2024 |
23.3.0 | 496 | 7/31/2024 |
23.2.5 | 589 | 6/20/2024 |
23.2.4 | 220 | 6/13/2024 |
23.2.3 | 151 | 6/10/2024 |
23.2.2 | 176 | 6/2/2024 |
23.2.1 | 168 | 5/16/2024 |
23.2.0 | 1,317 | 3/14/2024 |
23.1.0 | 211 | 3/12/2024 |
23.0.0 | 195 | 3/8/2024 |
22.1.3 | 268 | 2/26/2024 |
22.1.2 | 1,061 | 10/24/2023 |
22.1.1 | 269 | 10/4/2023 |
22.1.0 | 203 | 9/18/2023 |
22.0.5 | 252 | 9/7/2023 |
22.0.4 | 331 | 8/28/2023 |
22.0.3 | 273 | 8/15/2023 |
22.0.2 | 247 | 8/8/2023 |
22.0.1 | 197 | 8/8/2023 |
22.0.0 | 413 | 6/22/2023 |
22.0.0-arkenstone.1 | 86 | 6/21/2023 |
22.0.0-arkenstone.0 | 84 | 6/12/2023 |
21.0.2 | 411 | 9/7/2023 |
21.0.1 | 548 | 6/8/2023 |
21.0.0 | 236 | 6/2/2023 |
21.0.0-feanor.2 | 73 | 5/31/2023 |
21.0.0-feanor.1 | 1,146 | 5/30/2023 |
21.0.0-feanor.0 | 75 | 5/30/2023 |
20.2.0 | 2,338 | 1/23/2023 |
20.2.0-shire.17 | 110 | 1/19/2023 |
20.2.0-shire.16 | 104 | 1/16/2023 |
20.2.0-shire.15 | 107 | 1/12/2023 |
20.2.0-shire.14 | 107 | 1/12/2023 |
20.2.0-shire.13 | 102 | 1/12/2023 |
20.2.0-shire.12 | 106 | 1/11/2023 |
20.2.0-shire.11 | 101 | 1/10/2023 |
20.2.0-shire.10 | 107 | 1/6/2023 |
20.2.0-shire.9 | 104 | 1/6/2023 |
20.2.0-shire.8 | 98 | 1/6/2023 |
20.2.0-shire.7 | 101 | 1/6/2023 |
20.2.0-shire.6 | 110 | 1/5/2023 |
20.2.0-shire.5 | 108 | 1/5/2023 |
20.2.0-shire.4 | 109 | 1/5/2023 |
20.2.0-shire.3 | 111 | 1/5/2023 |
20.2.0-shire.2 | 115 | 12/26/2022 |
20.2.0-shire.1 | 110 | 12/26/2022 |
20.2.0-shire.0 | 107 | 12/26/2022 |
20.1.0 | 262 | 12/25/2022 |
20.1.0-faramir.1 | 97 | 12/12/2022 |
20.1.0-faramir.0 | 95 | 12/9/2022 |
20.0.2 | 921 | 12/13/2022 |
20.0.1 | 225 | 12/12/2022 |
20.0.0 | 228 | 12/8/2022 |
19.1.0-elrond.7 | 97 | 12/7/2022 |
19.1.0-elrond.6 | 97 | 12/5/2022 |
19.1.0-elrond.5 | 93 | 12/5/2022 |
19.1.0-elrond.4 | 96 | 12/2/2022 |
19.1.0-elrond.3 | 100 | 12/2/2022 |
19.1.0-elrond.2 | 94 | 11/29/2022 |
19.1.0-elrond.1 | 96 | 11/28/2022 |
19.1.0-elrond.0 | 96 | 11/28/2022 |
19.0.0 | 439 | 11/25/2022 |
19.0.0-proto.5 | 92 | 11/25/2022 |
19.0.0-proto.4 | 118 | 11/22/2022 |
19.0.0-proto.3 | 93 | 11/21/2022 |
19.0.0-proto.2 | 91 | 11/21/2022 |
19.0.0-proto.1 | 96 | 11/21/2022 |
19.0.0-proto.0 | 104 | 11/18/2022 |
18.2.0-bolt.1 | 95 | 11/16/2022 |
18.2.0-bolt.0 | 114 | 11/16/2022 |
18.1.1 | 651 | 10/31/2022 |
18.1.0 | 629 | 10/26/2022 |
18.0.1 | 648 | 10/20/2022 |
18.0.0 | 676 | 9/15/2022 |
17.2.3 | 710 | 9/9/2022 |
17.2.2 | 1,279 | 8/26/2022 |
17.2.1 | 1,530 | 8/10/2022 |
17.2.0 | 822 | 7/8/2022 |
17.1.2 | 718 | 7/7/2022 |
17.1.1 | 691 | 7/7/2022 |
17.1.0 | 699 | 7/5/2022 |
17.1.0-boromir.4 | 116 | 7/8/2022 |
17.1.0-boromir.3 | 111 | 7/5/2022 |
Version 23.5.0:
This adds support for retroactively redacting personal data details from previously committed events. Redactions are scoped to a single EventSourceId, and a single event type, and allow you to overwrite or remove specific fields.
How to use it:
Events that should be redacted must be annotated to target the fields that should be updated or removed
[EventType("24e3a119-57d5-45d7-b7ef-a736fe6331e7")]
public class CustomerRegistered
{
// The generic type will replace the value
[RedactablePersonalData<string>("<redacted>")]
public string Name { get; init; }
// The non-generic one will remove the field altogether
[RedactablePersonalData]
public Address? CustomerAddress { get; init; }
}They can then be redacted by committing a targeted redaction event on the same eventsourceId as the redacted events.
It can either be done with the built-in event
public void GdprForget(string reason, string performedBy)
{
Apply(Redactions.Create<CustomerRegistered>(reason, performedBy));
}or a user-created event
[EventType("de1e7e17-bad5-da7a-a4f7-e409ae1785dc")]
public class CustomerDetailsForgotten : PersonalDataRedactedForEvent<CustomerRegistered>
{
}Applied like this
public void GdprForget(string reason, string performedBy)
{
Apply(Redactions.Create<CustomerRegistered, CustomerDetailsForgotten>(reason, performedBy));
}What about read models and aggregate state ?:
Aggregates and read models should handle the redactions as normal events, and update state accordingly.
Ex
public void On(CustomerDetailsForgotten evt)
{
_address = null;
_name = null;
_gdprRedacted = true;
}Read models are not automagically updated, but should handle the redaction events themselves. Redaction events after being committed behave exactly as any other event, and can be processed by both eventhandlers and projections.
Since you would want the eventhandlers to only handle as few events as needed, user defined redaction events are the suggested way to perform redactions.
How does it work?:
The runtime will recognize the redaction event type with the redaction prefix "de1e7e17-bad5-da7a", and if the events have the correctly formatted structure, it will perform the redactions in the same transaction as the new events are being added.
It will replace overridden properties as specified in RedactedProperties, and remove properties that are defined with null values.
Redaction events themselves cannot be redacted, to ensure auditability of the system.
Added:
- Dolittle.SDK.Events.Redaction.PersonalDataRedactedForEvent - Built in event that can redact any event type
- Dolittle.SDK.Events.Redaction.PersonalDataRedactedForEvent<TEvent> - Class to extend in order to create redactions for specific events
- Dolittle.SDK.Events.Redaction - Use this to simplify creation of redaction events
Updated:
- The solution was updated to use centralized package management (https://learn.microsoft.com/en-us/nuget/consume-packages/Central-Package-Management) to simplify dependency maintenance. Dependencies have also been upgraded.
Changelog:
For all release notes, see changelog (https://github.com/dolittle/DotNET.SDK/blob/master/CHANGELOG.md)