You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: documentation/authentication.md
+1
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,7 @@ Azure Active Directory integration (referred to as Azure AD) is the recommended
20
20
21
21
-[Create an App Registration](https://learn.microsoft.com/azure/active-directory/develop/quickstart-register-app#register-an-application) in your Azure tenant that will be used by `dotnet monitor`. Note that a single App Registration can be used by multiple instances of `dotnet monitor`.
22
22
-[Add a new app role](https://learn.microsoft.com/azure/active-directory/develop/howto-add-app-roles-in-azure-ad-apps#app-roles-ui) for general API access.
23
+
-[Assign user to role](https://learn.microsoft.com/azure/active-directory/develop/howto-add-app-roles-in-apps#assign-users-and-groups-to-roles) via the Enterprise Applications section of AAD.
23
24
-[Configure Azure AD in dotnet monitor](./configuration/azure-ad-authentication-configuration.md).
24
25
25
26
> **Note**: Azure AD B2C is currently not supported.
Starting with `dotnet monitor` 8, the tool includes an egress extensibility model that allows additional egress providers to be discovered and usable by a `dotnet monitor` installation. The existing `AzureBlobStorage` egress provider has been moved to this model and remains as an available egress provider in the .NET Tool and `mcr.microsoft.com/dotnet/monitor` image offerings.
34
+
35
+
In addition to the current `dotnet monitor` offerings, a `monitor-base` image is now available; this image does not include egress providers (with the exception of `FileSystem` egress), allowing users to only include their preferred egress providers. For convenience, the `monitor` image and the nuget package will include all of `dotnet monitor`'s supported extensions.
36
+
37
+
### Manually Installing Supported Extensions
38
+
39
+
Users using the `monitor-base` image can manually install supported extensions via Multi-Stage Docker Builds, creating their own image that includes any desired egress providers.
40
+
41
+
For an example of using Multi-Stage Docker Builds, see the [Dockerfile](https://github.com/dotnet/dotnet-docker/blob/nightly/src/monitor/8.0/ubuntu-chiseled/amd64/Dockerfile) that the `dotnet monitor` team uses to construct the `amd64``monitor` image.
42
+
43
+
To directly access archives for one of `dotnet monitor`'s supported extensions, these are available using the following link (this example is specifically for the `linux-x64` archive): `https://dotnetbuilds.azureedge.net/public/diagnostics/monitor/$dotnet_monitor_extension_version/dotnet-monitor-egress-azureblobstorage-$dotnet_monitor_extension_version-linux-x64.tar.gz`. Note: the versions in this link will change in response to new `dotnet monitor` releases; as a result, the link will need to be changed to reflect the most recent version when updating your extensions.
44
+
45
+
#### Example Of Manually Installing AzureBlobStorage Extension Locally (Version Numbers May Vary)
46
+
47
+
1. Download the archive: `curl -fSL --output dotnet-monitor-egress-azureblobstorage.tar.gz https://dotnetbuilds.azureedge.net/public/diagnostics/monitor/8.0.0-preview.4.23260.4/dotnet-monitor-egress-azureblobstorage-8.0.0-preview.4.23260.4-linux-x64.tar.gz`
48
+
2. Extract the contents of `dotnet-monitor-egress-azureblobstorage.tar.gz`
49
+
* Example (Linux): `tar -xvzf dotnet-monitor-egress-azureblobstorage.tar.gz`
50
+
4. Place the `AzureBlobStorage` directory found inside the archive in one of `dotnet monitor`'s designated extension [locations](./learningPath/egress.md#well-known-egress-provider-locations).
51
+
* Example (Linux): Place `AzureBlobStorage` at `$XDG_CONFIG_HOME/dotnet-monitor/settings.json`.
52
+
5.`dotnet monitor` will now automatically detect the extension - ensure you have added the necessary configuration for the extension (configuration for extensions is written alongside the rest of `dotnet monitor` configuration).
53
+
54
+
> `dotnet monitor` may expand the acquisition model for extensions in the future; if you have a scenario that requires additional installation options, please let us know by creating a [discussion](https://github.com/dotnet/dotnet-monitor/discussions).
55
+
56
+
### Third-Party Egress Extensions
57
+
58
+
The extensibility model allows users to utilize third-party egress providers with `dotnet monitor`. **Note that `dotnet monitor` does not endorse or guarantee any third-party extensions - users should always exercise caution when providing sensitive authentication information (such as passwords) to untrusted extensions.** Third-party egress extensions are responsible for their own distribution, and are not included with `dotnet monitor`.
59
+
60
+
For more information on how to create your own egress extension, see our [learning path](../documentation/learningPath/).
0 commit comments