Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add documentation for Telemetry Logging #3738

Merged
merged 2 commits into from
Mar 6, 2024
Merged

Add documentation for Telemetry Logging #3738

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b722bb3
Add documentation for TelemetryLogging
EXPEkesheth Mar 4, 2024
961736e
Update TelemetryLogging.md
EXPEkesheth Mar 4, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions docs/TelemetryLogging.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
# Enabling telemetry logging with Application Insights

FHIR server enables telemetry logging to your Application Insights resource by updating the Telemetry section in appsettings.json.
1. Application Insights logging package with the Application Insights instrumentation key.
1. Application Insights logging package with the Application Insights connection string.

Properties in Telemetry section in appsettings.json
* Provider : Telemetry provider is “ApplicationInsights” or “None” for disabling telemetry logging.
* InstrumentationKey : The instrumentation key of your Application Insights resource.
* ConnectionString : The connection string of your Application Insights resource.

**Note**:
1. Technical support for instrumentation key-based logging in Application Insights will end in March 2025.
2. When the instrumentation key and connection string are provided in appsettings.json for ApplicationInsights provider, the instrumentation key will be used.

Next Steps: OpenTelemetry provider is still experimental-mode, not recommended for production use.
To use OTEL, set the provider value to “OpenTelemetry” in appsettings.json. Incase the connection string is used for OpenTelemetry provider, the instrumentation key will be ignored.


Loading