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
Event name now will be inferred from the `LogRecord` being emitted. If no name is given, it defaults to `Log`.
14
+
15
+
- Removed `opentelemetry_etw_logs::{ExporterConfig, ReentrantLogProcessor, ETWExporter}` from the public API. Ability to customize Provider Group or Keyword may be added in the future.
16
+
17
+
- Renamed `logs_level_enabled` feature to `spec_unstable_logs_enabled` to match `opentelemetry` features.
18
+
19
+
-`default` feature does not enable `spec_unstable_logs_enabled` anymore.
Copy file name to clipboardExpand all lines: opentelemetry-etw-logs/examples/basic.rs
+7-18Lines changed: 7 additions & 18 deletions
Original file line number
Diff line number
Diff line change
@@ -5,14 +5,14 @@
5
5
//! run with `$ cargo run --example basic --all-features
6
6
//!
7
7
//! To view the telemetry emitted to ETW you can use [`logman`](https://learn.microsoft.com/windows-server/administration/windows-commands/logman) along with `perfview`. `logman` will listen to ETW
8
-
//! events from the given provider (on this example, `my-provider-name`) and store them in a `.etl` file.
8
+
//! events from the given provider (on this example, `provider-name`) and store them in a `.etl` file.
9
9
//! [`perfview`](https://github.com/microsoft/perfview) will allow you to visualize the events.
10
10
//!
11
11
//! Instructions using Powershell:
12
12
//!
13
-
//! 1. Get the ETW Session Guid for the given provider (on this example `my-provider-name`):
13
+
//! 1. Get the ETW Session Guid for the given provider (on this example `provider-name`):
0 commit comments